[jira] [Created] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

Samarth Jain created PHOENIX-3487: - Summary: IndexIT#testTableDescriptorPriority fails Key: PHOENIX-3487 URL: https://issues.apache.org/jira/browse/PHOENIX-3487 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because of HBASE-17108

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671370#comment-15671370 ] Hudson commented on PHOENIX-3485: - FAILURE: Integrated in Jenkins build Phoenix-master #1490 (See

[jira] [Created] (PHOENIX-3488) Support COUNT(DISTINCT x) in Phoenix-Calcite Integration

Eric Lomore created PHOENIX-3488: Summary: Support COUNT(DISTINCT x) in Phoenix-Calcite Integration Key: PHOENIX-3488 URL: https://issues.apache.org/jira/browse/PHOENIX-3488 Project: Phoenix

[jira] [Updated] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3487: -- Attachment: PHOENIX-3487_v2.patch Thanks for the review, [~jamestaylor]. Attached is the

[jira] [Commented] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671635#comment-15671635 ] James Taylor commented on PHOENIX-3487: --- Rather than assuming that every HBase table is a Phoenix

[jira] [Commented] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671545#comment-15671545 ] Samarth Jain commented on PHOENIX-3487: --- [~jamestaylor], please review. Another alternative to

[jira] [Updated] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3487: -- Attachment: PHOENIX-3487.patch > IndexIT#testTableDescriptorPriority fails >

[jira] [Resolved] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-3487. --- Resolution: Fixed Fix Version/s: 4.8.2 4.9.0 >

[jira] [Commented] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671863#comment-15671863 ] James Taylor commented on PHOENIX-3487: --- +1 > IndexIT#testTableDescriptorPriority fails >

[jira] [Commented] (PHOENIX-3488) Support COUNT(DISTINCT x) in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672054#comment-15672054 ] Eric Lomore commented on PHOENIX-3488: -- [~maryannxue], I believe I have a working patch for this.

[jira] [Updated] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3482: -- Attachment: (was: PHOENIX-3482.patch) > Provide a work around for HBASE-17096 >

[jira] [Updated] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3482: -- Attachment: PHOENIX-3482.patch > Provide a work around for HBASE-17096 >

Phoenix upgrade from 4.6.1 to 4.8.1

Hi, We are upgrading Phoenix from 4.6.1 to 4.8.1. Do we need to Alter SYSTEM.CATALOG to add the below columns manually or these will be added while antialiasing the connection. IS_NAMESPACE_MAPPED AUTO_PARTITION_SEQ APPEND_ONLY_SCHEMA UPDATE_CACHE_FREQUENCY TRANSACTIONAL Thanks Venkat

[jira] [Created] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

Sergey Soldatov created PHOENIX-3490: Summary: PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env Key: PHOENIX-3490 URL:

[jira] [Updated] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

