[jira] [Updated] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi updated PHOENIX-3336: - Attachment: (was: wrong-index.png) > get the wrong results when using the local secondary

[jira] [Commented] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531626#comment-15531626 ] Houliang Qi commented on PHOENIX-3336: -- I have added the ddl statements and the test case in the

[jira] [Updated] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi updated PHOENIX-3336: - Attachment: sample_2.csv sample_1.csv readme.txt

[jira] [Commented] (PHOENIX-3159) CachingHTableFactory may close HTable during eviction even if it is getting used for writing by another thread.

[ https://issues.apache.org/jira/browse/PHOENIX-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531520#comment-15531520 ] Devaraj Das commented on PHOENIX-3159: -- +1 > CachingHTableFactory may close HTable during

[jira] [Resolved] (PHOENIX-3235) Tephra errors when trying to create a transactional table in Phoenix 4.8.0

[ https://issues.apache.org/jira/browse/PHOENIX-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Chuang resolved PHOENIX-3235. - Resolution: Fixed Fix Version/s: 4.8.1 Tested and confirmed to be fixed in

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

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

[jira] [Commented] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531383#comment-15531383 ] James Taylor commented on PHOENIX-6: bq. but incrementing a numeric column can use the optimized path,

[jira] [Commented] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531316#comment-15531316 ] Gary Horen commented on PHOENIX-6: -- [~giacomotaylor]: >>would thus require a read before write For a

[jira] [Commented] (PHOENIX-3259) Create fat jar for transaction manager

[ https://issues.apache.org/jira/browse/PHOENIX-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531229#comment-15531229 ] Francis Chuang commented on PHOENIX-3259: - [~jamestaylor], replacing guava 12 with guava 13

[jira] [Commented] (PHOENIX-3201) Implement DAYOFWEEK and DAYOFYEAR built-in functions

[ https://issues.apache.org/jira/browse/PHOENIX-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531179#comment-15531179 ] James Taylor commented on PHOENIX-3201: --- [~an...@apache.org] - there's a bunch of scalar date

[jira] [Updated] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-6: --- Description: To support inserting a new row only if it doesn't already exist, we should support the

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531099#comment-15531099 ] James Taylor commented on PHOENIX-3181: --- Checked into master only for now. Will monitor how the

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531078#comment-15531078 ] Hadoop QA commented on PHOENIX-3181: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530934#comment-15530934 ] James Taylor commented on PHOENIX-2909: --- This solution isn't complete because it doesn't handle

[jira] [Updated] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2909: -- Assignee: (was: James Taylor) > Surface checkAndPut through UPDATE statement >

[jira] [Assigned] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-6: -- Assignee: James Taylor > Support ON DUPLICATE KEY construct >

[jira] [Updated] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-6: --- Description: To support inserting a new row only if it doesn't already exist, we should support the

[jira] [Updated] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2909: -- Fix Version/s: (was: 4.9.0) > Surface checkAndPut through UPDATE statement >

[jira] [Commented] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530929#comment-15530929 ] James Taylor commented on PHOENIX-6: FYI, [~gho...@salesforce.com] > Support ON DUPLICATE KEY

[jira] [Updated] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-6: --- Description: To support inserting a new row only if it doesn't already exist, we should support the

[jira] [Updated] (PHOENIX-6) Support ON DUPLICATE KEY construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-6: --- Summary: Support ON DUPLICATE KEY construct (was: Support on duplicate key ignore construct) >

[jira] [Updated] (PHOENIX-6) Support on duplicate key ignore construct

[ https://issues.apache.org/jira/browse/PHOENIX-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-6: --- Fix Version/s: 4.9.0 > Support on duplicate key ignore construct >

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: PHOENIX-3181_v9.patch Two passed test runs in a row. Let's try one more time. >

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: (was: PHOENIX-3181_v9.patch) > Run test methods in parallel to reduce test

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530830#comment-15530830 ] Hadoop QA commented on PHOENIX-3181: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: (was: PHOENIX-3181_v9.patch) > Run test methods in parallel to reduce test

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: PHOENIX-3181_v9.patch > Run test methods in parallel to reduce test suite run

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530676#comment-15530676 ] Hadoop QA commented on PHOENIX-3181: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: PHOENIX-3181_v9.patch > Run test methods in parallel to reduce test suite run

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: (was: PHOENIX-3181_v9.patch) > Run test methods in parallel to reduce test

[jira] [Resolved] (PHOENIX-3281) Workaround surefire error of there was a timeout or other error in the fork

[ https://issues.apache.org/jira/browse/PHOENIX-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3281. --- Resolution: Fixed Fix Version/s: 4.9.0 Most of the issues seem to be related to

[jira] [Assigned] (PHOENIX-3281) Workaround surefire error of there was a timeout or other error in the fork

[ https://issues.apache.org/jira/browse/PHOENIX-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3281: - Assignee: James Taylor > Workaround surefire error of there was a timeout or other

[jira] [Commented] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530480#comment-15530480 ] Hadoop QA commented on PHOENIX-3181: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Assigned] (PHOENIX-3140) Convert UpgradeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3140: - Assignee: James Taylor (was: prakul agarwal) > Convert UpgradeIT to be derived from

[jira] [Resolved] (PHOENIX-3153) Convert join-related IT tests to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3153. --- Resolution: Fixed Fix Version/s: 4.9.0 > Convert join-related IT tests to be derived

[jira] [Resolved] (PHOENIX-3140) Convert UpgradeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3140. --- Resolution: Fixed > Convert UpgradeIT to be derived from BaseHBaseManagedTimeTableReuseIT >

[jira] [Updated] (PHOENIX-3140) Convert UpgradeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3140: -- Fix Version/s: 4.9.0 > Convert UpgradeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[jira] [Updated] (PHOENIX-3181) Run test methods in parallel to reduce test suite run time

[ https://issues.apache.org/jira/browse/PHOENIX-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3181: -- Attachment: PHOENIX-3181_v9.patch > Run test methods in parallel to reduce test suite run

[DISCUSS] Making upgrade to a new minor release a manual step

(Resending email with a proper subject) Hello Phoenix folks, The purpose of this email is two fold: 1) to introduce folks about the new optional upgrade process and, 2) to get a consensus on what should the default behavior of the process be. As you may already know, when a new minor release is

[jira] [Commented] (PHOENIX-3282) Convert BaseClientManagedTimeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530141#comment-15530141 ] James Taylor commented on PHOENIX-3282: --- [~prakul] - are you available to help with this? Please

[jira] [Updated] (PHOENIX-3282) Convert BaseClientManagedTimeIT to be derived from BaseHBaseManagedTimeTableReuseIT

[ https://issues.apache.org/jira/browse/PHOENIX-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3282: -- Description: Convert BaseClientManagedTimeIT to be derived from

[jira] [Resolved] (PHOENIX-3290) Move and/or combine as many NeedsOwnCluster tests to bring down test run time

[ https://issues.apache.org/jira/browse/PHOENIX-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3290. --- Resolution: Fixed > Move and/or combine as many NeedsOwnCluster tests to bring down test

[jira] [Resolved] (PHOENIX-3293) Create separate test categories for stats enabled and disabled

[ https://issues.apache.org/jira/browse/PHOENIX-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3293. --- Resolution: Fixed Fix Version/s: 4.9.0 > Create separate test categories for stats

[jira] [Updated] (PHOENIX-3290) Move and/or combine as many NeedsOwnCluster tests to bring down test run time

[ https://issues.apache.org/jira/browse/PHOENIX-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3290: -- Fix Version/s: 4.9.0 > Move and/or combine as many NeedsOwnCluster tests to bring down test

[jira] [Assigned] (PHOENIX-3290) Move and/or combine as many NeedsOwnCluster tests to bring down test run time

[ https://issues.apache.org/jira/browse/PHOENIX-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3290: - Assignee: James Taylor > Move and/or combine as many NeedsOwnCluster tests to bring

[jira] [Assigned] (PHOENIX-3293) Create separate test categories for stats enabled and disabled

[ https://issues.apache.org/jira/browse/PHOENIX-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3293: - Assignee: James Taylor > Create separate test categories for stats enabled and

[jira] [Resolved] (PHOENIX-3286) Use regular queue depth instead of overriding it to zero for tests

[ https://issues.apache.org/jira/browse/PHOENIX-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3286. --- Resolution: Fixed > Use regular queue depth instead of overriding it to zero for tests >

[jira] [Assigned] (PHOENIX-3286) Use regular queue depth instead of overriding it to zero for tests

[ https://issues.apache.org/jira/browse/PHOENIX-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3286: - Assignee: James Taylor > Use regular queue depth instead of overriding it to zero for

[jira] [Updated] (PHOENIX-3286) Use regular queue depth instead of overriding it to zero for tests

[ https://issues.apache.org/jira/browse/PHOENIX-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3286: -- Fix Version/s: 4.9.0 > Use regular queue depth instead of overriding it to zero for tests >

[jira] [Resolved] (PHOENIX-3335) Improve documention of unsigned_long type mapping

[ https://issues.apache.org/jira/browse/PHOENIX-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3335. --- Resolution: Fixed Thanks for the patch, [~yhxx511]. I've aded you as a Phoenix contributor,

[jira] [Commented] (PHOENIX-3331) Bug in calculating minDisabledTimestamp for a batch

[ https://issues.apache.org/jira/browse/PHOENIX-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530062#comment-15530062 ] James Taylor commented on PHOENIX-3331: --- Please commit ASAP, [~an...@apache.org] to both 4.8, 4.x,

[jira] [Updated] (PHOENIX-3335) Improve documention of unsigned_long type mapping

[ https://issues.apache.org/jira/browse/PHOENIX-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3335: -- Assignee: William Yang > Improve documention of unsigned_long type mapping >

[jira] [Commented] (PHOENIX-3254) IndexId Sequence is incremented even if index exists already.

[ https://issues.apache.org/jira/browse/PHOENIX-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530037#comment-15530037 ] ASF GitHub Bot commented on PHOENIX-3254: - Github user JamesRTaylor commented on the issue:

[GitHub] phoenix issue #211: PHOENIX-3254 IndexId Sequence is incremented even if ind...

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/211 +1 on the changes (but please fix any formatting issues). Nice work, @ankitsinghal. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Commented] (PHOENIX-3254) IndexId Sequence is incremented even if index exists already.

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

[GitHub] phoenix pull request #211: PHOENIX-3254 IndexId Sequence is incremented even...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/211#discussion_r80950387 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java --- @@ -1499,6 +1502,53 @@ public void

[jira] [Commented] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530003#comment-15530003 ] Rajeshbabu Chintaguntla commented on PHOENIX-3336: -- [~houliang] Can you provide ddl

[jira] [Commented] (PHOENIX-3161) Check possibility of moving rebuilding code to coprocessor of data table.

[ https://issues.apache.org/jira/browse/PHOENIX-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529925#comment-15529925 ] Hadoop QA commented on PHOENIX-3161: {color:red}-1 overall{color}. Here are the results of testing

[GitHub] phoenix pull request #211: PHOENIX-3254 IndexId Sequence is incremented even...

Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/211#discussion_r80925250 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java --- @@ -1445,6 +1445,9 @@ public MetaDataResponse

[jira] [Updated] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi updated PHOENIX-3336: - Attachment: wrong-index-2.png > get the wrong results when using the local secondary index >

[jira] [Commented] (PHOENIX-3254) IndexId Sequence is incremented even if index exists already.

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

[jira] [Updated] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi updated PHOENIX-3336: - Description: When using phoenix local secondary index, two clients concurrent upsert data to

[jira] [Updated] (PHOENIX-3336) get the wrong results when using the local secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi updated PHOENIX-3336: - Attachment: wrong-index.png > get the wrong results when using the local secondary index >

[jira] [Commented] (PHOENIX-3254) IndexId Sequence is incremented even if index exists already.

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

[GitHub] phoenix pull request #211: PHOENIX-3254 IndexId Sequence is incremented even...

Github user chrajeshbabu commented on a diff in the pull request: https://github.com/apache/phoenix/pull/211#discussion_r80916280 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java --- @@ -1499,6 +1502,53 @@ public void

[jira] [Created] (PHOENIX-3336) get the wrong results when using the local secondary index

Houliang Qi created PHOENIX-3336: Summary: get the wrong results when using the local secondary index Key: PHOENIX-3336 URL: https://issues.apache.org/jira/browse/PHOENIX-3336 Project: Phoenix

[jira] [Updated] (PHOENIX-3161) Check possibility of moving rebuilding code to coprocessor of data table.

[ https://issues.apache.org/jira/browse/PHOENIX-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3161: --- Attachment: PHOENIX-3161.patch > Check possibility of moving rebuilding code to coprocessor

[jira] [Updated] (PHOENIX-3161) Check possibility of moving rebuilding code to coprocessor of data table.

[ https://issues.apache.org/jira/browse/PHOENIX-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3161: --- Attachment: (was: PHOENIX-3161.patch) > Check possibility of moving rebuilding code to

[jira] [Updated] (PHOENIX-3161) Check possibility of moving rebuilding code to coprocessor of data table.

[ https://issues.apache.org/jira/browse/PHOENIX-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3161: --- Attachment: PHOENIX-3161.patch [~jamestaylor], can you please review. This is what we

[jira] [Commented] (PHOENIX-3335) Improve documention of unsigned_long type mapping

[ https://issues.apache.org/jira/browse/PHOENIX-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528692#comment-15528692 ] William Yang commented on PHOENIX-3335: --- Build.sh failed on my MAC and I'm still trying to make it

[jira] [Updated] (PHOENIX-3335) Improve documention of unsigned_long type mapping

[ https://issues.apache.org/jira/browse/PHOENIX-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-3335: -- Attachment: PHOENIX-3335.patch > Improve documention of unsigned_long type mapping >

[jira] [Updated] (PHOENIX-3331) Bug in calculating minDisabledTimestamp for a batch

[ https://issues.apache.org/jira/browse/PHOENIX-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3331: -- Fix Version/s: 4.8.2 4.9.0 > Bug in calculating minDisabledTimestamp for a

[jira] [Commented] (PHOENIX-3331) Bug in calculating minDisabledTimestamp for a batch

[ https://issues.apache.org/jira/browse/PHOENIX-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528590#comment-15528590 ] James Taylor commented on PHOENIX-3331: --- +1 > Bug in calculating minDisabledTimestamp for a batch

[jira] [Resolved] (PHOENIX-3259) Create fat jar for transaction manager

[ https://issues.apache.org/jira/browse/PHOENIX-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3259. --- Resolution: Won't Fix The workaround is to remove the guava 12 lib from the hbase dir and

[jira] [Commented] (PHOENIX-3322) TPCH 100 query 2 exceeds size of hash cache

[ https://issues.apache.org/jira/browse/PHOENIX-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528545#comment-15528545 ] Lars Hofhansl commented on PHOENIX-3322: Anything between 100mb and 2gb to try? Also,