[jira] [Commented] (PHOENIX-922) Support SELECT without a from clause

[ https://issues.apache.org/jira/browse/PHOENIX-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613272#comment-14613272 ] Serhiy Bilousov commented on PHOENIX-922: - Is it expectation of this query to

[jira] [Commented] (PHOENIX-2002) [sqlline] allow disabling colors and starting w.o building autocompletion lists

[ https://issues.apache.org/jira/browse/PHOENIX-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14557124#comment-14557124 ] Serhiy Bilousov commented on PHOENIX-2002: -- I was thinking to file the same. We

[jira] [Created] (PHOENIX-1993) NPE on sqlline.py start.

Serhiy Bilousov created PHOENIX-1993: Summary: NPE on sqlline.py start. Key: PHOENIX-1993 URL: https://issues.apache.org/jira/browse/PHOENIX-1993 Project: Phoenix Issue Type: Bug

[jira] [Commented] (PHOENIX-1875) implement ARRAY_PREPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514108#comment-14514108 ] Serhiy Bilousov commented on PHOENIX-1875: -- I would add tests to cover date

[jira] [Commented] (PHOENIX-1897) Use physical table name as key in top level map for MutationState

[ https://issues.apache.org/jira/browse/PHOENIX-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505043#comment-14505043 ] Serhiy Bilousov commented on PHOENIX-1897: -- bq. for views, get the physical

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

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500203#comment-14500203 ] Serhiy Bilousov commented on PHOENIX-971: - Hi [~ndimiduk] I went thru the doc

[jira] [Commented] (PHOENIX-1759) PhoenixArray to have decent .toString() implementation.

[ https://issues.apache.org/jira/browse/PHOENIX-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500569#comment-14500569 ] Serhiy Bilousov commented on PHOENIX-1759: -- Does it still make any sense to

[jira] [Commented] (PHOENIX-1759) PhoenixArray to have decent .toString() implementation.

[ https://issues.apache.org/jira/browse/PHOENIX-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497685#comment-14497685 ] Serhiy Bilousov commented on PHOENIX-1759: -- I had little time to go over. Will

[jira] [Commented] (PHOENIX-1748) Applying TRUNC|ROUND|FLOOR|CEIL on TIMESTAMP should maintain return type of TIMESTAMP

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486249#comment-14486249 ] Serhiy Bilousov commented on PHOENIX-1748: -- what version are you running it on

[jira] [Comment Edited] (PHOENIX-1748) Applying TRUNC|ROUND|FLOOR|CEIL on TIMESTAMP should maintain return type of TIMESTAMP

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486249#comment-14486249 ] Serhiy Bilousov edited comment on PHOENIX-1748 at 4/8/15 10:46 PM:

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392700#comment-14392700 ] Serhiy Bilousov commented on PHOENIX-1748: -- Thank you [~dhacker1341] for not

[jira] [Commented] (PHOENIX-1748) Applying TRUNC|ROUND|FLOOR|CEIL on TIMESTAMP should maintain return type of TIMESTAMP

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14393107#comment-14393107 ] Serhiy Bilousov commented on PHOENIX-1748: -- I am definitely interested and

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389902#comment-14389902 ] Serhiy Bilousov commented on PHOENIX-1748: -- Thank you [~dhacker1341] for

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389914#comment-14389914 ] Serhiy Bilousov commented on PHOENIX-1748: -- Ok. Let me ask in different way.

[jira] [Comment Edited] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389914#comment-14389914 ] Serhiy Bilousov edited comment on PHOENIX-1748 at 4/1/15 2:59 AM:

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389909#comment-14389909 ] Serhiy Bilousov commented on PHOENIX-1748: -- Well, I tried with both client

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389922#comment-14389922 ] Serhiy Bilousov commented on PHOENIX-1748: -- Client operates on column metadata

[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=14384791#comment-14384791 ] Serhiy Bilousov commented on PHOENIX-1749: -- {quote} {noformat} SELECT a, b,

[jira] [Commented] (PHOENIX-1727) Pherf - Port shell scripts to python

[ https://issues.apache.org/jira/browse/PHOENIX-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378750#comment-14378750 ] Serhiy Bilousov commented on PHOENIX-1727: -- Just want to ping this one

[jira] [Commented] (PHOENIX-1750) Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail

[ https://issues.apache.org/jira/browse/PHOENIX-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377331#comment-14377331 ] Serhiy Bilousov commented on PHOENIX-1750: -- Well, from SQL point of view it

[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=14377339#comment-14377339 ] Serhiy Bilousov commented on PHOENIX-1768: -- Does in mean there will be no

[jira] [Commented] (PHOENIX-1750) Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail

[ https://issues.apache.org/jira/browse/PHOENIX-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377333#comment-14377333 ] Serhiy Bilousov commented on PHOENIX-1750: -- That is interesting. I will give it

[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=14376984#comment-14376984 ] Serhiy Bilousov commented on PHOENIX-1768: -- That was easy one :)

[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=14377013#comment-14377013 ] Serhiy Bilousov commented on PHOENIX-1768: -- I am not big in standards (very

[jira] [Commented] (PHOENIX-1750) Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail

[ https://issues.apache.org/jira/browse/PHOENIX-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377241#comment-14377241 ] Serhiy Bilousov commented on PHOENIX-1750: -- sorry but - why? this one works as

[jira] [Commented] (PHOENIX-1750) Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail

[ https://issues.apache.org/jira/browse/PHOENIX-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377219#comment-14377219 ] Serhiy Bilousov commented on PHOENIX-1750: -- no - why? Some build-in

[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=14375319#comment-14375319 ] Serhiy Bilousov commented on PHOENIX-1768: -- [~jamestaylor] I think it would be

[jira] [Commented] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

[ https://issues.apache.org/jira/browse/PHOENIX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368573#comment-14368573 ] Serhiy Bilousov commented on PHOENIX-1744: -- Both epoch values is valid epoch

[jira] [Commented] (PHOENIX-1756) Add Month() and Second() buildin functions

[ https://issues.apache.org/jira/browse/PHOENIX-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370331#comment-14370331 ] Serhiy Bilousov commented on PHOENIX-1756: -- IMHO. You can do a lot by math but

[jira] [Commented] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

[ https://issues.apache.org/jira/browse/PHOENIX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370258#comment-14370258 ] Serhiy Bilousov commented on PHOENIX-1744: -- done -

[jira] [Created] (PHOENIX-1759) PhoenixArray to have decent .toString() implementation.

Serhiy Bilousov created PHOENIX-1759: Summary: PhoenixArray to have decent .toString() implementation. Key: PHOENIX-1759 URL: https://issues.apache.org/jira/browse/PHOENIX-1759 Project: Phoenix

[jira] [Created] (PHOENIX-1760) CAST epoch (in seconds) AS TIME/DATE/TIMESTAMP fails.

Serhiy Bilousov created PHOENIX-1760: Summary: CAST epoch (in seconds) AS TIME/DATE/TIMESTAMP fails. Key: PHOENIX-1760 URL: https://issues.apache.org/jira/browse/PHOENIX-1760 Project: Phoenix

[jira] [Commented] (PHOENIX-1756) Add Month() and Second() buildin functions

[ https://issues.apache.org/jira/browse/PHOENIX-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370216#comment-14370216 ] Serhiy Bilousov commented on PHOENIX-1756: -- so Year(), Month(), Second() but

[jira] [Comment Edited] (PHOENIX-1287) Use the joni byte[] regex engine in place of j.u.regex

[ https://issues.apache.org/jira/browse/PHOENIX-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14367604#comment-14367604 ] Serhiy Bilousov edited comment on PHOENIX-1287 at 3/20/15 4:53 AM:

[jira] [Commented] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

[ https://issues.apache.org/jira/browse/PHOENIX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369546#comment-14369546 ] Serhiy Bilousov commented on PHOENIX-1744: -- q. [~jamestaylor] Phoenix only

[jira] [Created] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

Serhiy Bilousov created PHOENIX-1744: Summary: CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported. Key: PHOENIX-1744 URL: https://issues.apache.org/jira/browse/PHOENIX-1744 Project:

[jira] [Commented] (PHOENIX-1287) Use the joni byte[] regex engine in place of j.u.regex

[ https://issues.apache.org/jira/browse/PHOENIX-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14367604#comment-14367604 ] Serhiy Bilousov commented on PHOENIX-1287: -- Recently I had an issue with

[jira] [Created] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to to the DATE only.

Serhiy Bilousov created PHOENIX-1748: Summary: Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to to the DATE only. Key: PHOENIX-1748 URL:

[jira] [Updated] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1748: - Summary: Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on

[jira] [Updated] (PHOENIX-1749) ORDER BY and GROUP 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:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1749: - Description: In postgreSQL (and many others DBs) you can specify not only column name

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

Serhiy Bilousov created PHOENIX-1749: Summary: ORDER BY and GROUP BY should support column position as well as column alias Key: PHOENIX-1749 URL: https://issues.apache.org/jira/browse/PHOENIX-1749

[jira] [Commented] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

[ https://issues.apache.org/jira/browse/PHOENIX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368376#comment-14368376 ] Serhiy Bilousov commented on PHOENIX-1744: -- But how to deal with epoch time

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368203#comment-14368203 ] Serhiy Bilousov commented on PHOENIX-1748: -- Thank you [~jamestaylor] for prompt

[jira] [Created] (PHOENIX-1750) Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail

Serhiy Bilousov created PHOENIX-1750: Summary: Some build-in functions used in expression surface internal implementation as column alias what cause GROUP BY to fail Key: PHOENIX-1750 URL:

[jira] [Commented] (PHOENIX-1744) CAST from UNSIGNED_LONG (_INT) to * TIMESTAMP is not supported.

[ https://issues.apache.org/jira/browse/PHOENIX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368515#comment-14368515 ] Serhiy Bilousov commented on PHOENIX-1744: -- Well, actually we did define column

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366545#comment-14366545 ] Serhiy Bilousov commented on PHOENIX-1704: -- I have a question (mostly for my

[jira] [Commented] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14364291#comment-14364291 ] Serhiy Bilousov commented on PHOENIX-1580: -- Would this kind of optimisation be

[jira] [Commented] (PHOENIX-1705) implement ARRAY_APPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14364601#comment-14364601 ] Serhiy Bilousov commented on PHOENIX-1705: -- I am not sure if that is a given or

[jira] [Commented] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363763#comment-14363763 ] Serhiy Bilousov commented on PHOENIX-1580: -- I am waiting with inpatients to try

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361559#comment-14361559 ] Serhiy Bilousov commented on PHOENIX-1704: -- Nice work! I still could not run

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359913#comment-14359913 ] Serhiy Bilousov commented on PHOENIX-1704: -- [~jamestaylor], should this have

[jira] [Comment Edited] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303540#comment-14303540 ] Serhiy Bilousov edited comment on PHOENIX-1311 at 3/12/15 11:43 PM:

[jira] [Updated] (PHOENIX-1719) CREATE VIEW ... AS SELECT DDL should allow aliases for the column(s) definition.

[ https://issues.apache.org/jira/browse/PHOENIX-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1719: - Summary: CREATE VIEW ... AS SELECT DDL should allow aliases for the column(s)

[jira] [Created] (PHOENIX-1721) Add DUAL table or alike functionality

Serhiy Bilousov created PHOENIX-1721: Summary: Add DUAL table or alike functionality Key: PHOENIX-1721 URL: https://issues.apache.org/jira/browse/PHOENIX-1721 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-1721) Add DUAL table or alike functionality

[ https://issues.apache.org/jira/browse/PHOENIX-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1721: - Description: The DUAL table is a special one-row, one-column table present by default

[jira] [Created] (PHOENIX-1719) CREATE VIEW ... AS SELECT DDL should allow to specify aliases for the columns.

Serhiy Bilousov created PHOENIX-1719: Summary: CREATE VIEW ... AS SELECT DDL should allow to specify aliases for the columns. Key: PHOENIX-1719 URL: https://issues.apache.org/jira/browse/PHOENIX-1719

[jira] [Created] (PHOENIX-1720) Add 'OR REPLACE to the CREATE ... DDL statement.

Serhiy Bilousov created PHOENIX-1720: Summary: Add 'OR REPLACE to the CREATE ... DDL statement. Key: PHOENIX-1720 URL: https://issues.apache.org/jira/browse/PHOENIX-1720 Project: Phoenix

[jira] [Comment Edited] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351983#comment-14351983 ] Serhiy Bilousov edited comment on PHOENIX-1704 at 3/8/15 9:29 AM:

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351983#comment-14351983 ] Serhiy Bilousov commented on PHOENIX-1704: -- I am kind lost here. I feel like I

[jira] [Updated] (PHOENIX-1714) WHERE part for CREATE VIEW ... AS SELECT ... does not work for the quoted CF

[ https://issues.apache.org/jira/browse/PHOENIX-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1714: - Description: I was trying to build some views on top of HBase table but have very

[jira] [Created] (PHOENIX-1714) WHERE part for CREATE VIEW ... AS SELECT ... does not work for quoted CF

Serhiy Bilousov created PHOENIX-1714: Summary: WHERE part for CREATE VIEW ... AS SELECT ... does not work for quoted CF Key: PHOENIX-1714 URL: https://issues.apache.org/jira/browse/PHOENIX-1714

[jira] [Updated] (PHOENIX-1714) WHERE part for CREATE VIEW ... AS SELECT ... does not work for the quoted CF

[ https://issues.apache.org/jira/browse/PHOENIX-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serhiy Bilousov updated PHOENIX-1714: - Summary: WHERE part for CREATE VIEW ... AS SELECT ... does not work for the quoted CF

[jira] [Commented] (PHOENIX-1705) implement ARRAY_APPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14352120#comment-14352120 ] Serhiy Bilousov commented on PHOENIX-1705: -- [~jamestaylor], Was expectations

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351855#comment-14351855 ] Serhiy Bilousov commented on PHOENIX-1704: -- That what my thinking was to

[jira] [Comment Edited] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351681#comment-14351681 ] Serhiy Bilousov edited comment on PHOENIX-1704 at 3/8/15 1:44 AM:

[jira] [Commented] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351291#comment-14351291 ] Serhiy Bilousov commented on PHOENIX-1704: -- If I say something silly please

[jira] [Comment Edited] (PHOENIX-1704) Add year() built-in function

[ https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351291#comment-14351291 ] Serhiy Bilousov edited comment on PHOENIX-1704 at 3/7/15 1:37 AM:

[jira] [Commented] (PHOENIX-1665) Implement missing ARRAY built-in functions

[ https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349968#comment-14349968 ] Serhiy Bilousov commented on PHOENIX-1665: -- I thought unnest is postgresql's

[jira] [Comment Edited] (PHOENIX-1665) Implement missing ARRAY built-in functions

[ https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347350#comment-14347350 ] Serhiy Bilousov edited comment on PHOENIX-1665 at 3/4/15 6:45 PM:

[jira] [Commented] (PHOENIX-1665) Implement missing ARRAY built-in functions

[ https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347350#comment-14347350 ] Serhiy Bilousov commented on PHOENIX-1665: -- can we mark this

[jira] [Commented] (PHOENIX-1609) MR job to populate index tables

[ https://issues.apache.org/jira/browse/PHOENIX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323633#comment-14323633 ] Serhiy Bilousov commented on PHOENIX-1609: -- I do understand why using MR job be

[jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303540#comment-14303540 ] Serhiy Bilousov commented on PHOENIX-1311: -- I have to admit that it was my

[jira] [Commented] (PHOENIX-1233) Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError

[ https://issues.apache.org/jira/browse/PHOENIX-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265125#comment-14265125 ] Serhiy Bilousov commented on PHOENIX-1233: -- Thank you guys. Do you have a

[jira] [Commented] (PHOENIX-1233) Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError

[ https://issues.apache.org/jira/browse/PHOENIX-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250651#comment-14250651 ] Serhiy Bilousov commented on PHOENIX-1233: -- We have what looks the same issue:

[jira] [Created] (PHOENIX-1473) Connecting with Phoenix client when Phoenix is not deployed on region server(s) takes down region server(s).

SERHIY BILOUSOV created PHOENIX-1473: Summary: Connecting with Phoenix client when Phoenix is not deployed on region server(s) takes down region server(s). Key: PHOENIX-1473 URL:

[jira] [Commented] (PHOENIX-1473) Connecting with Phoenix client when Phoenix is not deployed on region server(s) takes down region server(s).

[ https://issues.apache.org/jira/browse/PHOENIX-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14219731#comment-14219731 ] SERHIY BILOUSOV commented on PHOENIX-1473: -- My understanding is that region