[ https://issues.apache.org/jira/browse/PHOENIX-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-3490: - Labels: hive (was: ) > PhoenixStorageHandler doesn't handler hbase configuration

[jira] [Updated] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

[ https://issues.apache.org/jira/browse/PHOENIX-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-3490: - Labels: HivePhoenix (was: hive) > PhoenixStorageHandler doesn't handler hbase

[jira] [Commented] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672300#comment-15672300 ] James Taylor commented on PHOENIX-3482: --- How about just doing a Put with the unlock value when we

[jira] [Commented] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672337#comment-15672337 ] James Taylor commented on PHOENIX-3482: --- +1 > Provide a work around for HBASE-17096 >

[jira] [Updated] (PHOENIX-3451) Incorrect determination of preservation of order for an aggregate query leads to incorrect query results

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3451: -- Fix Version/s: 4.8.2 4.9.0 > Incorrect determination of preservation of

Re: Phoenix upgrade from 4.6.1 to 4.8.1

Hi Venkat, These columns will automatically get added during the upgrade. The upgrade will occur when the first 4.8.1 client connects to the 4.8.1 cluster. FYI, we're voting on a 4.8.2 release which has some important bug fixes. Should be ready soon, so you may want to wait until then to do the

[jira] [Updated] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3482: -- Attachment: PHOENIX-3482.patch [~jamestaylor], please review. I am not sure if having

[jira] [Commented] (PHOENIX-3487) IndexIT#testTableDescriptorPriority fails

[ https://issues.apache.org/jira/browse/PHOENIX-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672147#comment-15672147 ] Hudson commented on PHOENIX-3487: - SUCCESS: Integrated in Jenkins build Phoenix-master #1491 (See

[jira] [Updated] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

[ https://issues.apache.org/jira/browse/PHOENIX-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-3490: - Attachment: PHOENIX-3490-1.patch Added HBase configuration as well as token generation

[jira] [Commented] (PHOENIX-3451) Incorrect determination of preservation of order for an aggregate query leads to incorrect query results

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672111#comment-15672111 ] Samarth Jain commented on PHOENIX-3451: --- +1, looks good. > Incorrect determination of

[jira] [Created] (PHOENIX-3489) Compile out expressions formed by only columns with WHERE clause equality constraints in GROUP BY and ORDER BY

James Taylor created PHOENIX-3489: - Summary: Compile out expressions formed by only columns with WHERE clause equality constraints in GROUP BY and ORDER BY Key: PHOENIX-3489 URL:

[jira] [Assigned] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-3482: - Assignee: Samarth Jain > Provide a work around for HBASE-17096 >

[jira] [Updated] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3482: -- Attachment: PHOENIX-3482_v2.patch Good idea, [~jamestaylor]. That makes the patch simpler and

[jira] [Created] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not OrderPreserving but OrderBy is reverse

chenglei created PHOENIX-3491: - Summary: OrderBy should be compiled out when GroupBy is not OrderPreserving but OrderBy is reverse Key: PHOENIX-3491 URL: https://issues.apache.org/jira/browse/PHOENIX-3491

[jira] [Updated] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[ https://issues.apache.org/jira/browse/PHOENIX-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3491: -- Description: for the following table: {code:borderStyle=solid} CREATE TABLE ORDERBY_TEST

[jira] [Updated] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[ https://issues.apache.org/jira/browse/PHOENIX-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3491: -- Summary: OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[jira] [Comment Edited] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[ https://issues.apache.org/jira/browse/PHOENIX-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672486#comment-15672486 ] chenglei edited comment on PHOENIX-3491 at 11/17/16 2:51 AM: - Just from

[jira] [Updated] (PHOENIX-3489) Compile out expressions formed by only columns with WHERE clause equality constraints in GROUP BY and ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3489: -- Fix Version/s: 4.10.0 > Compile out expressions formed by only columns with WHERE clause

[jira] [Commented] (PHOENIX-3469) Incorrect sort order for DESC primary key for NULLS LAST/NULLS FIRST

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15673014#comment-15673014 ] Hudson commented on PHOENIX-3469: - FAILURE: Integrated in Jenkins build Phoenix-master #1494 (See

[jira] [Commented] (PHOENIX-3452) NULLS FIRST/NULL LAST should not impact whether GROUP BY is order preserving

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15673015#comment-15673015 ] Hudson commented on PHOENIX-3452: - FAILURE: Integrated in Jenkins build Phoenix-master #1494 (See

[jira] [Created] (PHOENIX-3492) Add PageFilter with DistinctPrefixFilter when LIMIT clause is present

James Taylor created PHOENIX-3492: - Summary: Add PageFilter with DistinctPrefixFilter when LIMIT clause is present Key: PHOENIX-3492 URL: https://issues.apache.org/jira/browse/PHOENIX-3492 Project:

Re: [CANCEL][VOTE] Release of Apache Phoenix 4.8.2 RC1

The fix for PHOENIX-3452 has been checked in so I believe we're ready to proceed with the next RC. On Fri, Nov 11, 2016 at 9:42 AM, wrote: > > > From: "la...@apache.org" > To: Dev > Sent: Monday, November 7, 2016 1:31 PM >

[jira] [Commented] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

[ https://issues.apache.org/jira/browse/PHOENIX-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672974#comment-15672974 ] James Taylor commented on PHOENIX-3490: --- We're getting ready to cut an RC for 4.9.0. Would you

[jira] [Commented] (PHOENIX-3490) PhoenixStorageHandler doesn't handler hbase configuration properly and don't work in secured env

[ https://issues.apache.org/jira/browse/PHOENIX-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15673076#comment-15673076 ] Sergey Soldatov commented on PHOENIX-3490: -- [~jamestaylor] It would be nice to have (any

[jira] [Commented] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[ https://issues.apache.org/jira/browse/PHOENIX-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672486#comment-15672486 ] chenglei commented on PHOENIX-3491: --- Just from PHOENIX-3451,but is irrelevant to PHOENIX-3451,so open

[jira] [Resolved] (PHOENIX-3451) Incorrect determination of preservation of order for an aggregate query leads to incorrect query results

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3451. --- Resolution: Fixed > Incorrect determination of preservation of order for an aggregate query

[jira] [Updated] (PHOENIX-3491) OrderBy should be compiled out when GroupBy is not orderPreserving but OrderBy is reverse

[ https://issues.apache.org/jira/browse/PHOENIX-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3491: -- Description: for the following table: {code:borderStyle=solid} CREATE TABLE ORDERBY_TEST

[jira] [Commented] (PHOENIX-3482) Provide a work around for HBASE-17096

[ https://issues.apache.org/jira/browse/PHOENIX-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672637#comment-15672637 ] Hudson commented on PHOENIX-3482: - FAILURE: Integrated in Jenkins build Phoenix-master #1493 (See

[jira] [Updated] (PHOENIX-3452) NULLS FIRST/NULL LAST should not impact whether GROUP BY is order preserving

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3452: -- Fix Version/s: 4.8.2 4.9.0 > NULLS FIRST/NULL LAST should not impact

[jira] [Resolved] (PHOENIX-3452) NULLS FIRST/NULL LAST should not impact whether GROUP BY is order preserving

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3452. --- Resolution: Fixed > NULLS FIRST/NULL LAST should not impact whether GROUP BY is order

[jira] [Updated] (PHOENIX-3469) Incorrect sort order for DESC primary key for NULLS LAST/NULLS FIRST

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3469: -- Fix Version/s: 4.8.2 4.9.0 > Incorrect sort order for DESC primary key for

Query with index failed when data table's PK column is in DESC order

Hi all This is a very simple case, easy to repro, see the following SQLs: create table tt (pk integer primary key, a integer, b integer); create index tti on tt (a); upsert into tt values (1, 2, 3); select /*+index(tt tti)*/ b from tt where a = 2; // will query back to

Re: Query with index failed when data table's PK column is in DESC order

Good catch William, Please raise JIRA and upload patch there. http://issues.apache.org/jira/browse/PHOENIX Thanks, Rajeshbabu. On Wed, Nov 16, 2016 at 1:59 PM, William wrote: > Hi all >This is a very simple case, easy to repro, see the following SQLs: > > >create

[jira] [Commented] (PHOENIX-2890) Extend IndexTool to allow incremental index rebuilds

[ https://issues.apache.org/jira/browse/PHOENIX-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670099#comment-15670099 ] ASF GitHub Bot commented on PHOENIX-2890: - Github user ankitsinghal commented on a diff in the

[GitHub] phoenix pull request #210: PHOENIX-2890 Extend IndexTool to allow incrementa...

Github user ankitsinghal commented on a diff in the pull request: https://github.com/apache/phoenix/pull/210#discussion_r88209639 --- Diff: phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolForPartialBuildWithNamespaceEnabled.java --- @@ -0,0 +1,71 @@ +/* + *

[jira] [Commented] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei commented on PHOENIX-3451: --- [~jamestaylor]，I have a problem with your patch: why did you

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 11:41 AM: --

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 11:44 AM: --

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 2:46 PM: -

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 2:48 PM: -

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 2:49 PM: -

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 2:49 PM: -

[jira] [Comment Edited] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670234#comment-15670234 ] chenglei edited comment on PHOENIX-3451 at 11/16/16 2:38 PM: -

[jira] [Commented] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670786#comment-15670786 ] Samarth Jain commented on PHOENIX-3485: --- Good point, [~rajeshbabu]. I followed what is being done

[jira] [Commented] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670791#comment-15670791 ] Samarth Jain commented on PHOENIX-3485: --- Actually it turns out there is no getString() method so I

[jira] [Resolved] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-3485. --- Resolution: Fixed Fix Version/s: 4.8.2 4.9.0 > CSVBulkLoadToolIT

[jira] [Commented] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670686#comment-15670686 ] James Taylor commented on PHOENIX-3451: --- I removed those lines hoping it would just work :-). I'll

[jira] [Commented] (PHOENIX-3451) Secondary index and query using distinct: LIMIT doesn't return the first rows

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670770#comment-15670770 ] chenglei commented on PHOENIX-3451: --- Thank you for feedback ,[~jamestaylor], yes, if those lines are

[jira] [Commented] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670904#comment-15670904 ] Rajeshbabu Chintaguntla commented on PHOENIX-3485: -- [~samarthjain] You can use get()

[jira] [Updated] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3485: -- Attachment: PHOENIX-3485_addendum.patch > CSVBulkLoadToolIT failing consistently because

[jira] [Updated] (PHOENIX-3485) CSVBulkLoadToolIT failing consistently because of HBASE-17108

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3485: -- Summary: CSVBulkLoadToolIT failing consistently because of HBASE-17108 (was:

[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-3485) CSVBulkLoadToolIT failing consistently because transaction service client init fails

[ https://issues.apache.org/jira/browse/PHOENIX-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671112#comment-15671112 ] Samarth Jain commented on PHOENIX-3485: --- Thanks, [~rajeshbabu]. I have committed an addendum. >

[jira] [Resolved] (PHOENIX-3448) Possible deadlock because transaction service client is stuck

[ https://issues.apache.org/jira/browse/PHOENIX-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-3448. --- Resolution: Fixed > Possible deadlock because transaction service client is stuck >

[jira] [Updated] (PHOENIX-3451) Incorrect determination of preservation of order for an aggregate query leads to incorrect query results

[ https://issues.apache.org/jira/browse/PHOENIX-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3451: -- Summary: Incorrect determination of preservation of order for an aggregate query leads to