Ferix9288 opened a new issue, #11639:
URL: https://github.com/apache/pinot/issues/11639
For us, we utilize UUIDs as Pinot table names. V1 engine works and supports
it just fine but looks like V2 crashes and burns with the following error:
```
[
{
"message": "SQLParsingError:\nError composing query plan for: select *
from \"8593490b-01bf-46d4-a92c-bc270ac49aee\" limit
10\norg.apache.pinot.query.QueryEnvironment.planQuery(QueryEnvironment.java:182)\norg.apache.pinot.broker.requesthandler.MultiStageBrokerRequestHandler.handleRequest(MultiStageBrokerRequestHandler.java:125)\norg.apache.pinot.broker.requesthandler.BaseBrokerRequestHandler.handleRequest(BaseBrokerRequestHandler.java:263)\norg.apache.pinot.broker.requesthandler.BrokerRequestHandler.handleRequest(BrokerRequestHandler.java:48)\nCaught
exception while parsing query: SELECT * FROM
8593490b-01bf-46d4-a92c-bc270ac49aee_OFFLINE\norg.apache.pinot.sql.parsers.CalciteSqlParser.compileToSqlNodeAndOptions(CalciteSqlParser.java:144)\norg.apache.pinot.sql.parsers.CalciteSqlParser.compileToPinotQuery(CalciteSqlParser.java:186)\norg.apache.pinot.sql.parsers.CalciteSqlCompiler.compileToBrokerRequest(CalciteSqlCompiler.java:32)\norg.apache.pinot.query.routing.WorkerManager.get
RoutingTable(WorkerManager.java:207)\nEncountered \" \"FROM\" \"FROM \"\" at
line 1, column 10.\nWas expecting:\n <EOF> \n
\norg.apache.pinot.sql.parsers.parser.SqlParserImpl.generateParseException(SqlParserImpl.java:38633)\norg.apache.pinot.sql.parsers.parser.SqlParserImpl.jj_consume_token(SqlParserImpl.java:38430)\norg.apache.pinot.sql.parsers.parser.SqlParserImpl.SqlStmtsEof(SqlParserImpl.java:1033)\norg.apache.pinot.sql.parsers.CalciteSqlParser.compileToSqlNodeAndOptions(CalciteSqlParser.java:134)\n",
"errorCode": 150
}
]
```
Let me know if you guys need additional info. Also sorry if this is a dupe
but I couldn't find any similar issues
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
