[jira] [Commented] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829325#comment-15829325 ] Hadoop QA commented on PHOENIX-3609: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (PHOENIX-3549) Fail if binary field in CSV is not properly base64 encoded

[ https://issues.apache.org/jira/browse/PHOENIX-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3549: --- Fix Version/s: 4.10.0 > Fail if binary field in CSV is not properly base64 encoded > ---

[jira] [Reopened] (PHOENIX-3548) Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py

[ https://issues.apache.org/jira/browse/PHOENIX-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reopened PHOENIX-3548: Sorry, closed this by mistake.. documentation is yet to get in, so keeping it open. > Create

[jira] [Commented] (PHOENIX-3549) Fail if binary field in CSV is not properly base64 encoded

[ https://issues.apache.org/jira/browse/PHOENIX-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829319#comment-15829319 ] Ankit Singhal commented on PHOENIX-3549: This is committed as a part of PHOENIX-

[jira] [Resolved] (PHOENIX-3549) Fail if binary field in CSV is not properly base64 encoded

[ https://issues.apache.org/jira/browse/PHOENIX-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3549. Resolution: Fixed > Fail if binary field in CSV is not properly base64 encoded > -

[jira] [Updated] (PHOENIX-3610) Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store

[ https://issues.apache.org/jira/browse/PHOENIX-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3610: --- Description: Physical Tablename is used instead of phoenix table name . IndexHalfStoreFileR

[jira] [Created] (PHOENIX-3610) Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store

Ankit Singhal created PHOENIX-3610: -- Summary: Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store Key: PHOENIX-3610 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3609: --- Attachment: PHOENIX-3609.patch > Detect and fix corrupted local index region during compacti

[jira] [Updated] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3609: --- Attachment: (was: BUG-67084_v1.patch) > Detect and fix corrupted local index region duri

[jira] [Updated] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3609: --- Attachment: BUG-67084_v1.patch [~chrajeshbab...@gmail.com], can you please review the attach

[jira] [Created] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

Ankit Singhal created PHOENIX-3609: -- Summary: Detect and fix corrupted local index region during compaction Key: PHOENIX-3609 URL: https://issues.apache.org/jira/browse/PHOENIX-3609 Project: Phoenix

[jira] [Commented] (PHOENIX-3608) KeyRange interset should return EMPTY_RANGE when one of it is NULL_RANGE

[ https://issues.apache.org/jira/browse/PHOENIX-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829297#comment-15829297 ] Hadoop QA commented on PHOENIX-3608: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (PHOENIX-3608) KeyRange interset should return EMPTY_RANGE when one of it is NULL_RANGE

[ https://issues.apache.org/jira/browse/PHOENIX-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3608: - Attachment: PHOENIX-3608.patch Here is trivial patch. [~jamestaylor] ple

[jira] [Created] (PHOENIX-3608) KeyRange interset should return EMPTY_RANGE when one of it is NULL_RANGE

Rajeshbabu Chintaguntla created PHOENIX-3608: Summary: KeyRange interset should return EMPTY_RANGE when one of it is NULL_RANGE Key: PHOENIX-3608 URL: https://issues.apache.org/jira/browse/PHOENIX-3608

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829044#comment-15829044 ] Andrew Purtell commented on PHOENIX-3607: - We can evict from cache by LRU regard

[jira] [Comment Edited] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829028#comment-15829028 ] Geoffrey Jacoby edited comment on PHOENIX-3607 at 1/19/17 12:14 AM: --

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829028#comment-15829028 ] Geoffrey Jacoby commented on PHOENIX-3607: -- The discussion in https://issues.ap

[jira] [Updated] (PHOENIX-3519) Add COLUMN_ENCODED_BYTES table property

[ https://issues.apache.org/jira/browse/PHOENIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3519: Attachment: PHOENIX-3519-v2.patch [~jamestaylor] Thanks for the feedback, I have attached

Phoenix ODBC user experience

Hi There, If you are using Phoenix ODBC driver, could you please share your experience interms of stability of the set-up (since it requires Query server) and read/write performance. Performance is subjective but will give us some data points to assess the option of using ODBC drivers with C++.

[jira] [Comment Edited] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828857#comment-15828857 ] Thomas D'Silva edited comment on PHOENIX-3586 at 1/18/17 10:11 PM: ---

[jira] [Updated] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3586: Attachment: PHOENIX-3586-v3.patch I have attached a v3 patch which sets the immutableStor

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828822#comment-15828822 ] Geoffrey Jacoby commented on PHOENIX-3607: -- So then I think it comes down to a

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828733#comment-15828733 ] Josh Elser commented on PHOENIX-3607: - Thanks, Geoffrey. This is super helpful. bq.

[jira] [Commented] (PHOENIX-3584) Expose metrics for ConnectionQueryServices instances and their allocators in the JVM

[ https://issues.apache.org/jira/browse/PHOENIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828715#comment-15828715 ] Sergey Soldatov commented on PHOENIX-3584: -- Can this trace logging in Connectio

[jira] [Commented] (PHOENIX-3519) Add COLUMN_ENCODED_BYTES table property

[ https://issues.apache.org/jira/browse/PHOENIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828692#comment-15828692 ] James Taylor commented on PHOENIX-3519: --- Thanks for the patch, [~tdsilva]. Here's

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828684#comment-15828684 ] Geoffrey Jacoby commented on PHOENIX-3607: -- [~elserj] We're seeing Phoenix conn

[jira] [Commented] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828665#comment-15828665 ] James Taylor commented on PHOENIX-3586: --- bq. If we derive the immutableStorageSche

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828655#comment-15828655 ] Josh Elser commented on PHOENIX-3607: - I think there were issues WRT proxy-user auth

[jira] [Updated] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3586: Attachment: PHOENIX-3586-v2.patch > Add StorageScheme table property to allow users to spe

[jira] [Updated] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3586: Attachment: (was: PHOENIX-3586-v2.patch) > Add StorageScheme table property to allow u

[jira] [Updated] (PHOENIX-3586) Add StorageScheme table property to allow users to specify their custom storage schemes

[ https://issues.apache.org/jira/browse/PHOENIX-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3586: Attachment: PHOENIX-3586-v2.patch [~jamestaylor] Thanks for the review, I have attached a

[jira] [Commented] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

[ https://issues.apache.org/jira/browse/PHOENIX-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828553#comment-15828553 ] James Taylor commented on PHOENIX-3607: --- [~elserj] - remember PHOENIX-3189 and the

[jira] [Created] (PHOENIX-3607) Change hashCode calculation for caching ConnectionQueryServicesImpls

Geoffrey Jacoby created PHOENIX-3607: Summary: Change hashCode calculation for caching ConnectionQueryServicesImpls Key: PHOENIX-3607 URL: https://issues.apache.org/jira/browse/PHOENIX-3607 Projec

[jira] [Commented] (PHOENIX-3600) Core MapReduce classes don't provide location info

[ https://issues.apache.org/jira/browse/PHOENIX-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828412#comment-15828412 ] Hadoop QA commented on PHOENIX-3600: {color:red}-1 overall{color}. Here are the res

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been puttin

[jira] [Commented] (PHOENIX-3601) PhoenixRDD doesn't expose the preferred node locations to Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828357#comment-15828357 ] Josh Mahonin commented on PHOENIX-3601: --- Trivial patch, most of the functionality

[jira] [Updated] (PHOENIX-3601) PhoenixRDD doesn't expose the preferred node locations to Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-3601: -- Attachment: PHOENIX-3601.patch > PhoenixRDD doesn't expose the preferred node locations to Spa

[jira] [Commented] (PHOENIX-3600) Core MapReduce classes don't provide location info

[ https://issues.apache.org/jira/browse/PHOENIX-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828307#comment-15828307 ] Josh Mahonin commented on PHOENIX-3600: --- Mostly just ported the Phoenix/MR specifi

[jira] [Updated] (PHOENIX-3600) Core MapReduce classes don't provide location info

[ https://issues.apache.org/jira/browse/PHOENIX-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-3600: -- Attachment: PHOENIX-3600.patch > Core MapReduce classes don't provide location info >

[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 th

[jira] [Commented] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827706#comment-15827706 ] Hudson commented on PHOENIX-3134: - SUCCESS: Integrated in Jenkins build Phoenix-master #

[jira] [Resolved] (PHOENIX-3548) Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py

[ https://issues.apache.org/jira/browse/PHOENIX-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3548. Resolution: Fixed committed as part of PHOENIX-3134. > Create documentation for binaryEn

[jira] [Updated] (PHOENIX-3548) Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py

[ https://issues.apache.org/jira/browse/PHOENIX-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3548: --- Fix Version/s: 4.10.0 > Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.