Skip to main content
The Data Portal is the console where you connect data sources, create and configure tables, run ingestion, and query your data. When one of those actions cannot complete, the message it shows carries a code of the form DPE-#### — short for Data Portal Error. The code names the condition, not the wording. Copy gets improved over time; the code does not change with it, so it is safe to search for on this page, to bookmark, or to quote to support. The same codes appear in Data Portal API responses, so a failure reads the same whether you hit it in the console or from a script. This page lists every code the product can return, what each one means, and what to do about it. If you do not have a code in hand, start from Troubleshooting instead, which routes by symptom.
Alongside the code, each error shows a short reference. That identifies your specific occurrence rather than the class of problem, so include it when you contact support — it is what lets us find the exact event in our logs.

​
How to read an entry

Every entry says what happened and, where you can act on it, what to do next. The category tells you whether acting is worth your time at all: The first digit groups the code by the area it comes from: Connections and data sources | Platform | Request validation | Ingestion and tasks | Queries | Schema and table configuration

​
Connections and data sources

​
DPE-1041 — Not enough records to sample

We read the source but found no records to sample, so the schema could not be inferred. User correctable — you can correct this. What to do
  1. Check the path or query points at files that contain data.
  2. If a filter is set, confirm it is not excluding every record.
  3. Confirm the credentials can read the objects, not just list them.
  4. Preview the rows after changing it — the sample shows whether records now come through.
Related documentation

​
DPE-1042 — Catalog rejected our credentials

The data catalog refused access to that location with the credentials configured for this connection. User correctable — you can correct this. What to do
  1. Confirm the role has list and read permission for the catalog and bucket.
  2. Confirm the configured region matches the bucket region.
  3. Re-enter the credentials on the dataset’s Connection tab, then confirm with Test Connection.
Related documentation

​
DPE-1043 — Catalog configuration incomplete

This connection is missing the catalog settings needed to browse it. User correctable — you can correct this. What to do
  1. Open the connection, set the catalog type, and fill in the settings it asks for.
  2. Run Test Connection before saving — browsing stays unavailable until it passes.
Related documentation

​
DPE-1044 — Kafka credentials rejected

The stream refused the credentials configured for this connection. User correctable — you can correct this. What to do
  1. Check the SASL mechanism, username and password on the connection.
  2. Confirm the credentials have permission to read the topic.
  3. Change them on the dataset’s Connection tab and run Test Connection before saving.
Related documentation

​
DPE-1045 — Could not create the stream consumer

The stream consumer could not be created with the settings on this connection. User correctable — you can correct this. What to do
  1. Check the broker list, security protocol and topic name.
  2. Confirm the topic exists and is reachable from this environment.
  3. Run Test Connection after each change — it keeps failing the same way until the consumer can be created.
Related documentation

​
DPE-1046 — Stream messages could not be decoded

Messages were read from the stream but could not be decoded with the configured format. User correctable — you can correct this. What to do
  1. Confirm the message format matches what the topic actually produces.
  2. If a schema registry is used, confirm its URL and credentials.
  3. Preview the rows to confirm: messages that decode appear in the sample, ones that do not fail it.
Related documentation

​
DPE-1047 — Delta table could not be read

The Delta table could not be opened at the configured location. User correctable — you can correct this. What to do
  1. Confirm the table path points at the Delta table root, not a data file.
  2. Confirm the credentials can read the _delta_log directory.
  3. Correct the path on the dataset’s Connection tab, then run Test Connection.
Related documentation

​
DPE-1048 — Preview could not read the source data

We reached the source but could not read the data needed to build a preview. User correctable — you can correct this. What to do
  1. Confirm the file format matches the configured format.
  2. If the location spans regions, confirm the configured region matches the bucket.
  3. Set the right format on the Data Modeling step, then preview the rows again.
Related documentation

​
DPE-1049 — Not authorized to preview this table

Your account is not authorized to load this table for preview. User correctable — you can correct this. What to do
  1. Ask a workspace administrator to grant your account read access to this table.
  2. The grant is on the table in the source system, not in StarTree.
  3. Reload the page once it is granted.
Related documentation

​
DPE-1050 — No files matched the path

Nothing at the configured path matched the file pattern, so there was no data to read. User correctable — you can correct this. What to do
  1. Check the folder path and the file pattern for a typo.
  2. Confirm the files are present and that this connection can list them.
  3. Correct the path or the pattern on the Connection tab and run Test Connection.

​
DPE-1051 — The data source was busy

The data source reported that it is temporarily unavailable, so the read did not complete. Transient — temporary; retrying usually works. What to do
  1. Wait a moment and try again.

​
DPE-1052 — A value was outside the allowed range

One of the values supplied for this connection was rejected by the data source as out of range. User correctable — you can correct this. What to do
  1. Check the value against the limits the source system documents for that setting.
  2. Run Test Connection after changing it.

​
DPE-1053 — The file could not be read

The file {file} could not be read. It may be incomplete, or its format may not match what this connection expects. User correctable — you can correct this. What to do
  1. Confirm the file’s real format matches the format configured on this connection ({format}).
  2. Confirm the file is complete and not truncated.
  3. Confirm this connection has read access to that path.
  4. Set the connection’s format to the file’s real format, then run Test Connection.
Related documentation

​
DPE-1054 — No files matched that path

Nothing at {path} matched, so there was no data to read. User correctable — you can correct this. What to do
  1. Check the path and the file pattern for a typo.
  2. Confirm files are present at that location and this connection can list them.
  3. Correct it on the dataset’s Connection tab and run Test Connection.
Related documentation

​
DPE-1055 — Access was denied while reading this table

The credentials this data source uses were refused the {action} permission needed to read the table. User correctable — you can correct this. What to do
  1. Grant {action} to the role or user configured on this data source.
  2. If the permission was granted just now, the decision may still be cached — try again shortly.
  3. Nothing changes in StarTree — once the grant is in place, run Test Connection to confirm it.
Related documentation

​
DPE-1056 — The storage credentials cannot read that data

The credentials configured for this catalog’s storage were refused read access to the data file at {path}. User correctable — you can correct this. What to do
  1. Grant read access to that prefix for the identity configured under the catalog’s storage authentication settings.
  2. If the prefix is correct and access was granted recently, try again shortly.
  3. Once the grant is in place, run Test Connection — it reports the same refusal until it is.
Related documentation

​
DPE-1057 — The catalog would not let us sign in

