Kishore G
Kishore G
Shreeram Goyal
01/30/2023, 10:25 AM[
{
"message": "SQLParsingError:\njava.lang.RuntimeException: Error composing query plan for: select * from order_items join orders on order_items.order_id=orders.id limit 10\n\tat org.apache.pinot.query.QueryEnvironment.planQuery(QueryEnvironment.java:137)\n\tat org.apache.pinot.broker.requesthandler.MultiStageBrokerRequestHandler.handleRequest(MultiStageBrokerRequestHandler.java:156)\n\tat org.apache.pinot.broker.requesthandler.MultiStageBrokerRequestHandler.handleRequest(MultiStageBrokerRequestHandler.java:131)\n\tat org.apache.pinot.broker.requesthandler.BrokerRequestHandler.handleRequest(BrokerRequestHandler.java:47)\n...\nCaused by: java.lang.UnsupportedOperationException: unsupported!\n\tat org.apache.pinot.query.type.TypeFactory.toRelDataType(TypeFactory.java:82)\n\tat org.apache.pinot.query.type.TypeFactory.createRelDataTypeFromSchema(TypeFactory.java:49)\n\tat org.apache.pinot.query.catalog.PinotTable.getRowType(PinotTable.java:49)\n\tat org.apache.calcite.sql.validate.EmptyScope.resolve_(EmptyScope.java:161)",
"errorCode": 150
}
]
I have followed the steps given in the doc but keep getting this error. The same issue was there in v0.11.0. I upgraded it but I am still facing the issue, please help me rectifying it.Rahul Patwari
04/24/2023, 9:26 AMfrancoisa
04/24/2023, 1:42 PMAddress already in us
on querry.runner port. As broker / controller and server are using the same machine. Is there any way to make it work on same machine ?Rahul Patwari
05/04/2023, 12:59 PMLewis Yobs
05/04/2023, 1:01 PMPeter Pringle
05/08/2023, 11:27 PMPratik Bhadane
05/09/2023, 1:43 PMKishore G
Shriniket Pimparkar
05/10/2023, 11:17 AMKishore G
Ehsan Irshad
05/23/2023, 7:13 AMDugi Sarma
06/09/2023, 11:33 PMRong R
06/10/2023, 12:24 AMDugi Sarma
07/13/2023, 4:06 AMYoav Nordmann
07/31/2023, 9:23 PMselect PERCENTILETDIGEST(feature_value, 5, 100) as p5
from numerical_features
Using the V2 Multi Stage Query Engine, and I get the following error:
ProcessingException(errorCode:450, message:InternalError:
java.lang.RuntimeException: Error composing query plan for: select PERCENTILETDIGEST(feature_value, 5, 100) as p5
from numerical_features
at org.apache.pinot.query.QueryEnvironment.getTableNamesForQuery(QueryEnvironment.java:242)
at org.apache.pinot.controller.api.resources.PinotQueryResource.getMultiStageQueryResponse(PinotQueryResource.java:204)
at org.apache.pinot.controller.api.resources.PinotQueryResource.executeSqlQuery(PinotQueryResource.java:170)
...
Caused by: org.apache.calcite.runtime.CalciteContextException: From line 1, column 8 to line 1, column 47: No match found for function signature PERCENTILETDIGEST(<NUMERIC>, <NUMERIC>, <NUMERIC>)
at jdk.internal.reflect.GeneratedConstructorAccessor161.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:505)
...
Caused by: org.apache.calcite.sql.validate.SqlValidatorException: No match found for function signature PERCENTILETDIGEST(<NUMERIC>, <NUMERIC>, <NUMERIC>)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490))
I understand that this function does not exist in the V2 engine, but what is its replacement ?Yoav Nordmann
08/03/2023, 8:05 PMselect $timestamp$HOUR
from categorical_features
limit 10
It works in the older query engine, but when enabling the V2 engine I receive the following error:
ProcessingException(errorCode:450, message:InternalError:
java.lang.RuntimeException: Error composing query plan for: select $timestamp$HOUR
from categorical_features limit 10
at org.apache.pinot.query.QueryEnvironment.getTableNamesForQuery(QueryEnvironment.java:241)
at org.apache.pinot.controller.api.resources.PinotQueryResource.getMultiStageQueryResponse(PinotQueryResource.java:204)
at org.apache.pinot.controller.api.resources.PinotQueryResource.executeSqlQuery(PinotQueryResource.java:170)
...
Caused by: org.apache.calcite.runtime.CalciteContextException: From line 1, column 8 to line 1, column 22: Column '$timestamp$HOUR' not found in any table
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
...
Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Column '$timestamp$HOUR' not found in any table
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490))
Is the timestamp index not supported in V2 Engine ?Yoav Nordmann
08/03/2023, 9:05 PMselect distinct "timestamp"
from numerical_features
I get the following error:
[
{
"errorCode": 200,
"message": "QueryExecutionError:\njava.lang.RuntimeException: Error executing query: [0]@pinot-broker-0.pinot-broker-headless.pinot.svc.cluster.local:32855 MAIL_RECEIVE(RANDOM_DISTRIBUTED)\n└── [1]@pinot-server-0.pinot-server-headless.pinot.svc.cluster.local:37275 MAIL_SEND(RANDOM_DISTRIBUTED)->{[0]@pinot-broker-0.pinot-broker-headless.pinot.svc.cluster.local@{32855,32855}|[0]}\n └── [1]@pinot-server-0.pinot-server-headless.pinot.svc.cluster.local:37275 AGGREGATE_FINAL\n └── [1]@pinot-server-0.pinot-server-headless.pinot.svc.cluster.local:37275 MAIL_RECEIVE(HASH_DISTRIBUTED)\n └── [2]@pinot-server-0.pinot-server-headless.pinot.svc.cluster.local:37275 MAIL_SEND(HASH_DISTRIBUTED)->{[1]@pinot-server-0.pinot-server-headless.pinot.svc.cluster.local@{37275,42193}|[0]}\n...\nCaused by: java.lang.RuntimeException: Received error query execution result block: {1000=class java.sql.Timestamp cannot be cast to class java.lang.Long (java.sql.Timestamp is in module java.sql of loader 'platform'; java.lang.Long is in module java.base of loader 'bootstrap')\njava.lang.ClassCastException: class java.sql.Timestamp cannot be cast to class java.lang.Long (java.sql.Timestamp is in module java.sql of loader 'platform'; java.lang.Long is in module java.base of loader 'bootstrap')\n\tat org.apache.pinot.common.utils.DataSchema$ColumnDataType.convert(DataSchema.java:354)\n\tat org.apache.pinot.query.runtime.operator.utils.TypeUtils.canonicalizeRow(TypeUtils.java:66)\n\tat org.apache.pinot.query.runtime.operator.MultistageGroupByExecutor.getResult(MultistageGroupByExecutor.java:131)"
}
]
Xiang Fu
vmarchaud
08/11/2023, 10:17 AMPeter Pringle
08/19/2023, 1:10 AMXiang Fu
Xiang Fu
Xiang Fu
Johan Adami
08/26/2023, 3:19 PMJohan Adami
08/26/2023, 3:21 PMAdd the following configurations to your cluster config
. This seems to be lacking. It took me hours to try to understand which needs to be set on servers vs brokers vs both. I ended adding them to the server and broker confs, not the global cluster configurations, but I can’t tell if the global cluster configs would even work.Johan Adami
08/26/2023, 3:23 PMpinot.query.runner.hostname
because our instance id is different from our hostname. I had to dig through logs to see dns resolution errors and find the config in code. Why do we need this config when we already have pinot.broker.hostname
?Johan Adami
08/26/2023, 3:24 PMpinot.multistage.engine.enabled=false
. But I noticed that running queries with useMultistageEngine=true
still works, it just silently uses the v1 engine under the hood. This seems like a problem since it’s not what the user requested, and the actual json response from the broker comes out differently. I would have expected the query to immediately failshubham mawle
08/29/2023, 5:10 PM