[
https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679378#comment-16679378
]
Vladimir Sitnikov commented on CALCITE-2662:
--------------------------------------------
Would you probably add a test case to
https://github.com/apache/calcite/blob/425fa7b7fb9cc02f5078e0696284176be0283fa3/ubenchmark/src/main/java/org/apache/calcite/benchmarks/ParserBenchmark.java
?
> Planner: allow parsing directly a stream instead of a java.lang.String
> ----------------------------------------------------------------------
>
> Key: CALCITE-2662
> URL: https://issues.apache.org/jira/browse/CALCITE-2662
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.17.0
> Reporter: Enrico Olivelli
> Assignee: Julian Hyde
> Priority: Major
>
> In 1.17.0 the org.apache.calcite.tools.Planner interface only accept a
> java.lang.String as input.
> In order to reduce memory allocations and copies it will be useful that the
> planner could accept the query in a more 'raw' format.
> Creating a java.lang.String is very expensive, and if your "query" is coming
> from the network (think about a Netty Direct memory ByteBuf) you are forced
> to create a copy of the text of the query.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