The lakehouse catalog refused the sign-in for this data source’s credentials. User correctable — you can correct this. What to do
  1. Check that the sign-in details saved on this data source are still valid and have not been revoked.
  2. Confirm the account they belong to is entitled to use the catalog’s REST API — some workspaces require an explicit entitlement before that API answers at all.
  3. Confirm the catalog URL and warehouse name are the ones intended.
  4. Re-enter the sign-in details on the dataset’s Connection tab, then run Test Connection.
Related documentation

​
DPE-1058 — The bucket could not be listed

Reading the contents of bucket {bucket} was refused, so its files could not be browsed. User correctable — you can correct this. What to do
  1. Grant list and read permission on that bucket to the identity this connection uses.
  2. When the connection uses the environment’s own role rather than a role you supply, the permission has to be granted to that role.
  3. Once granted, run Test Connection — the table picker stays empty until it passes.
Related documentation

​
DPE-1059 — The streaming source rejected our credentials

The streaming source refused the credentials on this connection while reading partition metadata. User correctable — you can correct this. What to do
  1. Check the API key or credentials saved on this connection.
  2. Confirm the key is scoped to the cluster and topic this connection names, not only to the account.
  3. Replace the key on the dataset’s Connection tab, then run Test Connection.
Related documentation

​
DPE-1060 — The storage credentials were rejected

The identity configured for this catalog’s storage was refused by the cloud provider, so its data could not be read. User correctable — you can correct this. What to do
  1. Check the role and, if one is set, the external ID under the catalog’s storage settings.
  2. Confirm the role’s trust policy allows this environment to assume it.
  3. If access was granted just now, the decision may still be cached — try again shortly.
  4. Run Test Connection once the trust policy is updated; it is the quickest way to see the change take effect.
Related documentation

​
DPE-1061 — That role could not be assumed

The role this connection names refused to be assumed by this environment, so the storage behind it could not be read. User correctable — you can correct this. What to do
  1. Confirm the role’s trust policy allows this environment to assume it.
  2. Check the external ID on this connection matches the one the trust policy expects.
  3. If the trust policy was updated just now, the decision may still be cached — try again shortly.
  4. Run Test Connection once the trust policy is updated, rather than waiting for the next ingestion run.
Related documentation

​
DPE-1062 — That table snapshot is no longer available

The snapshot recorded for {table} is no longer in the catalog. A source table’s own retention removes snapshots, so one that was listed a moment ago can be gone by the time it is read. User correctable — you can correct this. What to do
  1. Reload the page so the current snapshot is picked up.
  2. If it keeps happening, lengthen snapshot retention on the source table so a snapshot survives long enough to be read.
  3. The Monitoring tab’s Snapshot Sync card shows which snapshot was last read successfully.
Related documentation

​
DPE-1063 — Browsing is not available for this source

Catalogs cannot be browsed for a {type} connection in this environment, so the list of tables could not be loaded. User correctable — you can correct this. What to do
  1. Type the database and table names directly instead of browsing for them.
  2. Everything else about the dataset works normally; only the picker is unavailable for this source type.
  3. If you need browsing for this source type, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-1064 — That sign-in needs a one-time passcode

The source refused the sign-in because the account it belongs to requires multi-factor authentication, and a passcode cannot be entered on a stored credential. User correctable — you can correct this. What to do
  1. Use a credential that does not require an interactive passcode — a service account, a service principal or an access token.
  2. If the account must keep multi-factor sign-in, create a separate machine account for StarTree and configure that one instead.
  3. Save the replacement credential on the dataset’s Connection tab and confirm with Test Connection.
Related documentation

​
DPE-1065 — No readable Parquet files at that path

The schema could not be inferred because no readable Parquet file was found under {path}. User correctable — you can correct this. What to do
  1. Check that the path points at the directory holding the Parquet files, not at a parent of it.
  2. Confirm the configured credentials can read that prefix.
  3. If the files were written moments ago, try again shortly.
  4. Correct the path on the Connection tab, then preview the rows.
Related documentation

​
DPE-1066 — That table is no longer in the catalog

The catalog no longer lists {table}, so it could not be read. A table that has been renamed, dropped or moved to another namespace disappears from the listing. User correctable — you can correct this. What to do
  1. Reload the table list and pick the table again.
  2. If it was renamed, point the dataset at the new name from its Connection tab.
  3. If it was moved to a different namespace or database, update that on the connection too — the table name alone is not enough.
Related documentation

​
DPE-1067 — That access key is not recognised

The object store rejected the access key configured for this source because it does not exist. A key that has been deleted or rotated stops working immediately. User correctable — you can correct this. What to do
  1. Re-enter the access key and secret for this source.
  2. Confirm the key is still active in the cloud provider’s console — a rotated key has to be replaced here too.
  3. Re-enter it on the dataset’s Connection tab and confirm with Test Connection.
Related documentation

​
DPE-1068 — Object storage refused the request

The storage service rejected the request as forbidden, so the data could not be read. User correctable — you can correct this. What to do
  1. Check the credential has read access to this bucket and prefix.
  2. If access is granted by role, confirm the role can be assumed from StarTree and that any bucket policy allows it.
  3. Re-test from the dataset’s Connection tab once the permission is in place.

​
DPE-1069 — That table is not an Iceberg table

{table} exists in the catalog but is not stored in Iceberg format, so it cannot be read as an external table. User correctable — you can correct this. What to do
  1. Pick a table that is registered as Iceberg — the catalog lists the format alongside each table.
  2. A view, or a table written in another format, cannot be used here even though it appears in the same catalog.
  3. If you expected this one to be Iceberg, it may have been created by a tool that registers metadata only; recreate it as an Iceberg table at the source.
Related documentation

​
DPE-1070 — The connection test could not run

The test could not be carried out because of a fault on our side, so whether the settings are correct is still unknown. Internal — a defect on our side. What to do
  1. Try the test again — a single failure may not repeat.
  2. If it keeps failing, contact StarTree support and quote the reference shown with this error; the settings you entered are not the cause.
Related documentation

​
DPE-1071 — The source took too long to answer

StarTree asked the source for data but no reply arrived within the time allowed, so the request stopped before it finished. Transient — temporary; retrying usually works. What to do
  1. Try again — a busy source can be slow to answer once.
  2. If it keeps happening, check that the host and port are correct and that the source accepts traffic from StarTree, for example through an allow-list or a private link.
  3. If the settings are correct and it still stops, contact StarTree support and quote the reference shown with this error.

​
DPE-1072 — The catalog’s reply was cut off

