[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14236677#comment-14236677 ] Julian Hyde commented on PHOENIX-971: - [~apurtell] for the record kylin is not molap

[jira] [Commented] (PHOENIX-1516) Add RANDOM built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244459#comment-14244459 ] Julian Hyde commented on PHOENIX-1516: -- [~jamestaylor] Oracle uses DBMS_RANDOM

[jira] [Commented] (PHOENIX-1516) Add RANDOM built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244484#comment-14244484 ] Julian Hyde commented on PHOENIX-1516: -- I see flaws in Oracle [

[jira] [Commented] (PHOENIX-1516) Add RANDOM built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14245842#comment-14245842 ] Julian Hyde commented on PHOENIX-1516: -- RAND without arguments seems to produce a

[jira] [Commented] (PHOENIX-1749) ORDER BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385083#comment-14385083 ] Julian Hyde commented on PHOENIX-1749: -- Ordinal positions have to be constants. Not

[jira] [Commented] (PHOENIX-1768) GROUP BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376752#comment-14376752 ] Julian Hyde commented on PHOENIX-1768: -- I'm pretty sure that GROUP BY ordinal is

[jira] [Commented] (PHOENIX-1768) GROUP BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377085#comment-14377085 ] Julian Hyde commented on PHOENIX-1768: -- An ordinary grouping set is typically

[jira] [Commented] (PHOENIX-1768) GROUP BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377103#comment-14377103 ] Julian Hyde commented on PHOENIX-1768: -- Microsoft SQL Server had a nice SQL

[jira] [Comment Edited] (PHOENIX-1768) GROUP BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377103#comment-14377103 ] Julian Hyde edited comment on PHOENIX-1768 at 3/24/15 2:04 AM:

[jira] [Commented] (PHOENIX-1768) GROUP BY should support column position as well as column alias

[ https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377230#comment-14377230 ] Julian Hyde commented on PHOENIX-1768: -- I am probably mistaken. Maybe it was only

[jira] [Commented] (PHOENIX-1878) Implement PhoenixSchema and PhoenixTable in Phoenix/Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505727#comment-14505727 ] Julian Hyde commented on PHOENIX-1878: -- PhoenixSchema.getTableNames is being called

[jira] [Commented] (PHOENIX-1879) Provide prepare statement hooks for Phoenix/Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505785#comment-14505785 ] Julian Hyde commented on PHOENIX-1879: -- In your driver, override

[jira] [Commented] (PHOENIX-1706) Create skeleton for parsing DDL

[ https://issues.apache.org/jira/browse/PHOENIX-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506417#comment-14506417 ] Julian Hyde commented on PHOENIX-1706: -- I have a basic implementation in

[jira] [Commented] (PHOENIX-1879) Provide prepare statement hooks for Phoenix/Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507726#comment-14507726 ] Julian Hyde commented on PHOENIX-1879: -- Yes, I see. The cluster hasn't even been

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538730#comment-14538730 ] Julian Hyde commented on PHOENIX-1954: -- [~lhofhansl], Would you consider it an

[jira] [Comment Edited] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538730#comment-14538730 ] Julian Hyde edited comment on PHOENIX-1954 at 5/11/15 10:07 PM:

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538624#comment-14538624 ] Julian Hyde commented on PHOENIX-1954: -- I've not seen it in any other DB, but the

[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481870#comment-14481870 ] Julian Hyde commented on PHOENIX-971: - bq. maybe the naming of the driver and it's

[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14395084#comment-14395084 ] Julian Hyde commented on PHOENIX-971: - For the last question, I logged CALCITE-663.

[jira] [Commented] (PHOENIX-1749) ORDER BY should support ordinal position as well as expression

[ https://issues.apache.org/jira/browse/PHOENIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487713#comment-14487713 ] Julian Hyde commented on PHOENIX-1749: -- [~maryannxue] Yes, that is what collations

[jira] [Comment Edited] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487694#comment-14487694 ] Julian Hyde edited comment on PHOENIX-971 at 4/9/15 5:21 PM: -

[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487694#comment-14487694 ] Julian Hyde commented on PHOENIX-971: - Just remember that if there are multiple JDBC

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694076#comment-14694076 ] Julian Hyde commented on PHOENIX-953: - [~maryannxue], That capability you refer to -

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694111#comment-14694111 ] Julian Hyde commented on PHOENIX-953: - I'm skeptical. It's hard to do de-correlation,

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682199#comment-14682199 ] Julian Hyde commented on PHOENIX-953: - By the way, Postgres' 'UNNEST' reminds me of

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682172#comment-14682172 ] Julian Hyde commented on PHOENIX-953: - Postgres implementation of UNNEST departs from

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695743#comment-14695743 ] Julian Hyde commented on PHOENIX-953: - * It seems that Derby does not support UNNEST

[jira] [Commented] (PHOENIX-914) Native HBase timestamp support to optimize date range queries in Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696034#comment-14696034 ] Julian Hyde commented on PHOENIX-914: - I like the idea of extending the meta-model to

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680809#comment-14680809 ] Julian Hyde commented on PHOENIX-953: - UNNEST produces a relation. So it can only be

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681203#comment-14681203 ] Julian Hyde commented on PHOENIX-953: - No, you can't use UNNEST in a SELECT clause

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693968#comment-14693968 ] Julian Hyde commented on PHOENIX-953: - There is no need for a version of UNNEST that

[jira] [Commented] (PHOENIX-2383) Implement Sequence in Phoenix/Calcite integration

[ https://issues.apache.org/jira/browse/PHOENIX-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007260#comment-15007260 ] Julian Hyde commented on PHOENIX-2383: -- You are correct. Calcite does not currently have "NEXT n

[jira] [Commented] (PHOENIX-2383) Implement Sequence in Phoenix/Calcite integration

[ https://issues.apache.org/jira/browse/PHOENIX-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007965#comment-15007965 ] Julian Hyde commented on PHOENIX-2383: -- I think the plan was that a sequence would be, from

[jira] [Commented] (PHOENIX-2383) Implement Sequence in Phoenix/Calcite integration

[ https://issues.apache.org/jira/browse/PHOENIX-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006204#comment-15006204 ] Julian Hyde commented on PHOENIX-2383: -- Yes, CALCITE-494. > Implement Sequence in Phoenix/Calcite

[jira] [Updated] (PHOENIX-1784) Port existing Phoenix optimizations to Phoenix/Calcite integration

[ https://issues.apache.org/jira/browse/PHOENIX-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated PHOENIX-1784: - Labels: calcite (was: ) > Port existing Phoenix optimizations to Phoenix/Calcite integration >

[jira] [Commented] (PHOENIX-1997) Join optimization: Apply one table's where condition to the others

[ https://issues.apache.org/jira/browse/PHOENIX-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14992275#comment-14992275 ] Julian Hyde commented on PHOENIX-1997: -- Calcite already does this: JoinPushTransitivePredicatesRule

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718041#comment-14718041 ] Julian Hyde commented on PHOENIX-953: - Go to https://en.wikipedia.org/wiki/SQL:2011

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715992#comment-14715992 ] Julian Hyde commented on PHOENIX-953: - I was wrong. I checked SQL-2011, and you can

[jira] [Commented] (PHOENIX-953) Support UNNEST for ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725843#comment-14725843 ] Julian Hyde commented on PHOENIX-953: - I don't have an opinion about whether key_expr would be

[jira] [Commented] (PHOENIX-2300) Support the use of secondary indexes in Drill

[ https://issues.apache.org/jira/browse/PHOENIX-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940401#comment-14940401 ] Julian Hyde commented on PHOENIX-2300: -- Phoenix introduces indexes into the plan via a planning

[jira] [Commented] (PHOENIX-2476) Use the standard string concatenation operator symbol

[ https://issues.apache.org/jira/browse/PHOENIX-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035001#comment-15035001 ] Julian Hyde commented on PHOENIX-2476: -- No, Calcite does not support string concatenation using

[jira] [Commented] (PHOENIX-2476) Recognize '+' and CONCAT as string concatenation operators

[ https://issues.apache.org/jira/browse/PHOENIX-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035092#comment-15035092 ] Julian Hyde commented on PHOENIX-2476: -- Amusing to see a similar discussion in the Drupal forums 6

[jira] [Comment Edited] (PHOENIX-2523) Use same client/server caching mechanism for Phoenix/Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057385#comment-15057385 ] Julian Hyde edited comment on PHOENIX-2523 at 12/15/15 5:47 AM: I can't

[jira] [Commented] (PHOENIX-2965) Use DistinctPrefixFilter logic for COUNT(DISTINCT ...) and COUNT(...) GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319776#comment-15319776 ] Julian Hyde commented on PHOENIX-2965: -- Agreed, composite distinct count (and indeed composite

[jira] [Commented] (PHOENIX-2965) Use DistinctPrefixFilter logic for COUNT(DISTINCT ...) and COUNT(...) GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317119#comment-15317119 ] Julian Hyde commented on PHOENIX-2965: -- Yes, Calcite does that. It can even handle multiple

[jira] [Commented] (PHOENIX-2702) Show estimate rows and bytes touched in explain plan.

[ https://issues.apache.org/jira/browse/PHOENIX-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157514#comment-15157514 ] Julian Hyde commented on PHOENIX-2702: -- Calcite returns EXPLAIN by default in text format (indented

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159419#comment-15159419 ] Julian Hyde commented on PHOENIX-2646: -- I'd only expect ANY and ALL to work for a small set of

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159279#comment-15159279 ] Julian Hyde commented on PHOENIX-2646: -- I don't know what "array ANY, ALL functions" are. > Extend

[jira] [Created] (PHOENIX-2693) More DDL

Julian Hyde created PHOENIX-2693: Summary: More DDL Key: PHOENIX-2693 URL: https://issues.apache.org/jira/browse/PHOENIX-2693 Project: Phoenix Issue Type: Sub-task Reporter:

[jira] [Commented] (PHOENIX-2693) More DDL

[ https://issues.apache.org/jira/browse/PHOENIX-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152708#comment-15152708 ] Julian Hyde commented on PHOENIX-2693: -- Ah, sorry. I linked PHOENIX-1706 to PHOENIX-2199 so they'd

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152828#comment-15152828 ] Julian Hyde commented on PHOENIX-2646: -- Calcite has {{SIMILAR TO}}, which is standard and (per the

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153188#comment-15153188 ] Julian Hyde commented on PHOENIX-2646: -- CALCITE-1066 is a work in progress. It would allow extra

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153191#comment-15153191 ] Julian Hyde commented on PHOENIX-2646: -- PS Yes standard SQL looks like FORTAN, I freely admit it.

[jira] [Commented] (PHOENIX-2646) Extend VARCHAR matching with ~ regex syntax

[ https://issues.apache.org/jira/browse/PHOENIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153427#comment-15153427 ] Julian Hyde commented on PHOENIX-2646: -- No quarrel with their user-defined types and functions

[jira] [Commented] (PHOENIX-2757) Phoenix Can't Coerce String to Boolean

[ https://issues.apache.org/jira/browse/PHOENIX-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188705#comment-15188705 ] Julian Hyde commented on PHOENIX-2757: -- If I recall correctly, Oracle will automatically coerce

[jira] [Commented] (PHOENIX-2757) Phoenix Can't Coerce String to Boolean

[ https://issues.apache.org/jira/browse/PHOENIX-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190262#comment-15190262 ] Julian Hyde commented on PHOENIX-2757: -- [~ndimiduk], I believe that, for a parameter of any data

[jira] [Moved] (PHOENIX-2767) Support columns for IN list

[ https://issues.apache.org/jira/browse/PHOENIX-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde moved CALCITE-1155 to PHOENIX-2767: --- Affects Version/s: (was: 1.5.0) Component/s:

[jira] [Commented] (PHOENIX-2767) Support columns for IN list

[ https://issues.apache.org/jira/browse/PHOENIX-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15194415#comment-15194415 ] Julian Hyde commented on PHOENIX-2767: -- Yes, I think so. > Support columns for IN list >

[jira] [Commented] (PHOENIX-2228) Support CREATE TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201727#comment-15201727 ] Julian Hyde commented on PHOENIX-2228: -- [~rajeshbabu], WIP patch looks good. In addition to the IT,

[jira] [Commented] (PHOENIX-2794) Flatten nested aggregate queries when possible

[ https://issues.apache.org/jira/browse/PHOENIX-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15213760#comment-15213760 ] Julian Hyde commented on PHOENIX-2794: -- Calcite does not, but it could, for MIN, MAX, SUM. (Or any

[jira] [Commented] (PHOENIX-2845) Timestamp ignores nanos in literal expressions

[ https://issues.apache.org/jira/browse/PHOENIX-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267925#comment-15267925 ] Julian Hyde commented on PHOENIX-2845: -- Sounds reasonable. > Timestamp ignores nanos in literal

[jira] [Commented] (PHOENIX-2845) Timestamp ignores nanos in literal expressions

[ https://issues.apache.org/jira/browse/PHOENIX-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267302#comment-15267302 ] Julian Hyde commented on PHOENIX-2845: -- The TIMESTAMP type has a scale. The default scale differs

[jira] [Commented] (PHOENIX-3054) Counting zero null rows returns an empty result set

[ https://issues.apache.org/jira/browse/PHOENIX-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455835#comment-15455835 ] Julian Hyde commented on PHOENIX-3054: -- Right. The behavior is as if there is one group that

[jira] [Commented] (PHOENIX-3046) `NOT LIKE '%'` unexpectedly returns results

[ https://issues.apache.org/jira/browse/PHOENIX-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15479742#comment-15479742 ] Julian Hyde commented on PHOENIX-3046: -- According to the standard, {{LIKE}} and {{NOT LIKE}} will

[jira] [Commented] (PHOENIX-3242) Support CREATE OR REPLACE FUNCTION in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486350#comment-15486350 ] Julian Hyde commented on PHOENIX-3242: -- [~jamestaylor], Do what Oracle does: never add a new verb,

[jira] [Commented] (PHOENIX-3264) Allow TRUE and FALSE to be used as literal constants

[ https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494919#comment-15494919 ] Julian Hyde commented on PHOENIX-3264: -- The "Impl" in the class name is a clue that it is

[jira] [Commented] (PHOENIX-3347) Change conformance or remove SELECT statements without FROM clauses

[ https://issues.apache.org/jira/browse/PHOENIX-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549323#comment-15549323 ] Julian Hyde commented on PHOENIX-3347: -- Up to you. Maybe a PHOENIX member in SqlConformance. Or

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549331#comment-15549331 ] Julian Hyde commented on PHOENIX-2679: -- Do these shadow tables exist in HBase? > Implement column

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1643#comment-1643 ] Julian Hyde commented on PHOENIX-2679: -- [~jamestaylor], I think [~maryannxue] has found a good

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1700#comment-1700 ] Julian Hyde commented on PHOENIX-2679: -- We're making sure that the hard stuff is in Calcite - in

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549550#comment-15549550 ] Julian Hyde commented on PHOENIX-2679: -- IIRC, and if it is useful, there is a way for a

[jira] [Commented] (PHOENIX-2679) Implement column family schema structure in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549468#comment-15549468 ] Julian Hyde commented on PHOENIX-2679: -- I believe that Schema is only used at validation time, not

[jira] [Commented] (PHOENIX-3265) Surround columns named date with double quotes

[ https://issues.apache.org/jira/browse/PHOENIX-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15547038#comment-15547038 ] Julian Hyde commented on PHOENIX-3265: -- CALCITE-1256 only applies if the name is ALSO a built-in

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497639#comment-15497639 ] Julian Hyde commented on PHOENIX-476: - I agree with [~kliew]. The result should be (1, NULL).

[jira] [Commented] (PHOENIX-3264) Allow TRUE and FALSE to be used as literal constants

[ https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504370#comment-15504370 ] Julian Hyde commented on PHOENIX-3264: -- Yeah, you need to be in a particular environment (i.e.

[jira] [Commented] (PHOENIX-3264) Allow TRUE and FALSE to be used as literal constants

[ https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513988#comment-15513988 ] Julian Hyde commented on PHOENIX-3264: -- Hopefully you can understand why I am pushing back and do

[jira] [Commented] (PHOENIX-3264) Allow TRUE and FALSE to be used as literal constants

[ https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513622#comment-15513622 ] Julian Hyde commented on PHOENIX-3264: -- Probably convertLiteral is intentionally private and there

[jira] [Comment Edited] (PHOENIX-3299) Janino could not work in shaded package

[ https://issues.apache.org/jira/browse/PHOENIX-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507187#comment-15507187 ] Julian Hyde edited comment on PHOENIX-3299 at 9/20/16 5:23 PM: --- If you

[jira] [Commented] (PHOENIX-3299) Janino could not work in shaded package

[ https://issues.apache.org/jira/browse/PHOENIX-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507187#comment-15507187 ] Julian Hyde commented on PHOENIX-3299: -- If you hard-code a package name or class name, shade can't

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507229#comment-15507229 ] Julian Hyde commented on PHOENIX-476: - I don't think you should allow {{CURRENT_DATE}} or similar.

[jira] [Commented] (PHOENIX-476) Support declaration of DEFAULT in CREATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504513#comment-15504513 ] Julian Hyde commented on PHOENIX-476: - [~jamestaylor], I'm skeptical. DEFAULT is clearly intended to

[jira] [Commented] (PHOENIX-3357) Issue with column re-ordering in column family support for Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563275#comment-15563275 ] Julian Hyde commented on PHOENIX-3357: -- I think the ordered list of columns should be a property of

[jira] [Commented] (PHOENIX-3267) Replace use of SELECT null with CAST(null AS )

[ https://issues.apache.org/jira/browse/PHOENIX-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15595841#comment-15595841 ] Julian Hyde commented on PHOENIX-3267: -- It would be possible to change Calcite to handle this, but

[jira] [Commented] (PHOENIX-3351) Implement TODOs in PhoenixTableModify#upsert to allow writes to tenant specific tables

[ https://issues.apache.org/jira/browse/PHOENIX-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689078#comment-15689078 ] Julian Hyde commented on PHOENIX-3351: -- If I recall correctly, TenantId and similar columns are not

[jira] [Commented] (PHOENIX-3471) Allow accessing full (legacy) Phoenix EXPLAIN information via Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687363#comment-15687363 ] Julian Hyde commented on PHOENIX-3471: -- I am torn on this proposal. I am a huge fan of matchers,

[jira] [Commented] (PHOENIX-3440) Calcite has specific requirements for date and datetime operations

[ https://issues.apache.org/jira/browse/PHOENIX-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671064#comment-15671064 ] Julian Hyde commented on PHOENIX-3440: -- We have CALCITE-304 logged, but not progress in a long

[jira] [Comment Edited] (PHOENIX-3440) Calcite has specific requirements for date and datetime operations

[ https://issues.apache.org/jira/browse/PHOENIX-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671064#comment-15671064 ] Julian Hyde edited comment on PHOENIX-3440 at 11/16/16 5:37 PM: We have

[jira] [Commented] (PHOENIX-3477) Support sequence arithmetic in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671106#comment-15671106 ] Julian Hyde commented on PHOENIX-3477: -- I don't think we need arithmetic "inside a sequence". In

[jira] [Commented] (PHOENIX-3299) Janino could not work in shaded package

[ https://issues.apache.org/jira/browse/PHOENIX-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726542#comment-15726542 ] Julian Hyde commented on PHOENIX-3299: -- Is this a duplicate of CALCITE-1461? > Janino could not

[jira] [Commented] (PHOENIX-3732) Support for dynamic columns in UPSERT in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930704#comment-15930704 ] Julian Hyde commented on PHOENIX-3732: -- Yes, as long as there's a conformance setting to disallow

[jira] [Commented] (PHOENIX-3712) Column alias can't be resolved in GROUP BY clause

[ https://issues.apache.org/jira/browse/PHOENIX-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895309#comment-15895309 ] Julian Hyde commented on PHOENIX-3712: -- FYI, the relevant Calcite issue is CALCITE-1306. > Column

[jira] [Commented] (PHOENIX-3712) Column alias can't be resolved in GROUP BY clause

[ https://issues.apache.org/jira/browse/PHOENIX-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895980#comment-15895980 ] Julian Hyde commented on PHOENIX-3712: -- And [~kliew], if you'd like to contribute CALCITE-1306 I'd

[jira] [Updated] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated PHOENIX-3809: - Summary: CURRENT_DATE() (with parentheses) is illegal in Calcite (was: CURRENT_DATE() (with

[jira] [Commented] (PHOENIX-418) Support approximate COUNT DISTINCT

[ https://issues.apache.org/jira/browse/PHOENIX-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107832#comment-16107832 ] Julian Hyde commented on PHOENIX-418: - In CALCITE-1588 [~gian] points out that Oracle, BigQuery and

[jira] [Commented] (PHOENIX-2048) change to_char() function to use HALF_UP rounding mode

[ https://issues.apache.org/jira/browse/PHOENIX-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090022#comment-16090022 ] Julian Hyde commented on PHOENIX-2048: -- I don't think you need it to be configurable. If you ask 10

[jira] [Commented] (PHOENIX-2048) change to_char() function to use HALF_UP rounding mode

[ https://issues.apache.org/jira/browse/PHOENIX-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090297#comment-16090297 ] Julian Hyde commented on PHOENIX-2048: -- By the way, if you don't have an Oracle instance, this is

[jira] [Commented] (PHOENIX-2370) ResultSetMetaData.getColumnDisplaySize() returns bad value for varchar and varbinary columns

[ https://issues.apache.org/jira/browse/PHOENIX-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087662#comment-16087662 ] Julian Hyde commented on PHOENIX-2370: -- So I think that 40 is a good pragmatic choice. I seem to

[jira] [Commented] (PHOENIX-2048) change to_char() function to use HALF_UP rounding mode

[ https://issues.apache.org/jira/browse/PHOENIX-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087667#comment-16087667 ] Julian Hyde commented on PHOENIX-2048: -- Make it behave the same as Oracle. > change to_char()

[jira] [Commented] (PHOENIX-4035) Consider tables and sequences under same namespace in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091133#comment-16091133 ] Julian Hyde commented on PHOENIX-4035: -- bq. And at the same time Calcite expects table names also

[jira] [Commented] (PHOENIX-3993) Make use of DATETIME_PLUS operator in calcite for arithmetics on DATE and TIME

[ https://issues.apache.org/jira/browse/PHOENIX-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075597#comment-16075597 ] Julian Hyde commented on PHOENIX-3993: -- There is an open case for this, CALCITE-304 which covers

  1   2   >