RelDataType.isNullable() returns true if and only if the type is optional.
> On Feb 22, 2016, at 7:28 PM, Homer wrote:
>
> Julian,
>
> Thanks for the quick response.
>
> Sorry but I don't seem to see how I make the column optional. I am looking
> at RelDataType
I expected as much re: code documentation. Totally understandable, but I
figured it couldn't hurt to check.
As for Cassandra and materialized views, that's exactly what I was thinking
and the reason I opened the issue about updates to support Cassandra 3.x :)
Calcite's automatic rewriting seems
By the way, interesting that you are interested in Cassandra and
materialized views. Cassandra announced materialized view support
recently[1] but they solved only half of a problem (not an
insignificant half, I hasten to add), namely materialized view
maintenance. They don't transparently
As is typical for complex pieces of code like this, the documentation
is in the code (and the unit test). It's probably not what you wanted
to hear, but the code mutates quite fast and so if we'd written a
design doc a few months ago it would be partially inaccurate.
I, Maryann Xue and Amogh
Is there any documentation anywhere on how the current implementation of
query rewriting for materialized views work? Mostly I'm referring
to MaterializedViewSubstitutionVisitor. There's a lot of code to digest
with not a lot of documentation and it would be helpful to have a reference
to refer.
Hi Jesús,
Thank you very much for the response, I will check this out.
Best,
Victor
On Tue, Feb 23, 2016 at 2:27 PM, Jesus Camacho Rodriguez <
jcamachorodrig...@hortonworks.com> wrote:
> Hi Victor,
>
> The time taken to generate the optimize plan will depend on the size of
> the plan and the
I think both ideas are good to benefit from GSoC.
In particular, I proposed Piglet because it can give us a good baseline to test
different optimization techniques in the presence of reutilization of
intermediary results i.e. Spool operators.
As I am more familiar with Pig, I could create an