Hi Danny, I looked at your design proposal and it looks great. All common hint cases that we may possibly need are covered there. Thank you.
I hope the community will release it soon since hints are essential for production-grade systems. From what I see in other projects, such as Flink or Drill, they have to rely on properties set somewhere else (configuration, session), to achieve the same goals, which is not user-friendly. Regards, Vladimir. пн, 28 окт. 2019 г. в 13:26, Danny Chan <[email protected]>: > Here is the discussion mailing list [1] > > [1] > https://ponymail-vm.apache.org/_GUI_/thread.html/db3799d70232ec85e294bb8885431a3f5c88bb28f4fd3337368b1480@%3Cdev.calcite.apache.org%3E > > Best, > Danny Chan > 在 2019年10月28日 +0800 PM5:09，Vladimir Ozerov <[email protected]>，写道： > > Hi colleagues, > > > > I am working on Calcite integration with Hazelcast. One particular > problem > > is that we need query hints. I found a couple of tickets [1] [2], and it > > seems that hints are not readily available at the moment. So I have two > > questions: > > 1) Is it true that there is no built-in way to provide query hints at the > > moment? Are there any plans to finally add hints to the engine? > > 2) As a possible solution, I am considering extending SELECT syntax with > a > > custom parser extension. Do you know any example of extended SELECT > syntax > > in existing Calcite integrations? I found an example of SqlInsert command > > extension in Apache Flink, but maybe somebody already extended SELECT as > > well? > > > > Thank you, > > Vladimir. > > > > [1] https://issues.apache.org/jira/browse/CALCITE-482 > > [2] https://issues.apache.org/jira/browse/CALCITE-495 >