The Iceberg catalog began sending the details of {table}, but the reply stopped partway through, so the table could not be read. When a reply stops at the same point on every attempt, a size limit is the usual cause, and trying again on its own will not help. Upstream — a service we depend on did not answer as expected. What to do
  1. Expire old snapshots on {table}. The catalog sends the table’s full snapshot history in this reply, and a long history makes it very large.
  2. If a proxy or gateway sits in front of the catalog, check whether it limits the size of responses.
  3. If the reply is still cut off, contact StarTree support and quote the reference shown with this error.
Related documentation

​
Platform

​
DPE-0000 — Something went wrong on our side

This action did not complete because of an unexpected problem on our side. Internal — a defect on our side. What to do
  1. Retry the action.
  2. If it happens again, contact StarTree support and quote the reference shown with this error.

​
DPE-5101 — The system is busy

We could not complete your request because the service is at capacity right now. Transient — temporary; retrying usually works. What to do
  1. Wait a moment and try again.

​
DPE-5102 — The system is busy

A database operation could not complete right now. Transient — temporary; retrying usually works. What to do
  1. Wait a moment and try again.

​
DPE-5103 — The system is busy

A database operation could not complete right now. Transient — temporary; retrying usually works. What to do
  1. Wait a moment and try again.

​
DPE-5104 — A service we depend on is unavailable

A service this action depends on could not be reached. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.
  2. If it persists, contact StarTree support and quote the reference shown with this error.

​
DPE-5105 — A service we depend on is unavailable

A service this action depends on did not respond. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.
  2. If it persists, contact StarTree support and quote the reference shown with this error.

​
DPE-5106 — The cluster is not reachable

We could not reach the cluster that stores this dataset. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.
  2. If it persists, contact StarTree support and quote the reference shown with this error.

​
DPE-5107 — The cluster is at capacity

The cluster declined this request because it is protecting itself from overload. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.

​
DPE-5108 — Something went wrong on our side

The cluster returned an error we could not interpret, so the action did not complete. Internal — a defect on our side. What to do
  1. Retry the action.
  2. If it happens again, contact StarTree support and quote the reference shown with this error.

​
DPE-5109 — The request could not be read

The request body was not valid JSON, so it could not be read and nothing was changed. User correctable — you can correct this. What to do
  1. Reload the page and repeat the action.
  2. If you are calling the API directly, the body has to be well-formed JSON and the request has to set a JSON content type.

​
DPE-5110 — A service we depend on is unavailable

A service this action depends on did not respond in time. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.
  2. If it persists, contact StarTree support and quote the reference shown with this error.

​
DPE-5111 — That action is not available here

This request used a method this address does not accept, so nothing was changed. Internal — a defect on our side. What to do
  1. Reload the page and try again.
  2. If it happens again, contact StarTree support and quote the reference shown with this error.

​
DPE-5112 — That address does not exist

Nothing on this service answers that address, so the request was not processed. Internal — a defect on our side. What to do
  1. Reload the page and try again.
  2. If it happens again, contact StarTree support and quote the reference shown with this error.

​
DPE-5117 — A stored setting could not be read

One of this connection’s saved settings is incomplete, so it could not be loaded. Internal — a defect on our side. What to do
  1. Reopen the connection and save it again to rewrite the stored settings.
  2. If that does not help, contact StarTree support and quote the reference shown with this error.

​
DPE-5118 — The request was cancelled

The request ended before a reply could be sent, usually because the page was closed or navigated away from. Informational — not a failure; act only if you want a different outcome.

​
DPE-5119 — Cluster health is not available right now

The cluster answered the health request without any detail, so there is nothing to show yet. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a few moments.
  2. If it stays empty, contact StarTree support and quote the reference shown with this message.

​
DPE-5120 — Something went wrong on our side

This action did not complete because a database request could not be carried out. Internal — a defect on our side. What to do
  1. Retry the action.
  2. If it happens again, contact StarTree support and quote the reference shown with this message.

​
DPE-5121 — The cluster did not answer in time

A call to the cluster did not complete, so this action could not finish. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a moment.
  2. If it keeps happening, contact StarTree support and quote the reference shown with this error.

​
DPE-5122 — A service we depend on did not answer

An internal service this action needs returned an error, so the action could not complete. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a moment.
  2. If it keeps happening, contact StarTree support and quote the reference shown with this error.

​
DPE-5123 — An answer from the cluster could not be read

The cluster replied in a shape this action did not expect, so the result could not be read. Internal — a defect on our side. What to do
  1. Retry the action.
  2. If it happens again, contact StarTree support and quote the reference shown with this error.

​
DPE-5124 — That data source type is not recognised

The request named a data source type this environment does not have. User correctable — you can correct this. What to do
  1. Pick a data source type from the list offered under Select Data Source.
  2. If you are calling the API directly, read the type ids from the data source types endpoint rather than hard-coding one.
  3. Types differ by environment, so one that works elsewhere may not exist here.

​
DPE-5125 — The change is still being applied

The change was accepted, but the cluster had not finished applying it everywhere before we stopped waiting, so {table} may take a little longer to reflect it. Upstream — a service we depend on did not answer as expected. What to do
  1. Refresh in a few minutes to see the change take effect.
  2. If it has not settled by then, contact StarTree support and quote the reference shown with this error.

​
DPE-5126 — That file is not served here

A browser asked this service for a static file it does not serve. Nothing the reader did caused it and nothing is affected. Informational — not a failure; act only if you want a different outcome. What to do
  1. No action is needed.

​
DPE-5127 — Some copies of this data are in an error state

Parts of this dataset are held on servers that could not bring them online, and the cluster does not retry those on its own, so the change was stopped rather than left half-applied. Upstream — a service we depend on did not answer as expected. What to do
  1. Contact StarTree support and quote the reference shown with this error — clearing this needs a reset on the affected copies.
  2. Querying the dataset may return partial results until it is cleared.

​
DPE-5128 — The change stopped making progress

The cluster began applying this change but stopped advancing, so it was abandoned rather than left running indefinitely. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a few minutes — a cluster that was busy usually completes the change on a later attempt.
  2. If it stalls repeatedly, contact StarTree support and quote the reference shown with this error.

​
DPE-5129 — The API reference could not be generated

The page that describes this service’s API could not be built because of a fault on our side. The API itself is unaffected. Internal — a defect on our side. What to do
  1. Keep using the API as normal — only the reference page is affected.
  2. If you need the reference page, contact StarTree support and quote the reference shown with this error.

​
Request validation

​
DPE-5201 — Ingestion type not recognised

This dataset is configured with an ingestion type this version does not recognise. User correctable — you can correct this. What to do
  1. Open the dataset and pick an ingestion type from the list under Select Data Source.
  2. This usually means the dataset was created on a newer version than this environment runs.
  3. If the type should exist here, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-5202 — A required value was missing

