Indeed. But as I said on this list a while ago, it’s simpler for our users and more efficient for everyone if questions are asked and answered on StackOverflow. An answer on SO will be seen by many more people than an answer on the dev list, and it much more likely to be found by a google search, and unlike an answer on the list, it will be refined and corrected over time.
So, we should not discourage people asking questions there. We, the Calcite community, should be endeavoring to answer questions on SO as they come up*, and this will have the effect of growing the community. Julian * Yeah, I know we’re all really busy. > On Apr 10, 2016, at 8:51 PM, Josh Elser <[email protected]> wrote: > > You can always ask questions directly on this mailing list, Kostas. > > Now that you mentioned them here, someone will probably try to take a look. > > Konstantinos Kougios wrote: >> Hi, I've posted a couple of calcite related questions on stack overflow >> a couple of weeks ago. Unfortunately I didn't get any responses yet. >> >> What is the best way to get some help? >> >> http://stackoverflow.com/questions/36283160/apache-calcite-querying-without-using-the-jdbc-api >> >> >> http://stackoverflow.com/questions/36219953/how-to-avoid-calcite-doing-aggregations-in-memory >> >> >> http://stackoverflow.com/questions/36219910/calcite-id-filters-what-is-the-easiest-way-to-get-them >> >> >> Also an other question I got is if calcite supports DDL (create table) >> and insert/upserts. It seems apache phoenix does that ( and if I am >> correct it uses calcite). I get an exception when I try it. >> >> Thanks, >> >> Kostas
