Hi,
Do you have to be a committer to be release manager.
Whats involved. I will volunteer anyway :-)
Michael.
On 08/25/2017 04:07 PM, Julian Hyde wrote:
It's about time we did a release. 1.13 was exactly 2 months ago.
Does anyone have any constraints on the release date? (Must be before
X,
Julian Hyde created CALCITE-1969:
Summary: Annotate user-defined functions as strict and semi-strict
Key: CALCITE-1969
URL: https://issues.apache.org/jira/browse/CALCITE-1969
Project: Calcite
It's about time we did a release. 1.13 was exactly 2 months ago.
Does anyone have any constraints on the release date? (Must be before
X, must be after Y?)
Any volunteers to be release manager?
Julian
On Fri, Aug 25, 2017 at 3:07 PM, LogSplitter wrote:
> Hello,
>
> I was wondering if there is
The Apache Jenkins build system has built Calcite-Master (build #100)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/100/ to
view the results.
Hello,
I was wondering if there is any estimated of when calcite 1.14 might be
released.
I am tossing up whether I use a patched version 1.13 release or wait a
little longer for real 1.14 for work I am needing to ship?
thanks
Michael
Julian Hyde created CALCITE-1968:
Summary: Support OpenGIS Simple Feature Access SQL
Key: CALCITE-1968
URL: https://issues.apache.org/jira/browse/CALCITE-1968
Project: Calcite
Issue Type: Bug
I already feel a responsibility for the Cassandra adapter since that's been
my primary contribution. Although it doesn't seem to be getting a lot of
use, I review any PR or JIRA that pops up for that.
--
Michael Mior
mm...@apache.org
2017-08-24 21:04 GMT-04:00 zhiqiang :
> I think we can assign
It apparently has something to do with MV substitutions as I couldn't
reproduce it in any other way than using a query that can be substituted
by an MV. Hard to say where the problem might be. Is there a specific
phase in the planning for this optimization that might not be triggered
anymore af