The request did not include {param}, which is required to complete it. User correctable — you can correct this. What to do
  1. Reload the page and repeat the action so {param} is sent.
  2. If you are calling the API directly, include {param} — it has no default.

​
DPE-5203 — You do not have access to this

Your account is not authorized for this action in this workspace. Informational — not a failure; act only if you want a different outcome. What to do
  1. Ask a workspace administrator to grant the permission you need.
Related documentation

​
DPE-5204 — You do not have access to this

Your account is not authorized for this action in the cluster. Informational — not a failure; act only if you want a different outcome. What to do
  1. Ask a workspace administrator to grant the permission you need.
Related documentation

​
DPE-5205 — You do not have access to this

Your account is not authorized for this action in this workspace. Informational — not a failure; act only if you want a different outcome. What to do
  1. Ask a workspace administrator to grant the permission you need.
Related documentation

​
DPE-5206 — Connection not found

The connection this dataset uses is no longer available. User correctable — you can correct this. What to do
  1. Open the dataset’s Connection tab and pick a connection from Existing Connection.
  2. If the one it used was deleted, create it again under New Connection, then run Test Connection.
  3. The dataset keeps its schema and ingestion settings while you reconnect it.
Related documentation

​
DPE-5207 — Uploaded file could not be read

The uploaded file could not be read. It may have been interrupted, or exceed the size limit. User correctable — you can correct this. What to do
  1. Upload the file again — an interrupted upload cannot be resumed.
  2. Files must be under 30 MB; a larger one is refused before it is read.
  3. For anything larger, put the file in object storage and connect to it instead of uploading it.
Related documentation

​
DPE-5208 — Uploaded file was empty

The uploaded file contained no records, so no schema could be inferred. User correctable — you can correct this. What to do
  1. Open the file and confirm it has a header row and at least one row of data under it.
  2. Re-upload it — files must be under 30 MB.
  3. For CSV, check the delimiter matches the file; a wrong delimiter reads the whole file as one unusable column.

​
DPE-5209 — Setting not recognised

One of the settings sent with this request is not recognised. User correctable — you can correct this. What to do
  1. Reload the page so the current set of options is loaded, then set it again.
  2. If it still fails, the setting has been withdrawn from this version — leave it unset.

​
DPE-5210 — That dataset could not be found

The dataset {srn} no longer exists, or it was renamed while this page was open. User correctable — you can correct this. What to do
  1. Reload the page and open the dataset again from the Tables list.
  2. If it is not in the list, it was deleted — nothing further is needed.
  3. If you reached this from a bookmark or a shared link, the name in the link is out of date.

​
DPE-5211 — You do not have access to that

Your account does not have permission to {action}. User correctable — you can correct this. What to do
  1. Ask a workspace administrator for a role that allows this action.
  2. Quote the action name shown in this error — that is the permission to grant.
  3. Once granted, reload the page: permissions are read when the page loads.

​
DPE-5212 — That value is not valid here

The value supplied for {param} is not one this request accepts. User correctable — you can correct this. What to do
  1. Open the item from its list rather than editing the address bar.
  2. If you are calling the API directly, check the type {param} expects — an id where a name is required is the usual cause.

​
DPE-5213 — A required value was not supplied

{field} is required, and the request did not include it. User correctable — you can correct this. What to do
  1. Fill in {field} and submit again.
  2. If the field is not on screen, it belongs to a later step — complete the steps in order.
  3. For a JSON editor, use Validate before saving; it reports the missing field by name.

​
DPE-5214 — A required value was not supplied

The request was missing a value it needs, so it was not processed. User correctable — you can correct this. What to do
  1. Reload the page and repeat the action.
  2. If a field on screen is empty, fill it in — required fields are marked Required.
  3. If you are calling the API directly, check the request against the API reference.

​
DPE-5215 — Choose a source type

This request did not say which kind of source it is for. User correctable — you can correct this. What to do
  1. Go back to Select Data Source and choose the source type.
  2. Accepted values: {types}.

​
DPE-5216 — That name is already taken

Another data source in this workspace already uses this name. User correctable — you can correct this. What to do
  1. Enter a different name under New Connection.
  2. To reuse the existing one instead, pick it from Existing Connection rather than creating a second.
  3. Names must be unique per workspace, so a name in use elsewhere in your organisation is still available here.

​
DPE-5217 — That dataset belongs to a different workspace

The dataset named in the request is not in the workspace the request was made against. User correctable — you can correct this. What to do
  1. Switch to the workspace that owns the dataset, then repeat the action.
  2. The workspace is part of the dataset’s reference, so a link saved from another workspace will keep failing here.
  3. If you cannot see that workspace, ask an administrator for access to it.

​
DPE-5218 — That value is not one of the accepted options

{parameter} only accepts a fixed set of values, and the one supplied is not among them. User correctable — you can correct this. What to do
  1. Pick {parameter} from its dropdown rather than typing it — the list holds the accepted values.
  2. If you are editing JSON directly, copy the value exactly, including its case.

​
DPE-5219 — That data source type is not available here

That data source type is not one this environment can use. User correctable — you can correct this. What to do
  1. Choose one of the data source types offered under Select Data Source.
  2. Availability differs by environment, so a type you have used elsewhere may not be enabled here.
  3. If you expect this type to be available, contact StarTree support and quote the reference shown with this message.

​
DPE-5220 — A required setting is missing

This source cannot be used until {property} is set. User correctable — you can correct this. What to do
  1. Set {property} on the connection, then run Test Connection.
  2. If you do not know the value, it comes from the source system’s own settings, not from StarTree.
  3. Leave no leading or trailing spaces — they are kept and will not match.
Related documentation

​
DPE-5221 — Ingestion settings are needed to preview rows

Sample rows cannot be read until this dataset’s ingestion settings have been filled in. User correctable — you can correct this. What to do
  1. Finish the Data Modeling step for this dataset, then preview again.
  2. Preview reads rows through the dataset’s ingestion settings, so it cannot run before they exist.
Related documentation

​
DPE-5222 — A source in the list is no longer there

While building the list of datasets for a source, that source had already been removed, so its datasets were left out. Informational — not a failure; act only if you want a different outcome. What to do
  1. Reload the page to see the current list.
Related documentation

​
DPE-5223 — Notification preferences need a recipient or a dataset

Listing notification preferences needs either a recipient email address or a dataset key, and neither was supplied. User correctable — you can correct this. What to do
  1. Retry from the dataset’s Notifications tab, which supplies the dataset key.
  2. Or supply a recipient email address to list one person’s preferences.

