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
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
+1
On Mon, Mar 20, 2017 at 9:37 AM, Michael Mior wrote:
> +1 (non-binding)
>
> Checked hashes and signature of the tarball and compiled and ran tests.
>
> --
> Michael Mior
> michael.m...@gmail.com
>
> 2017-03-17 17:30 GMT-04:00 Julian Hyde :
>
> > Hi all,
> >
> > I have created a build for Apac
integration tests
> >> actually execute Pig. This seems like a less desirable option IMHO, as
> >> integration tests are not run on 'mvn install.'
> >>
> >> Thanks,
> >>
> >> Eli
> >>
> >> [1] https://developer.ibm.co
Here a Mac Pro with Comcast network connection (not much better than what
Julian has in a ski cabin maybe). Core build took 3:22 min, and Pig took
07:38 min.
On Mon, Mar 13, 2017 at 9:08 AM, Julian Hyde wrote:
> The env was a ski cabin. And as you know, ski cabins often have blunt
> knives, poor
me.
>
> Eli
>
> > On Mar 10, 2017, at 10:26 PM, Maryann Xue wrote:
> >
> > I was suspecting that too so removed "-DskipTests" option and tried again
> > with "mvn install", but still got the issue after all tests passed in the
> > &quo
ug, but it probably only happens
> with particular combinations of targets/flags.
>
> Julian
>
> > On Mar 10, 2017, at 3:21 PM, Jess Balint wrote:
> >
> > Being the last one to commit, it's fine for me. :) Maybe clean first?
> >
> > Jess
> >
> > O
Hi all,
Was trying to do 'mvn install' today but got an error as follows:
[ERROR] Failed to execute goal de.thetaphi:forbiddenapis:2.3:check
(default) on project calcite-core: Check for forbidden API calls failed:
java.lang.ClassNotFoundException:
org.apache.calcite.sql.parser.parserextensiontest
Maryann Xue created CALCITE-1688:
Summary: Query containing set operations (UNION/MINUS/INTERSECT)
would cause infinite loop in materialization substitution
Key: CALCITE-1688
URL: https://issues.apache.org/jira
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
Maryann Xue created CALCITE-1637:
Summary: Add missing MutableRels for all operators
Key: CALCITE-1637
URL: https://issues.apache.org/jira/browse/CALCITE-1637
Project: Calcite
Issue Type
Thank you Julian, for pointing this out! I'll fix it ASAP.
On Fri, Feb 10, 2017 at 11:08 AM Julian Hyde wrote:
> Maryann,
>
> Your code broke under newer versions of Guava. In Guava 21 or higher,
> which requires Java 8 or higher, Guava’s Predicate extends Java’s
> Predicate. Therefore you need t
Maryann Xue created CALCITE-1628:
Summary: Add an alternative match pattern for SemiJoinRule
Key: CALCITE-1628
URL: https://issues.apache.org/jira/browse/CALCITE-1628
Project: Calcite
Issue
Hi folks,
As many of you may be aware, we have been working on the integration
between Apache Calcite and Apache Phoenix, in which Calcite is going to
replace the existing standalone Phoenix's parser, validator and query
planner and Phoenix will continue to focus on runtime features and
execution
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
; communities. Welcome to the PMC, Maryann. Well deserved.
> >>
> >> Julian
> >>
> >>
> >> > On Jan 9, 2017, at 10:23 AM, James Taylor
> >> wrote:
> >> >
> >> > On behalf of the Apache Calcite PMC, I'm please
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
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
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: https://issues.apache.org/jira/browse
Maryann Xue created CALCITE-1500:
Summary: Allow materialization-applied rels to run pre-processing
programs
Key: CALCITE-1500
URL: https://issues.apache.org/jira/browse/CALCITE-1500
Project: Calcite
Maryann Xue created CALCITE-1499:
Summary: Add an option to exclude VolcanoPlanner's "originalRoot"
from planning process
Key: CALCITE-1499
URL: https://issues.apache.org/jira/brow
Maryann Xue created CALCITE-1498:
Summary: RelMdUtil.checkInputForCollationAndLimit() should also
consider input collations as a zero-length collation list.
Key: CALCITE-1498
URL: https://issues.apache.org/jira
Maryann Xue created CALCITE-1455:
Summary: Support customized star expansion in ViewTable
Key: CALCITE-1455
URL: https://issues.apache.org/jira/browse/CALCITE-1455
Project: Calcite
Issue
Maryann Xue created CALCITE-1431:
Summary: RelDataTypeFactoryImpl.copyType() did not copy StructKind
Key: CALCITE-1431
URL: https://issues.apache.org/jira/browse/CALCITE-1431
Project: Calcite
Maryann Xue created CALCITE-1426:
Summary: Support customized star expansion in RelDataType
Key: CALCITE-1426
URL: https://issues.apache.org/jira/browse/CALCITE-1426
Project: Calcite
Issue
Maryann Xue created CALCITE-1425:
Summary: Support two-level column structure in INSERT/UPDATE/MERGE
Key: CALCITE-1425
URL: https://issues.apache.org/jira/browse/CALCITE-1425
Project: Calcite
Maryann Xue created CALCITE-1415:
Summary: Add sub-query support for RelStructuredTypeFlattener
Key: CALCITE-1415
URL: https://issues.apache.org/jira/browse/CALCITE-1415
Project: Calcite
Maryann Xue created CALCITE-1379:
Summary: When expanding STAR, expand sub-fields in RecordType
columns of StructKind.PEEK_FIELDS and StructKind.PEEK_FIELDS_DEFAULT
Key: CALCITE-1379
URL: https
Maryann Xue created CALCITE-1378:
Summary: ArrayIndexOutOfBoundException in sql-to-rel conversion
for two-level columns
Key: CALCITE-1378
URL: https://issues.apache.org/jira/browse/CALCITE-1378
Maryann Xue created CALCITE-1374:
Summary: Support operator "!=" as an alternative to "<>"
Key: CALCITE-1374
URL: https://issues.apache.org/jira/browse/CALCITE-1374
Projec
Maryann Xue created CALCITE-1335:
Summary: ArrayImpl to return JDBC objects for method getArray()
Key: CALCITE-1335
URL: https://issues.apache.org/jira/browse/CALCITE-1335
Project: Calcite
Maryann Xue created CALCITE-1319:
Summary: Support bind variables in DDL
Key: CALCITE-1319
URL: https://issues.apache.org/jira/browse/CALCITE-1319
Project: Calcite
Issue Type: Improvement
Maryann Xue created CALCITE-1278:
Summary: CalciteSignature's ColumnMetaData info is wrong for DELETE
Key: CALCITE-1278
URL: https://issues.apache.org/jira/browse/CALCITE-1278
Project: Ca
Maryann Xue created CALCITE-1268:
Summary: Union should apply explicit Project over its children if
they have different but coercible types
Key: CALCITE-1268
URL: https://issues.apache.org/jira/browse/CALCITE
Maryann Xue created CALCITE-1228:
Summary: INSERT/UPSERT with values as bind parameters throws
exception in SqlValidator
Key: CALCITE-1228
URL: https://issues.apache.org/jira/browse/CALCITE-1228
Maryann Xue created CALCITE-1208:
Summary: Improve two-level column structure handling
Key: CALCITE-1208
URL: https://issues.apache.org/jira/browse/CALCITE-1208
Project: Calcite
Issue Type
Hi,
Phoenix has a two-level column structure for its tables, first level being
column families and second being columns under each family. We tried
modeling column families as of STRUCT types and columns as fields in their
corresponding STRUCT types. We have now passed parsing and validation, and
Hi Josh,
Thank you for reminding me! I have just pushed in another commit to fix the
javadoc problems.
Thanks,
Maryann
On Thu, Apr 7, 2016 at 4:24 PM, Josh Elser wrote:
> Maryann,
>
> ICYMI, your commit on CALCITE-1182 had some javadoc issues.
>
>
> Apache Jenkins Server wrote:
>
>> The Apach
Maryann Xue created CALCITE-1182:
Summary: Add ProjectRemoveRule to pre-processing program of
materialization substitution
Key: CALCITE-1182
URL: https://issues.apache.org/jira/browse/CALCITE-1182
Maryann Xue created CALCITE-1169:
Summary: Memory leak caused by CALCITE-604 and CALCITE-1147
Key: CALCITE-1169
URL: https://issues.apache.org/jira/browse/CALCITE-1169
Project: Calcite
Issue
Maryann Xue created CALCITE-1165:
Summary: VocanoCost comparing floating point numbers might cause
problems in a few places
Key: CALCITE-1165
URL: https://issues.apache.org/jira/browse/CALCITE-1165
Looks like there might be some memory leak in Phoenix test cases with
Calcite master. I'll figure out which CI exactly caused the issue. And if
anyone knows any suspect, please let me know.
Thanks,
Maryann
On Thu, Mar 17, 2016 at 1:22 PM, Julian Hyde wrote:
> I see that the avatica-1.7.1 vote
you.
>
> Julian
>
>
>
> On Wed, Mar 9, 2016 at 2:23 PM, Maryann Xue wrote:
> > Hi all,
> >
> > I had trouble dealing with the latest change in metadata provider:
> >
> https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commitdiff;h=d14040c52f8b
Hi all,
I had trouble dealing with the latest change in metadata provider:
https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commitdiff;h=d14040c52f8b0bc351443cff1584e8b587378698.
After modifying the Phoenix metadata classes to adapt to the interface
change, I got several exceptions. Am st
Hi Chengxiang,
A simple answer is "no" to question #2. Would you mind sharing your test
cases? It could sometimes be tricky playing with the VolcanoPlanner. My
experience is 1) the final plan you see in which the rule(s) have not taken
effect does not mean the rule(s) are not fired. Did you try se
7;ve understood your problem correctly.
>
>
> On Thu, Feb 25, 2016 at 10:16 PM Maryann Xue
> wrote:
>
> > Hi Michael,
> >
> > We had a little difficulty defining our secondary indices as materialized
> > views with our Schema SPI implementation too, and this m
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 in
let us know what you find… this is the perfect time to find & fix
> > such problems.
> > >
> > > You might find it useful to try against Calcite just before 816 and 794
> > were committed. Those were both big changes.
> > >
> > > Julian
> > &g
t; > OK, let us know what you find… this is the perfect time to find & fix
> such problems.
> >
> > You might find it useful to try against Calcite just before 816 and 794
> were committed. Those were both big changes.
> >
> > Julian
> >
> >> On Jan 11,
Having some problems with Calcite-Phoenix here. Still trying to identify...
Thanks,
Maryann
On Mon, Jan 11, 2016 at 10:03 PM, Josh Elser wrote:
> ACK'ed
>
> Julian Hyde wrote:
>
>> I just pushed 1.6.0-SNAPSHOT to Apache; it’s based on
>> https://github.com/apache/calcite/commit/78973eca94e81f7c
I'd like to be part of it, for anything it takes, discussion, review, code
contribution, whatever.
Thanks,
Maryann
On Sun, Dec 13, 2015 at 8:13 PM, Julian Hyde wrote:
> tl;dr: Please can at least one person from Drill, Hive, Phoenix, and
> any other interested stakeholders, review and join the
n 11/8/15, 3:31 PM, "Jacques Nadeau" wrote:
>>>
>>> Welcome Josh!
>>>>
>>>> On Sun, Nov 8, 2015 at 2:20 PM, Julian Hyde wrote:
>>>>
>>>> On behalf of the PMC I am delighted to announce Josh Elser as a new
>>>>
t;Josh Elser" wrote:
>
> >Congrats, Maryann!
> >
> >Julian Hyde wrote:
> >> On behalf of the PMC I am delighted to announce Maryann Xue as a new
> >> Calcite committer.
> >>
> >> Maryann (and Josh Elser announced in a separate message
4, 2015 at 2:13 PM, Maryann Xue wrote:
> Hi,
>
> I just became aware of this requirement in Phoenix using Calcite last week
> that for some Phoenix tables, we'd like to have two slightly different
> table scan strategies, "ordered" vs. "unordered", the
Hi,
I just became aware of this requirement in Phoenix using Calcite last week
that for some Phoenix tables, we'd like to have two slightly different
table scan strategies, "ordered" vs. "unordered", the latter of which does
not guarantee primary key of the returned rows but can be significantly
f
tion last week.
>>>>>
>>>>> I am tracking an issue in RelFieldTrimmer that I have detected in Hive
>>>>> QA run (seems related to Aggregate operators and grouping sets treatment).
>>>>> I will post another update asap.
>>>&g
lemented ArchiveEnumerableSort.
>
> Should it work as I expect, or there is something other that I need to do?
>
> On Sat, Oct 31, 2015 at 3:26 AM, Maryann Xue
> wrote:
> > Oh, it's not on master branch yet. It's the "calcite" branch, and for
> > PhoenixTa
1f32fda6c59a;hb=refs/heads/calcite
.
On Fri, Oct 30, 2015 at 4:36 PM, Alexander Reshetov <
alexander.v.reshe...@gmail.com> wrote:
> Could you please point me to PhoenixTable in repo? Unfortunately I
> could not find it.
>
> On Fri, Oct 30, 2015 at 10:33 PM, Maryann Xue
> wrot
Think having another physical TableScan operator, say,
"PhoenixTableScanUnordered" should be enough to solve this problem. But I'm
just curious, James, why is there such a big performance difference?
On Fri, Oct 30, 2015 at 12:36 PM, Maryann Xue wrote:
> I see, James. Think
And you also need to add that "collations" as a trait of the your
implementation of TableScan so that the planner will know.
On Fri, Oct 30, 2015 at 3:33 PM, Maryann Xue wrote:
> SortRemoveRule.INSTANCE is already in the default rule set. I think what
> you should do is just
SortRemoveRule.INSTANCE is already in the default rule set. I think what
you should do is just make your table return the right collation trait. For
example in Phoenix we have a Table implementation called PhoenixTable which
overrides getStatistic() and implements getCollations() of Statistic.
On
Anything
> > might be suspicious here?
> >
> >
> > Thanks,
> > Maryann
> >
> > On Thu, Oct 29, 2015 at 4:42 PM, Jacques Nadeau
> > wrote:
> >
> > > On the first point, in Drill we treat this as distributed and collated
> on
>
exchanges are used to
> redistribute data (or get it to the client node). Each exchange will
> maintain or not the specific traits.
>
> On Thu, Oct 29, 2015 at 9:02 AM, Maryann Xue
> wrote:
>
> > Hi,
> >
> > I have two questions regarding the Phoenix + Calc
Hi,
I have two questions regarding the Phoenix + Calcite integration:
1)
Phoenix has salted tables which add a hashed value "header" to the
beginning of the rowkey. Thus salted tables are hash partitioned but
maintains primary key order within each partition.
So question is how should we describe
64 matches
Mail list logo
