[jira] [Commented] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339703#comment-16339703 ] Maryann Xue commented on CALCITE-1054: -- Fixed in master branch: # Avoid using Lists.transform()

[jira] [Commented] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338860#comment-16338860 ] Maryann Xue commented on CALCITE-1054: -- [~julianhyde], it was caused by: {code:java}

[jira] [Commented] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338383#comment-16338383 ] Maryann Xue commented on CALCITE-1054: -- Sure, I'll take a look. Thank you for the debug

[jira] [Comment Edited] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324587#comment-16324587 ] Maryann Xue edited comment on CALCITE-1054 at 1/12/18 9:45 PM: --- After

[jira] [Commented] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324587#comment-16324587 ] Maryann Xue commented on CALCITE-1054: -- After verifying CALCITE-1118 along with CALCITE-1427 and

[jira] [Commented] (CALCITE-1054) NPE caused by wrong code generation for Timestamp fields

[ https://issues.apache.org/jira/browse/CALCITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323517#comment-16323517 ] Maryann Xue commented on CALCITE-1054: -- Could you please review this PR

[jira] [Resolved] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1941. -- Resolution: Fixed Fixed in

[jira] [Commented] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147866#comment-16147866 ] Maryann Xue commented on CALCITE-1941: -- Committed changes in PR. I removed

[jira] [Commented] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146449#comment-16146449 ] Maryann Xue commented on CALCITE-1941: -- "isBefore" sounds good. I'll change the description

[jira] [Updated] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1941: - Description: The current Schema#snapshot(long timestamp) interface is limited, for it assumes

[jira] [Updated] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1941: - Description: The current Schema#snapshot(long timestamp) interface is limited, for it assumes

[jira] [Commented] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146053#comment-16146053 ] Maryann Xue commented on CALCITE-1941: -- Sorry, [~julianhyde], for my late response on this issue.

[jira] [Commented] (CALCITE-1966) Support for normal views to act as materialization table

[ https://issues.apache.org/jira/browse/CALCITE-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142970#comment-16142970 ] Maryann Xue commented on CALCITE-1966: -- Thank you for your quick response, [~cbeikov]! I think

[jira] [Commented] (CALCITE-1966) Support for normal views to act as materialization table

[ https://issues.apache.org/jira/browse/CALCITE-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142947#comment-16142947 ] Maryann Xue commented on CALCITE-1966: -- I think using qualified name instead of RelOptTable in

[jira] [Commented] (CALCITE-1941) Refine interface Schema#snapshot()

[ https://issues.apache.org/jira/browse/CALCITE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126605#comment-16126605 ] Maryann Xue commented on CALCITE-1941: -- [~julianhyde], could you please review

[jira] [Created] (CALCITE-1941) Refine interface Schema#snapshot()

Maryann Xue created CALCITE-1941: Summary: Refine interface Schema#snapshot() Key: CALCITE-1941 URL: https://issues.apache.org/jira/browse/CALCITE-1941 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-1742) Create a read-consistent view of CalciteSchema for each statement compilation

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997591#comment-15997591 ] Maryann Xue commented on CALCITE-1742: -- [~julianhyde], [~jni], Could you please take a look at

[jira] [Updated] (CALCITE-1742) Create a read-consistent view of CalciteSchema for each statement compilation

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1742: - Summary: Create a read-consistent view of CalciteSchema for each statement compilation (was:

[jira] [Commented] (CALCITE-1748) Make CalciteCatalogReader.getSchema extendable to support dynamically load schema tree - getSchema need to be set to protected to allow overriding

[ https://issues.apache.org/jira/browse/CALCITE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977358#comment-15977358 ] Maryann Xue commented on CALCITE-1748: -- So basically once we have a read consistency layer inside

[jira] [Comment Edited] (CALCITE-1748) Make CalciteCatalogReader.getSchema extendable to support dynamically load schema tree - getSchema need to be set to protected to allow overriding

[ https://issues.apache.org/jira/browse/CALCITE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977358#comment-15977358 ] Maryann Xue edited comment on CALCITE-1748 at 4/20/17 8:01 PM: --- So

[jira] [Commented] (CALCITE-1748) Make CalciteCatalogReader.getSchema extendable to support dynamically load schema tree - getSchema need to be set to protected to allow overriding

[ https://issues.apache.org/jira/browse/CALCITE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977238#comment-15977238 ] Maryann Xue commented on CALCITE-1748: -- bq. Calcite has the assumption that a full schema tree is

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965211#comment-15965211 ] Maryann Xue commented on CALCITE-1742: -- bq. So, then the question is: How burdensome is for the

[jira] [Comment Edited] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965146#comment-15965146 ] Maryann Xue edited comment on CALCITE-1742 at 4/11/17 11:46 PM: Thank

[jira] [Comment Edited] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965146#comment-15965146 ] Maryann Xue edited comment on CALCITE-1742 at 4/11/17 11:45 PM: Thank

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965146#comment-15965146 ] Maryann Xue commented on CALCITE-1742: -- Thank you, [~jni], for the feedback! bq. I have one

[jira] [Comment Edited] (CALCITE-1050) Avatica can't serialize java.sql.Array

[ https://issues.apache.org/jira/browse/CALCITE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964919#comment-15964919 ] Maryann Xue edited comment on CALCITE-1050 at 4/11/17 8:29 PM: --- Not sure,

[jira] [Commented] (CALCITE-1050) Avatica can't serialize java.sql.Array

[ https://issues.apache.org/jira/browse/CALCITE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964919#comment-15964919 ] Maryann Xue commented on CALCITE-1050: -- Not sure, but I think other than {{createArrayOf}},

[jira] [Commented] (CALCITE-1050) Avatica can't serialize java.sql.Array

[ https://issues.apache.org/jira/browse/CALCITE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964742#comment-15964742 ] Maryann Xue commented on CALCITE-1050: -- Thank you very much for doing the Array support, [~elserj]!

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964632#comment-15964632 ] Maryann Xue commented on CALCITE-1742: -- I just realized that solution 2 was not right. If we had to

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963875#comment-15963875 ] Maryann Xue commented on CALCITE-1742: -- [~jni] and [~julianhyde], could you please take a look at

[jira] [Comment Edited] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961102#comment-15961102 ] Maryann Xue edited comment on CALCITE-1742 at 4/7/17 4:51 PM: -- bq. Do we

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961102#comment-15961102 ] Maryann Xue commented on CALCITE-1742: -- bq. Do we know why the TableEntry found in schema could not

[jira] [Commented] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959938#comment-15959938 ] Maryann Xue commented on CALCITE-1742: -- Thank you, [~jni], for pressing me on the details! I first

[jira] [Updated] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1742: - Description: {{CalciteSchema}} is designed to have two sets of objects, the explicit and the

[jira] [Updated] (CALCITE-1742) CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit table map

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1742: - Summary: CalciteCatalogReader should not add resolved tables into CalciteSchema's explicit

[jira] [Comment Edited] (CALCITE-1742) Avoid caching sub-objects from CalciteSchema if caching is not enabled

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959924#comment-15959924 ] Maryann Xue edited comment on CALCITE-1742 at 4/6/17 10:51 PM: --- bq. From

[jira] [Commented] (CALCITE-1742) Avoid caching sub-objects from CalciteSchema if caching is not enabled

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959847#comment-15959847 ] Maryann Xue commented on CALCITE-1742: -- Sorry, the description was a little inaccurate. In fact, I

[jira] [Created] (CALCITE-1742) Avoid caching sub-objects from CalciteSchema if caching is not enabled

Maryann Xue created CALCITE-1742: Summary: Avoid caching sub-objects from CalciteSchema if caching is not enabled Key: CALCITE-1742 URL: https://issues.apache.org/jira/browse/CALCITE-1742 Project:

[jira] [Updated] (CALCITE-1742) Avoid caching sub-objects from CalciteSchema if caching is not enabled

[ https://issues.apache.org/jira/browse/CALCITE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1742: - Description: We have two implementations of CalciteSchema, {{CachingCalciteSchema}} and

[jira] [Commented] (CALCITE-1693) Pig adapter test runs slowly

[ https://issues.apache.org/jira/browse/CALCITE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925139#comment-15925139 ] Maryann Xue commented on CALCITE-1693: -- Tried that option, the time spent on Pig component build

[jira] [Commented] (CALCITE-1688) Query containing set operations (UNION/MINUS/INTERSECT) would cause infinite loop in materialization substitution

[ https://issues.apache.org/jira/browse/CALCITE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904145#comment-15904145 ] Maryann Xue commented on CALCITE-1688: -- Could you please take a look at

[jira] [Created] (CALCITE-1688) Query containing set operations (UNION/MINUS/INTERSECT) would cause infinite loop in materialization substitution

Maryann Xue created CALCITE-1688: Summary: Query containing set operations (UNION/MINUS/INTERSECT) would cause infinite loop in materialization substitution Key: CALCITE-1688 URL:

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902570#comment-15902570 ] Maryann Xue commented on CALCITE-1675: -- Could you please take a look at my latest commit on that

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902178#comment-15902178 ] Maryann Xue commented on CALCITE-1675: -- Can I go further to remove {{findQualifyingTableName}}

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902159#comment-15902159 ] Maryann Xue commented on CALCITE-1675: -- Think what we could do is to remove

[jira] [Issue Comment Deleted] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1675: - Comment: was deleted (was: Maybe not. {{findQualifyingTables}} is to find all matching tables

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902154#comment-15902154 ] Maryann Xue commented on CALCITE-1675: -- Maybe not. {{findQualifyingTables}} is to find all matching

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900745#comment-15900745 ] Maryann Xue commented on CALCITE-1675: -- Because I removed {{findQualifyingTables}} from its super

[jira] [Commented] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

[ https://issues.apache.org/jira/browse/CALCITE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900461#comment-15900461 ] Maryann Xue commented on CALCITE-1675: -- Could you please take a look at

[jira] [Created] (CALCITE-1675) Two-level column name cannot be resolved in ORDER BY

Maryann Xue created CALCITE-1675: Summary: Two-level column name cannot be resolved in ORDER BY Key: CALCITE-1675 URL: https://issues.apache.org/jira/browse/CALCITE-1675 Project: Calcite

[jira] [Resolved] (CALCITE-1637) Add mutable equivalents for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1637. -- Resolution: Fixed Thank you, [~julianhyde], for the review! Fixed in

[jira] [Updated] (CALCITE-1637) Add mutable equivalents for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1637: - Summary: Add mutable equivalents for all relational expressions (was: Add missing MutableRels

[jira] [Commented] (CALCITE-1637) Add missing MutableRels for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875480#comment-15875480 ] Maryann Xue commented on CALCITE-1637: -- Could you please take a look at

[jira] [Comment Edited] (CALCITE-1637) Add missing MutableRels for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869416#comment-15869416 ] Maryann Xue edited comment on CALCITE-1637 at 2/16/17 7:41 AM: --- The

[jira] [Commented] (CALCITE-1637) Add missing MutableRels for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869416#comment-15869416 ] Maryann Xue commented on CALCITE-1637: -- The problem is that mutable rels are now only used by

[jira] [Updated] (CALCITE-1637) Add missing MutableRels for all relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1637: - Summary: Add missing MutableRels for all relational expressions (was: Add missing MutableRels

[jira] [Commented] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860134#comment-15860134 ] Maryann Xue commented on CALCITE-1500: -- Created and committed in a separate JIRA CALCITE-1628 for

[jira] [Resolved] (CALCITE-1628) Add an alternative match pattern for SemiJoinRule

[ https://issues.apache.org/jira/browse/CALCITE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1628. -- Resolution: Fixed Fixed in

[jira] [Updated] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1500: - Attachment: CALCITE-1500-fix2.patch Thank you, [~julianhyde], for the nice feedback! Just

[jira] [Commented] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857013#comment-15857013 ] Maryann Xue commented on CALCITE-1500: -- bq. It's cosmetic, but rather than creating a hasProject

[jira] [Updated] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1500: - Attachment: CALCITE-1500-fix.patch [~julianhyde], {{SemiJoinRule}} did not fire because the

[jira] [Commented] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855084#comment-15855084 ] Maryann Xue commented on CALCITE-1500: -- Yes, I'll take a look right away. I verified all the tests

[jira] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

Title: Message Title Maryann Xue resolved as Fixed

[jira] (CALCITE-1500) Decouple materialization and lattice substitution from VolcanoPlanner

Title: Message Title Maryann Xue updated an issue

[jira] (CALCITE-1500) Allow materialization-applied rels to run pre-processing programs

Title: Message Title Maryann Xue commented on CALCITE-1500

[jira] [Commented] (CALCITE-1549) Improve error message when table or column not found

[ https://issues.apache.org/jira/browse/CALCITE-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843533#comment-15843533 ] Maryann Xue commented on CALCITE-1549: -- Oh, I see. We'll apply a fix on Phoenix side then, and

[jira] [Commented] (CALCITE-1549) Improve error message when table or column not found

[ https://issues.apache.org/jira/browse/CALCITE-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843487#comment-15843487 ] Maryann Xue commented on CALCITE-1549: -- [~julianhyde], could you please look at

[jira] [Commented] (CALCITE-1549) Improve error message when table or column not found

[ https://issues.apache.org/jira/browse/CALCITE-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843453#comment-15843453 ] Maryann Xue commented on CALCITE-1549: -- I'm looking at it. Will submit a patch soon. > Improve

[jira] [Commented] (CALCITE-1500) Allow materialization-applied rels to run pre-processing programs

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840624#comment-15840624 ] Maryann Xue commented on CALCITE-1500: -- [~julianhyde], I just committed changes to the PR, based on

[jira] [Commented] (CALCITE-1500) Allow materialization-applied rels to run pre-processing programs

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838597#comment-15838597 ] Maryann Xue commented on CALCITE-1500: -- Yes, we can. So how about I make "materializations and

[jira] [Commented] (CALCITE-1536) Initialize cluster before planner

[ https://issues.apache.org/jira/browse/CALCITE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838595#comment-15838595 ] Maryann Xue commented on CALCITE-1536: -- I like option 2 too, the reason I did it the other way was

[jira] [Commented] (CALCITE-1500) Allow materialization-applied rels to run pre-processing programs

[ https://issues.apache.org/jira/browse/CALCITE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838496#comment-15838496 ] Maryann Xue commented on CALCITE-1500: -- Thank you very much for the feedback, [~julianhyde]! I just

[jira] [Commented] (CALCITE-1536) Initialize cluster before planner

[ https://issues.apache.org/jira/browse/CALCITE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838474#comment-15838474 ] Maryann Xue commented on CALCITE-1536: -- I'm having slightly different thoughts. Once we can have

[jira] [Resolved] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

[ https://issues.apache.org/jira/browse/CALCITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1571. -- Resolution: Fixed Fix Version/s: 1.12.0 Thank you, [~julianhyde], for the review!

[jira] [Commented] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

[ https://issues.apache.org/jira/browse/CALCITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819527#comment-15819527 ] Maryann Xue commented on CALCITE-1571: -- {{addImplicitFuncNamesToBuilder}} is called by

[jira] [Commented] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

[ https://issues.apache.org/jira/browse/CALCITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819412#comment-15819412 ] Maryann Xue commented on CALCITE-1571: -- Just made another check-in to that pull request. [~jni] and

[jira] [Commented] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

[ https://issues.apache.org/jira/browse/CALCITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817252#comment-15817252 ] Maryann Xue commented on CALCITE-1571: -- I see. Thanks, [~jni]! Anyway, if we look at the code I

[jira] [Commented] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

[ https://issues.apache.org/jira/browse/CALCITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816721#comment-15816721 ] Maryann Xue commented on CALCITE-1571: -- [~julianhyde], could you please review this fix for me?

[jira] [Created] (CALCITE-1571) Could not resolve VIEW with SimpleCalciteSchema

Maryann Xue created CALCITE-1571: Summary: Could not resolve VIEW with SimpleCalciteSchema Key: CALCITE-1571 URL: https://issues.apache.org/jira/browse/CALCITE-1571 Project: Calcite Issue

[jira] [Comment Edited] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749842#comment-15749842 ] Maryann Xue edited comment on CALCITE-1499 at 12/14/16 11:39 PM: -

[jira] [Commented] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749842#comment-15749842 ] Maryann Xue commented on CALCITE-1499: -- Julian, I agree with you with the list of state in the

[jira] [Commented] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746457#comment-15746457 ] Maryann Xue commented on CALCITE-1499: -- Thank you for the review, [~julianhyde]! I added a test

[jira] [Commented] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744418#comment-15744418 ] Maryann Xue commented on CALCITE-1499: -- Sorry, I forgot to mention you, [~julianhyde]. > Exclude

[jira] [Resolved] (CALCITE-1534) Allow compound identifiers in INSERT target column list

[ https://issues.apache.org/jira/browse/CALCITE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1534. -- Resolution: Fixed Fix Version/s: 1.11.0 Fixed in

[jira] [Commented] (CALCITE-1534) Allow compound identifiers in INSERT target column list

[ https://issues.apache.org/jira/browse/CALCITE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743601#comment-15743601 ] Maryann Xue commented on CALCITE-1534: -- Thank you very much for the suggestions, [~julianhyde]!

[jira] [Created] (CALCITE-1534) Allow compound identifiers in INSERT/UPDATE target column list

Maryann Xue created CALCITE-1534: Summary: Allow compound identifiers in INSERT/UPDATE target column list Key: CALCITE-1534 URL: https://issues.apache.org/jira/browse/CALCITE-1534 Project: Calcite

[jira] [Commented] (CALCITE-1524) Add a project to the planner root so that rules know which output fields are used

[ https://issues.apache.org/jira/browse/CALCITE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730268#comment-15730268 ] Maryann Xue commented on CALCITE-1524: -- [~julianhyde], your fix has broken something: Try: {code}

[jira] [Commented] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730211#comment-15730211 ] Maryann Xue commented on CALCITE-1499: -- Could you please kindly review

[jira] [Updated] (CALCITE-1499) Exclude VolcanoPlanner's "originalRoot" from default planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1499: - Summary: Exclude VolcanoPlanner's "originalRoot" from default planning process (was: Add an

[jira] [Resolved] (CALCITE-1507) OFFSET cannot be pushed through a JOIN if the non-preserved side of outer join is not count-preserving

[ https://issues.apache.org/jira/browse/CALCITE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1507. -- Resolution: Fixed Fix Version/s: 1.11.0 Fixed in

[jira] [Commented] (CALCITE-1507) OFFSET cannot be pushed through a JOIN if the non-preserved side of outer join is not count-preserving

[ https://issues.apache.org/jira/browse/CALCITE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723361#comment-15723361 ] Maryann Xue commented on CALCITE-1507: -- Could you please kindly review my PR for this issue

[jira] [Resolved] (CALCITE-1425) Support two-level column structure in INSERT/UPDATE/MERGE

[ https://issues.apache.org/jira/browse/CALCITE-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved CALCITE-1425. -- Resolution: Fixed Fixed in

[jira] [Commented] (CALCITE-1425) Support two-level column structure in INSERT/UPDATE/MERGE

[ https://issues.apache.org/jira/browse/CALCITE-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706441#comment-15706441 ] Maryann Xue commented on CALCITE-1425: -- No. Every element in List is parallel to each other. The

[jira] [Created] (CALCITE-1508) SortJoinTransposeRule can remove the top Sort node if it is a trivial ORDER BY and the non-preserved side of the outer join is count-preserving

Maryann Xue created CALCITE-1508: Summary: SortJoinTransposeRule can remove the top Sort node if it is a trivial ORDER BY and the non-preserved side of the outer join is count-preserving Key: CALCITE-1508 URL:

[jira] [Created] (CALCITE-1507) OFFSET cannot be pushed through a JOIN if the non-preserved side of outer join is not count-preserving

Maryann Xue created CALCITE-1507: Summary: OFFSET cannot be pushed through a JOIN if the non-preserved side of outer join is not count-preserving Key: CALCITE-1507 URL:

[jira] [Commented] (CALCITE-1498) Avoid LIMIT with trivial ORDER BY being pushed through JOIN endlessly

[ https://issues.apache.org/jira/browse/CALCITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687723#comment-15687723 ] Maryann Xue commented on CALCITE-1498: -- bq. In that query, neither side is count-preserving. So I

[jira] [Updated] (CALCITE-1498) Avoid LIMIT with trivial ORDER BY being pushed through JOIN endlessly

[ https://issues.apache.org/jira/browse/CALCITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1498: - Description: Currently LIMIT with trivial ORDER BY will be pushed through a JOIN endlessly by

[jira] [Updated] (CALCITE-1498) Avoid LIMIT with trivial ORDER BY being pushed through JOIN endlessly

[ https://issues.apache.org/jira/browse/CALCITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated CALCITE-1498: - Summary: Avoid LIMIT with trivial ORDER BY being pushed through JOIN endlessly (was: Allow

[jira] [Commented] (CALCITE-1498) Allow LIMIT with trivial ORDER BY to be pushed through JOIN

[ https://issues.apache.org/jira/browse/CALCITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687640#comment-15687640 ] Maryann Xue commented on CALCITE-1498: -- Take this query as an example: {code} select d.deptno,

[jira] [Commented] (CALCITE-1499) Add an option to exclude VolcanoPlanner's "originalRoot" from planning process

[ https://issues.apache.org/jira/browse/CALCITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687506#comment-15687506 ] Maryann Xue commented on CALCITE-1499: -- I just tried it. Calling "RelOptPlanner.clear()" would do

  1   2   3   >