​
DPE-5224 — That data source belongs to a different workspace

The data source is registered against another workspace, so it cannot be used from this one. User correctable — you can correct this. What to do
  1. Switch to the workspace that owns this data source.
  2. Or create a data source in the current workspace pointing at the same system.

​
DPE-5225 — That recipient has no preferences set

No notification preferences have been saved for this recipient yet, so there is nothing to show. Informational — not a failure; act only if you want a different outcome. What to do
  1. Set preferences for this recipient to start receiving notifications.
Related documentation

​
Ingestion and tasks

​
DPE-3104 — No ingestion runs yet

This dataset has no ingestion task scheduled, so there is no run history to show. Informational — not a failure; act only if you want a different outcome. What to do
  1. Schedule an ingestion task to get started.
Related documentation

​
DPE-3105 — No ingestion runs yet

No ingestion run has been recorded for this dataset yet, so there is no progress to report. Informational — not a failure; act only if you want a different outcome. What to do
  1. Schedule an ingestion task, then check back once the first run starts.
Related documentation

​
DPE-3106 — No files matched this run

The ingestion task ran but found no new input files matching the configured path, so nothing was scheduled. Informational — not a failure; act only if you want a different outcome. What to do
  1. Confirm the input path and file pattern point at the files you expect.
  2. If files were already ingested, this is expected — each file is processed once.
Related documentation

​
DPE-3107 — Ingestion service unavailable

We could not reach the service that reports ingestion progress. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry in a few minutes.
  2. If it persists, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3108 — Preview is not available for this dataset

Sample rows cannot be shown for a dataset ingested with {taskType}. Its ingestion is unaffected — only the preview is. Informational — not a failure; act only if you want a different outcome. What to do
  1. Continue without the preview, or inspect the data with a query once ingestion has run.
Related documentation

​
DPE-3109 — Task configuration missing

This dataset has no configuration for the requested ingestion task, so it cannot be scheduled. User correctable — you can correct this. What to do
  1. Open the dataset’s Tasks tab and add the configuration for that task type.
  2. A task cannot be scheduled before its configuration exists, so the schedule will keep failing until it does.
Related documentation

​
DPE-3110 — Ingestion task scheduling failed

The scheduler rejected the request to run this ingestion task. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry shortly.
  2. If it persists, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3111 — Ingestion state unavailable

Ingestion is not running for this dataset, and we could not tell whether it was never started or the cluster is missing state for it. Upstream — a service we depend on did not answer as expected. What to do
  1. Refresh in a moment to see whether it recovers.
  2. If it persists, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3112 — Could not read ingestion progress

We could not read the consuming-segment information for this dataset. This is on our side. Upstream — a service we depend on did not answer as expected. What to do
  1. Retry shortly.
  2. If it persists, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3113 — Could not reach the ingestion service

We could not reach the service that reports task progress, so its status is unavailable right now. Upstream — a service we depend on did not answer as expected. What to do
  1. Wait a moment and refresh.
  2. If it keeps happening, contact StarTree support and quote the reference shown with this error.

​
DPE-3115 — No files found at the source path

Nothing could be listed at {uri}, so there was nothing to ingest. User correctable — you can correct this. What to do
  1. Check the path on the dataset’s Connection tab for a typo, and confirm files exist under it.
  2. Confirm the connection’s credentials allow listing that location, not only reading a known file.
  3. Run the task again from the Tasks tab once the path lists files.
Related documentation

​
DPE-3116 — Ingestion could not be scheduled

The ingestion run for {table} could not be scheduled. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a moment.
  2. If it persists, contact StarTree support and quote the reference shown with this error.

​
DPE-3117 — Ingestion status is unavailable

The ingestion service did not return the task details for this dataset, so its status cannot be shown right now. Upstream — a service we depend on did not answer as expected. What to do
  1. Wait a moment and refresh.
  2. If it keeps happening, contact StarTree support and quote the reference shown with this error.

​
DPE-3118 — Ingestion run failed

The most recent ingestion run for this dataset did not complete. Upstream — a service we depend on did not answer as expected. What to do
  1. Open the dataset’s Tasks tab to see which run failed and what it reported.
  2. If runs keep failing, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3119 — You do not have access to task details

Reading task details for this dataset requires a permission this account does not have. Informational — not a failure; act only if you want a different outcome.

​
DPE-3120 — Pinot answered with nothing

The cluster returned an empty reply where a result was expected, so this action could not complete. Upstream — a service we depend on did not answer as expected. What to do
  1. Try again in a moment.
  2. If it keeps happening, contact StarTree support and quote the reference shown with this error.

​
DPE-3121 — No new ingestion run was needed

The scheduled check ran and found nothing new to ingest since the previous run, so no run was started. Informational — not a failure; act only if you want a different outcome. What to do
  1. Nothing to do — the next scheduled check starts a run once there is new data.
Related documentation

​
DPE-3122 — Streaming ingestion has stalled

Part of this dataset has stopped reading from the stream, so new records are not arriving. This is on our side, not your configuration. Upstream — a service we depend on did not answer as expected. What to do
  1. Check again in a few minutes — reading usually resumes on its own.
  2. If it persists, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3123 — A source file could not be ingested

{file} could not be turned into data for this dataset. The file may be incomplete, or its columns may not match the dataset’s schema. User correctable — you can correct this. What to do
  1. Check that {file} is complete and that its columns match the dataset’s Schema tab.
  2. A column present in the file but absent from the schema is ignored; one the schema requires but the file lacks fails the file.
  3. Fix or remove the file, then run the ingestion again from the Tasks tab.
Related documentation

​
DPE-3124 — Ingestion paused while capacity frees up

New ingestion runs are being held back for this dataset because the environment has reached its configured capacity limits. Informational — not a failure; act only if you want a different outcome. What to do
  1. Runs resume on their own once capacity frees up.
  2. If the pause continues, contact StarTree support about the capacity for this environment.
Related documentation

​
DPE-3125 — Some rows have timestamps out of range

A segment could not be created because its time range {range} falls outside the range StarTree accepts, {allowed}. Rows carrying a placeholder or a mis-parsed timestamp produce dates far in the past or the future. User correctable — you can correct this. What to do
  1. Correct the timestamps in the source data, or exclude the rows carrying them.
  2. A placeholder date or a unit mismatch is the usual cause — seconds read as milliseconds land in 1970, milliseconds read as seconds land far in the future.
  3. If those rows are expected, set segmentTimeValueCheck to false under ingestionConfig in the Configuration tab to allow them.
  4. The dataset’s other files are unaffected; only the rejected segment needs reloading.
