Re: Question about Git tag for 4.8.2 release and RC2

2017-05-14 Thread Lars George
Hi Josh, I think the point LarsF was making is that there are tags missing for 4.8.2, it is only the commits as you stated. See https://www.dropbox.com/s/xh3g008te08mwbg/Screenshot%202017-05-15%2008.32.45.png?dl=0 for reference of what we are seeing (which has no "tag" link to those commits). No w

[jira] [Commented] (PHOENIX-2454) Upsert with Double.NaN returns NumberFormatException

2017-05-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009968#comment-16009968 ] ASF GitHub Bot commented on PHOENIX-2454: - Github user chuxi closed the pull req

[GitHub] phoenix pull request #148: bugfix: PHOENIX-2454 Upsert with Double.NaN retur...

2017-05-14 Thread chuxi
Github user chuxi closed the pull request at: https://github.com/apache/phoenix/pull/148 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: HBase 2.0 future integration.

2017-05-14 Thread Andrew Purtell
HBase itself declares 0.98 EOL. There is nobody planning to make more releases of it. I was the former RM of this code line so am pretty sure about that, although this is open source, anyone can be lobbied to make another. There is already reason and certain eventuality regarding leaving it behi

Re: HBase 2.0 future integration.

2017-05-14 Thread Josh Elser
Sergey Soldatov wrote: Hi, Well, HBase 2.0 will be released in the near future and we need to think about adopting Phoenix to it. I tried to do that and already feel uncomfortable with the amount of changes related to existing and potential problems. There are the list of problems I'm aware at

[jira] [Commented] (PHOENIX-2640) Make it possible to kill running queries (and ideally list them too)

2017-05-14 Thread chenzhifa (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009941#comment-16009941 ] chenzhifa commented on PHOENIX-2640: Hi, is this feature still on the roadmap of pho

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

2017-05-14 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009833#comment-16009833 ] Josh Elser commented on PHOENIX-3807: - I've just hacked something together (albeit,

[jira] [Assigned] (PHOENIX-3807) Add server level metrics for secondary indexes

2017-05-14 Thread Josh Elser (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser reassigned PHOENIX-3807: --- Assignee: Josh Elser > Add server level metrics for secondary indexes > ---

[jira] [Updated] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Ohad Shacham (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated PHOENIX-3734: -- Attachment: PHOENIX-3734.v3.patch > Refactor Phoenix to use TAL instead of direct calls to Tep

[jira] [Updated] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Ohad Shacham (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated PHOENIX-3734: -- Attachment: (was: PHOENIX-3734.v2.patch) > Refactor Phoenix to use TAL instead of direct c

[jira] [Commented] (PHOENIX-3814) Unable to connect to Phoenix via Spark

2017-05-14 Thread Wajid Khattak (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009662#comment-16009662 ] Wajid Khattak commented on PHOENIX-3814: [~jmahonin] [~jamestaylor] Any updates

[jira] [Commented] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009659#comment-16009659 ] Hadoop QA commented on PHOENIX-3734: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Ohad Shacham (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated PHOENIX-3734: -- Attachment: (was: PHOENIX-3734.v1.patch) > Refactor Phoenix to use TAL instead of direct c

[jira] [Updated] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Ohad Shacham (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated PHOENIX-3734: -- Attachment: PHOENIX-3734.v2.patch > Refactor Phoenix to use TAL instead of direct calls to Tep

[jira] [Commented] (PHOENIX-3734) Refactor Phoenix to use TAL instead of direct calls to Tephra

2017-05-14 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009623#comment-16009623 ] Hadoop QA commented on PHOENIX-3734: {color:red}-1 overall{color}. Here are the res