Phoenix 5.0 + Cloudera CDH 6.0 Integration

Hi all, Is there anyone working towards Phoenix 5.0 / Cloudera (CDH) 6.0 integration at this point? I could not find any related JIRA for this after a quick search, and wanted to check here first before adding one. If I were to attempt this myself, is there a suggested approach? I can see from

[jira] [Updated] (PHOENIX-4849) UPSERT SELECT fails with stale region boundary exception after a split

[ https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4849: Attachment: SerialIterators.diff > UPSERT SELECT fails with stale region boundary

Re: Salting based on partial rowkeys

Ahh, I get you now. For a composite primary key made up of columns 1 through N, you want similar controls to compute the value of the salt based on a sequence of the columns 1 through M where M <= N (instead of always on all columns). For large numbers of salt buckets and a scan over a

[jira] [Updated] (PHOENIX-4880) Phoenix IndexTool doesn't work on HBase2 per documentation

[ https://issues.apache.org/jira/browse/PHOENIX-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4880: Fix Version/s: (was: 4.15.0) > Phoenix IndexTool doesn't work on HBase2 per documentation >

Re: Salting based on partial rowkeys

In case the text formatting is lost below, I also added it as a comment in the JIRA ticket: https://issues.apache.org/jira/browse/PHOENIX-4757 On Thu, Sep 13, 2018 at 3:24 PM, Gerald Sangudi wrote: > Sorry I missed Josh's reply; I've subscribed to the dev list now. > > Below is a

Re: Salting based on partial rowkeys

Sorry I missed Josh's reply; I've subscribed to the dev list now. Below is a copy-and-paste from our internal document. Thanks in advance for your review and additional feedback on this. Gerald *BackgroundWe make extensive use of multi-column rowkeys and salting

[jira] [Assigned] (PHOENIX-4594) Perform binary search on guideposts during query compilation

[ https://issues.apache.org/jira/browse/PHOENIX-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin Shi reassigned PHOENIX-4594: Assignee: Bin Shi (was: Abhishek Singh Chouhan) Attachment: PHOENIX-4594-0913.patch

Access Client Side Metrics for PhoenixRDD usage

Hi all, I see that LLAM-1819 had implemented client metric collection mechanism in the PhoenixRecordReader class, which I believe is then used by PhoenixInputFormat and then used by PhoenixRDD, but I am having trouble locating example of how we can access the metric on

Re: Salting based on partial rowkeys

Gerald, I think you missed Josh's reply here : https://lists.apache.org/thread.html/c5145461805429622a410c23c1199d578e146a5c94511b2d5833438b@%3Cdev.phoenix.apache.org%3E Could you explain how using a subset of the pk columns to generate the salt byte helps with partitioning, aggregations etc?

Re: Salting based on partial rowkeys

Hi folks, Any thoughts or feedback on this? Thanks, Gerald On Mon, Sep 10, 2018 at 1:56 PM, Gerald Sangudi wrote: > Hello folks, > > We have a requirement for salting based on partial, rather than full, > rowkeys. My colleague Mike Polcari has identified the requirement and > proposed an

[jira] [Created] (PHOENIX-4904) NPE exception when use non-existing filed in function

Jaanai created PHOENIX-4904: --- Summary: NPE exception when use non-existing filed in function Key: PHOENIX-4904 URL: https://issues.apache.org/jira/browse/PHOENIX-4904 Project: Phoenix Issue Type:

[jira] [Updated] (PHOENIX-4904) NPE exception when use non-existing filed in function

[ https://issues.apache.org/jira/browse/PHOENIX-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaanai updated PHOENIX-4904: Issue Type: Bug (was: New Feature) > NPE exception when use non-existing filed in function >