Related documentation

​
DPE-3126 — This dataset has no data to show

No segments are present for this dataset. When every row’s timestamp is older than the retention period, its segments are removed automatically. User correctable — you can correct this. What to do
  1. Check the timestamp field in the data that was loaded — if its newest value predates the retention period, nothing is kept.
  2. Increase the retention period in the Configuration tab, or load data that falls inside it.
  3. The Monitoring tab shows when the last run completed, which tells you whether data arrived and aged out or never arrived.
  4. If retention is not the cause, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3127 — The source warehouse is suspended

The ingestion could not run because every warehouse on the source Snowflake account is suspended. A trial that has ended suspends them until billing details are added. User correctable — you can correct this. What to do
  1. Resume a warehouse in the Snowflake account, or add billing details there if a trial has ended.
  2. Then open the dataset’s Tasks tab and run the ingestion again.
  3. Nothing in StarTree needs changing — the account holding the source data is what refused.
Related documentation

​
DPE-3128 — This dataset needs exactly one task configuration

The ingestion settings hold more than one task configuration, or none, and exactly one is required. User correctable — you can correct this. What to do
  1. Open the dataset’s Ingestion settings and leave a single task configuration in place.
  2. If you were adding a second ingestion type, create a separate dataset for it instead.

​
DPE-3129 — Ingestion tasks could not be generated

The cluster could not work out what this dataset’s next ingestion run should do, so no task was submitted. Upstream — a service we depend on did not answer as expected. What to do
  1. Open the dataset’s Tasks tab — the most recent run records the reason underneath this one.
  2. A source that cannot be listed or read is the usual cause, so check the Connection tab’s settings still work with Test Connection.
  3. If runs keep failing, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3130 — Another run is already being prepared

Task generation for this dataset is already in progress elsewhere in the cluster, so this attempt stopped rather than duplicating it. Informational — not a failure; act only if you want a different outcome. What to do
  1. No action is needed — the run that holds the lock continues normally.
Related documentation

​
DPE-3131 — The ingestion schedule is not firing correctly

This dataset’s next run is recorded as a time that has already passed, which means the schedule is no longer firing as configured. User correctable — you can correct this. What to do
  1. Open the dataset’s Tasks tab and save the schedule again — re-saving rebuilds the trigger.
  2. If it goes wrong again after re-saving, contact StarTree support and quote the reference shown with this error.
Related documentation

​
DPE-3132 — That file could not be read

The uploaded file could not be read into the dataset, so nothing was ingested. User correctable — you can correct this. What to do
  1. Check the file opens in the format it was uploaded as — a mismatch between the real format and the chosen one is the usual cause.
  2. Confirm the file is complete; an interrupted upload fails part-way through the data rather than at the start.
  3. If some rows carry a different shape from the rest, correct or remove them and upload again.
Related documentation

​
DPE-3133 — The time column is missing from the uploaded data

The segment built from this data does not contain {timeColumn}, the column this dataset’s configuration names as its time column, so the upload was rejected. User correctable — you can correct this. What to do
  1. Check that {timeColumn} is spelled exactly as it is in the schema — the configuration and the schema must name the same column.
  2. If the column was renamed or removed from the schema, update the time column in the dataset’s configuration to match.
  3. To accept data without a time column, set segmentTimeValueCheck to false under ingestionConfig in the Configuration tab. Segments loaded that way carry no time range.
Related documentation

​
Queries

​
DPE-4301 — Query could not be parsed

The query could not be parsed, so it was not run. User correctable — you can correct this. What to do
  1. Check the query for an unclosed quote or bracket, or a missing comma between selected columns.
  2. The editor validates as you type, and marks the position it stopped at.
  3. Use Format Query to make an unbalanced bracket visible.
Related documentation

​
DPE-4302 — Query took too long

The query did not finish within the time allowed and was stopped. Transient — temporary; retrying usually works. What to do
  1. Narrow the time range or add a filter, then run it again.
Related documentation

​
DPE-4303 — Table not found for this query

The query references a table that does not exist in this workspace. Informational — not a failure; act only if you want a different outcome. What to do
  1. Check the table name in the query.

​
DPE-4304 — Query analysis is not set up

Query analysis is switched on for this environment, but the service that performs it has no endpoint or credential configured, so no analysis can run. Nothing about the query caused this. Upstream — a service we depend on did not answer as expected. What to do
  1. Contact StarTree support to finish enabling query analysis for this environment.
  2. On a self-managed install, ask whoever administers it to set the analysis service endpoint and credential.

​
DPE-4305 — That query could not be parsed

The SQL could not be read, so nothing was run. User correctable — you can correct this. What to do
  1. Check the query for an unclosed quote, bracket or comment.
  2. Confirm every table and column name is spelled as it is in the dataset.
  3. Run a smaller part of the statement to find the clause that will not parse.

​
Schema and table configuration

​
DPE-2201 — Dataset name not allowed

Dataset names may use lowercase letters, numbers, hyphens and underscores only. User correctable — you can correct this. What to do
  1. Rename it on the Create table step using lowercase letters, numbers, hyphens and underscores only.
  2. Capital letters and spaces are the two that are usually at fault.
  3. A dataset cannot be renamed once it exists, so it is worth getting right here — the name becomes part of its internal identifiers.
Related documentation

​
DPE-2202 — Dataset name is required

A dataset name was not provided, so the dataset could not be created. User correctable — you can correct this. What to do
  1. Enter a name for the dataset on the Create table step and submit again.
  2. Lowercase letters, numbers, hyphens and underscores are accepted.
Related documentation

​
DPE-2203 — Double underscore not allowed in name

Dataset names cannot contain a double underscore, which Pinot reserves for internal naming. User correctable — you can correct this. What to do
  1. Remove the double underscore on the Create table step — a single underscore is fine.
  2. This applies to the dataset name and its schema name; both are rejected.
  3. Pinot reserves the double underscore for its own segment naming, so it cannot appear in either.
Related documentation

​
DPE-2204 — Column name not allowed

A column name contains a forward slash or a backslash. Those two characters are reserved because column names become path segments internally. User correctable — you can correct this. What to do
  1. Rename the column so it contains no forward slash or backslash.
  2. Every other character is accepted, so only those two need removing.
  3. Rename it on the Data Modeling step, or in the Schema tab’s Edit view, then Save Schema.
Related documentation

​
DPE-2205 — Schema is not backward-compatible

The updated schema cannot replace the existing one because it drops or changes columns already in use. User correctable — you can correct this. What to do
  1. Open the Schema tab, choose Edit, and put back every column the existing schema has.
  2. You may add new columns freely — only removing or retyping an existing one is refused.
  3. To change a column’s type, create a new dataset with the type you want and load the data into it; the stored segments cannot be reinterpreted in place.
Related documentation

​
DPE-2206 — Table configuration rejected

Pinot rejected the table configuration for this dataset. User correctable — you can correct this. What to do
  1. Open the Configuration tab, choose Edit, and use Validate — it reports the exact field at fault.
  2. If you pasted the configuration, check for a trailing comma or an unquoted value; a parse failure is reported as the whole config being invalid.
  3. A value of the wrong type is the other common cause — a number entered as text, or text where a number is required.
Related documentation

​
DPE-2207 — Datetime format not recognised

The datetime format configured for a column does not match the values in the source data. User correctable — you can correct this. What to do
  1. Set Datetime Format on the column to match the source values exactly.
  2. For epoch values, the format is a size, a unit and a type — for example 1:MILLISECONDS:EPOCH.
  3. For formatted text, give the pattern the values actually use, such as a four-digit year, then month, then day.
  4. Preview the rows after changing it: the sample shows whether the values now parse.
Related documentation

​
DPE-2208 — This dataset already exists

A dataset with this name already exists in the workspace. User correctable — you can correct this. What to do
  1. Choose a different dataset name.
  2. To change the existing dataset instead, open it from the Tables list — creating it again is not needed.
  3. A deleted dataset’s name is free again only once its removal finishes.
Related documentation

​
DPE-2209 — Dataset not found

This dataset is no longer available. It may have been deleted, or the link may be out of date. Informational — not a failure; act only if you want a different outcome. What to do
  1. Refresh the page, then open the dataset from the list.
Related documentation

​
DPE-2210 — Dataset not found

This dataset is no longer available. It may have been deleted, or the link may be out of date. Informational — not a failure; act only if you want a different outcome. What to do
  1. Refresh the page, then open the dataset from the list.

​
DPE-2211 — Transform refers to a field that does not exist

The transform for column {columnName} refers to {property}, which is not present on the source record. User correctable — you can correct this. What to do
  1. On the Data Modeling step, open {columnName} and check the field name in its Transformation panel against the source record.
  2. Field names are case-sensitive, and a nested field needs its full path, not just the leaf name.
  3. If the field is genuinely absent from some records, guard the transform so a missing value is tolerated rather than fatal.
  4. Preview the rows to confirm the transform now resolves.
Related documentation

​
DPE-2212 — Transform expression could not be evaluated

A transform or filter expression on this dataset could not be evaluated against the source data. User correctable — you can correct this. What to do
  1. On the Data Modeling step, open the affected column’s Transformation panel and re-check the expression.
  2. Confirm every field it references exists in the source and holds the type the expression assumes.
  3. Preview the rows after editing — the sample is evaluated through the same expression.
Related documentation

​
DPE-2213 — Column value did not match its type

A value in column {columnName} could not be converted to the type configured for it. User correctable — you can correct this. What to do
  1. Either set {columnName}’s Field Type to a type its values fit, or correct the values at the source.
  2. A single stray value is enough to fail the whole column — an empty string where a number is expected is the usual one.
  3. Preview the rows to see the offending value before you change the type.
Related documentation

​
DPE-2214 — Dataset not found in Pinot

This dataset does not exist in the cluster. It may have been deleted, or never finished creating. Informational — not a failure; act only if you want a different outcome. What to do
  1. Refresh the page, then open the dataset from the list.

​
DPE-2215 — That identifier is not valid

One of the identifiers in this request is not in a form this service recognises. User correctable — you can correct this. What to do
  1. Reload the page and repeat the action from the list rather than from a saved link.
  2. If you are calling the API directly, the identifier must be the full reference the list endpoint returns, not just a name.

​
DPE-2216 — Dataset removed

The dataset {table} was removed. Its entry here will clear on its own shortly. Informational — not a failure; act only if you want a different outcome. What to do
  1. Refresh the list in a moment.

​
DPE-2217 — Dimension table needs a primary key

A dimension table has to declare at least one primary key column, and this one declares none. User correctable — you can correct this. What to do
  1. On the Data Modeling step, set Primary Key on at least one column.
  2. The primary key is what identifies a row for lookups, so a dimension table cannot be created without one.
  3. If this was not meant to be a dimension table, clear isDimTable in the Configuration tab instead.
Related documentation

​
DPE-2218 — That server tenant does not exist

The server tenant named in this table configuration has no instances, so the table cannot be placed. User correctable — you can correct this. What to do
  1. Set Tenant in the Configuration tab to one that exists in this environment.
  2. The name is case-sensitive and must match exactly.
  3. If the tenant should exist, it has no servers assigned yet — a workspace administrator assigns those.
Related documentation

​
DPE-2219 — A dataset of that name already exists

{table} already exists, so it cannot be created again. User correctable — you can correct this. What to do
  1. Choose a different name for the new dataset.
  2. To change the existing one, open it from the Tables list and edit it instead of creating it again.

​
DPE-2220 — That setting cannot be changed after creation

{fields} cannot be changed on an existing dataset, because doing so would make the data already stored inconsistent with the new setting. User correctable — you can correct this. What to do
  1. Put {fields} back to their current values; the rest of your changes will then save.
  2. To adopt the new setting, create a new dataset with it and load the data into that.
  3. These settings determine how existing segments were written, which is why they cannot change under data that is already stored.

​
DPE-2221 — A value in the configuration has the wrong type

The value {value} was given where a {targetType} is required, so the configuration could not be read. User correctable — you can correct this. What to do
  1. Replace {value} with a valid {targetType}.
  2. Quoting is the usual cause: a number wrapped in quotes is read as text and refused.
  3. If the value stands for missing data, leave the field out rather than filling it with a placeholder.
  4. Use Validate in the Configuration tab to confirm before saving.

​
DPE-2222 — The configuration could not be read

Part of the dataset configuration is not valid, so it could not be applied. User correctable — you can correct this. What to do
  1. Open the Configuration tab, choose Edit, and use Validate — it names the field at fault.
  2. If you pasted the configuration, check it is complete: a truncated paste is the most common cause.
  3. Check the Schema tab too — a dataset is rejected if either half is invalid.

​
DPE-2223 — A timestamp did not match its declared format

The value {value} could not be read as a time using the format declared for that column. User correctable — you can correct this. What to do
  1. Set Datetime Format on that column so it describes the values actually present.
  2. For epoch values the format is size, unit and type — for example 1:MILLISECONDS:EPOCH; a value in seconds declared as milliseconds reads as 1970.
  3. For formatted text, the pattern has to match exactly, separators included.
  4. Preview the rows after changing it to confirm the values parse.

​
DPE-2224 — No servers are assigned to that tenant

The server tenant {tag} has no servers assigned to it, so this dataset cannot be placed on it. User correctable — you can correct this. What to do
  1. Set Tenant in the Configuration tab to one that has servers assigned.
  2. A tenant with no servers cannot hold data, so the dataset has nowhere to be placed.
  3. If this is the tenant you expect to use, ask a workspace administrator to assign servers to it.
Related documentation

​
DPE-2225 — Granularity value not recognised

The granularity in this configuration is not a value the cluster accepts, so the configuration was rejected and nothing was changed. User correctable — you can correct this. What to do
  1. Set the granularity to a size and a unit — either 1:DAYS or DAYS|1.
  2. The unit has to be one of NANOSECONDS, MICROSECONDS, MILLISECONDS, SECONDS, MINUTES, HOURS or DAYS, in capitals.
  3. If you copied the line out of a configuration file, paste only the value — a field holding the property name as well as the value is the most common cause.
  4. Remove the granularity entirely to fall back to this dataset’s default.
Related documentation

​
DPE-2226 — The two halves name different time columns

A dataset that ingests both batch and streaming data must use one time column on both halves. This one names {offline} on the batch half and {realtime} on the streaming half, so the configuration was rejected. User correctable — you can correct this. What to do
  1. Set the same time column on both halves, then save again.
  2. Time Column is on the Data Modeling step; both halves have to name the same one because a query spans them together.
  3. If only one half is needed, remove the other rather than leaving its time column unset.
Related documentation

​
DPE-2227 — The dataset still has tasks running

It could not be deleted because {tasks} task(s) are still running on it. Its schedules have been cleared, so no further tasks will start. Transient — temporary; retrying usually works. What to do
  1. Wait for the running tasks to finish, then delete the dataset again.
Related documentation

​
DPE-2228 — The primary key names a column that is not there

This dataset’s primary key lists {column}, which is not one of its columns, so the dataset could not be created. User correctable — you can correct this. What to do
  1. On the Data Modeling step, either add a column named {column} or change the primary key to a column that exists.
  2. The primary key has to be spelled exactly as the column is, including case.
  3. A dimension table needs at least one primary key column, so it cannot simply be cleared.
Related documentation

​
DPE-2229 — The dataset has neither batch nor streaming settings

A dataset has to say where its data comes from — a batch source, a streaming source, or both. This configuration says neither, so it was rejected. User correctable — you can correct this. What to do
  1. Open the Configuration tab, choose Edit, and add the batch or streaming section, then use Validate.
  2. If you are creating the dataset, go back to Select Data Source — the choice there is what fills this in.
  3. A dataset that ingests both keeps both sections; removing one is only correct if that half is genuinely unused.
Related documentation

​
DPE-2230 — The time column is not in the schema

The table config uses {column} as its time column, but the schema has no field with that name, so the dataset could not be saved. User correctable — you can correct this. What to do
  1. On the Schema Config step, add a field named {column} with fieldType DATE_TIME.
  2. Or change timeColumnName in the table config to a DATE_TIME field the schema already has.
  3. The name has to match exactly, including case and underscores.
Related documentation

​
DPE-2231 — The star-tree index names a column that is not there

The star-tree index lists {column} as a dimension, but the schema has no column with that name, so the dataset could not be saved. User correctable — you can correct this. What to do
  1. On the Data Modeling step, add a column named {column}, or remove it from the star-tree index.
  2. Derived time columns such as __timeDAY have to exist as real schema fields before an index can reference them.
  3. The name has to match exactly, including case and any $ separators.

​
DPE-2232 — The schema is missing a column the table config uses

The table config for {table} refers to {column}, and the schema does not define it, so the two could not be saved together. User correctable — you can correct this. What to do
  1. On the Schema Config step, add a column named {column}.
  2. Or edit the table config so it no longer refers to {column}.
  3. Schema and table config are validated as a pair, so a name in one must exist in the other.

​
DPE-2233 — The dataset is larger than a dimension table may be

A dimension table is held in memory on every server, so it has a size ceiling. This dataset asks for {requested} bytes against a limit of {allowed}. User correctable — you can correct this. What to do
  1. Create this dataset as a regular OFFLINE or REALTIME table rather than a dimension table.
  2. Or reduce the data so it fits the limit — dimension tables are meant for small lookup sets.
  3. Ask StarTree support if the ceiling needs raising for this workspace.

​
DPE-2234 — Every column needs raw encoding

An external table stores its own data, so every column has to be read without a dictionary. These columns have no encoding set and would default to a dictionary: {columns}. User correctable — you can correct this. What to do
  1. Generate the configuration from the source rather than writing it by hand — the preview step fills in the encoding for every column.
  2. If you are editing the configuration directly, add a field config with raw encoding for each column listed.
  3. A sorted index cannot be used on an external table either, so remove one if the configuration sets it.
Related documentation

​
DPE-2235 — A transform expression could not be read

The expression set on {column} could not be parsed, so the configuration was rejected and nothing was changed. User correctable — you can correct this. What to do
  1. Open the column on the Data Modeling step and check its Transformation for a stray quote or bracket — an unbalanced one is the usual cause.
  2. Function names take their arguments in parentheses, even when there are none.
  3. Preview the rows after fixing it; the sample is evaluated through the same expression.
Related documentation

​
DPE-2236 — A transform writes to a column that is not there

The transform writes to {column}, which is not one of this dataset’s columns and is not consumed by another transform, so the value would have nowhere to go. User correctable — you can correct this. What to do
  1. Add {column} to the dataset on the Data Modeling step, or point the transform at a column that already exists.
  2. The destination has to be spelled exactly as the column is, including case.
Related documentation

​
DPE-2237 — That dataset name is already taken

A dataset with this name already exists in the workspace, so it could not be recorded a second time. User correctable — you can correct this. What to do
  1. Choose a different name for the new dataset.
  2. If you are re-creating one you just deleted, wait for the removal to finish and try again — the name is released only when it completes.
Related documentation

​
DPE-2238 — The schema was missing from the request

The table configuration could not be worked out because the request carried no schema for the new dataset. User correctable — you can correct this. What to do
  1. Go back to the schema step, confirm the columns, and continue again so the schema is sent.
  2. If you are calling the API directly, send the Pinot schema together with its column mappings in the schema value, not on its own.