[jira] [Created] (HBASE-21549) Add shell command for serial replication peer

2018-12-04 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21549: -- Summary: Add shell command for serial replication peer Key: HBASE-21549 URL: https://issues.apache.org/jira/browse/HBASE-21549 Project: HBase Issue

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Sean Busbey
That sounds like a fine plan for Phoenix to do. Please no changing minimum jdk requirements for HBase in minor releases. It's bad enough that we had to give up on Hadoop compatibility for minor releases. I'm sure it's only a matter of time before that puts us in a bad spot wrt JDK support. On

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Thomas D'Silva
I think Phoenix might end up moving the connector modules (spark, kakfa etc) and the query server into a separate repos so that they can be compiled with Java 8. Phoenix core would continue to maintain the same java version compatibility as HBase. On Tue, Dec 4, 2018 at 4:37 PM Andrew Purtell

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Andrew Purtell
I'm not taking a position, just pointing out that dropping Phoenix coprocessors compiled with Java 8 into a Java 7 runtime won't work. It is unclear at least to me if mixing HBase compiled with Java 7 and coprocessors compiled with Java 8 in a Java 8 runtime would be ok. Based on that I would say

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Zach York
Isn't Phoenix's compatibility guarantees separate from HBase's? If Phoenix only works with a Java8 environment, then couldn't Phoenix only support Java8 environments in releases after the Java 8 Avatica issue without requiring HBase's compatibility to drop support for Java7? While it's nice to

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Andrew Purtell
We have the current compatibility promise that we will build with Java 7 so folks using a Java 7 JRE can consume and deploy them. If we will be assuming Java 8 runtimes predominate, then we can build with Java 8. On Tue, Dec 4, 2018 at 4:15 PM Sean Busbey wrote: > What about installing

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Sean Busbey
What about installing Phoenix coprocessors built with Java 8 into a Java 8 runtime that's running the currently built for jdk7 HBase? Shouldn't that work fine? On Tue, Dec 4, 2018, 16:16 Andrew Purtell I thought only the Avatica module aka PQS must be compiled using Java 8? > Maybe you can

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Andrew Purtell
I thought only the Avatica module aka PQS must be compiled using Java 8? Maybe you can script a Phoenix build that uses the Java 7 compiler for the coprocessor modules and a Java 8 compiler only for the PQS? Otherwise, if all Phoenix modules including the coprocessor code are compiled with Java

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Josh Elser
On 12/4/18 3:28 PM, Sean Busbey wrote: On Tue, Dec 4, 2018 at 2:14 PM Josh Elser wrote: Phoenix depends on Avatica for its Phoenix Query Server. Avatica requires Java8. Thus, the impasse. Generally our maintaining JDK7 support shouldn't limit the ability of any downstream user to require a

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Sean Busbey
On Tue, Dec 4, 2018 at 2:14 PM Josh Elser wrote: > > Phoenix depends on Avatica for its Phoenix Query Server. Avatica > requires Java8. Thus, the impasse. > Generally our maintaining JDK7 support shouldn't limit the ability of any downstream user to require a newer JDK. Is there some context I'm

Re: [DISCUSS] JDK8 for >=1.5.x?

2018-12-04 Thread Josh Elser
Phoenix depends on Avatica for its Phoenix Query Server. Avatica requires Java8. Thus, the impasse. I'd pose the question: are we really doing our users a service for continuing to allow them to use Java7? Not trying to be contentious in asking that -- I am just (happily) seeing fewer and

[jira] [Resolved] (HBASE-21531) race between region report and region move causes master to kill RS

2018-12-04 Thread Sergey Shelukhin (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin resolved HBASE-21531. -- Resolution: Duplicate > race between region report and region move causes master to

Re: About to release 1.4.9

2018-12-04 Thread Andrew Purtell
Needed another round with HBASE-21464. I plan to commit a fix for this today, to unblock the release, and roll a new RC. On Thu, Nov 29, 2018 at 5:55 PM Andrew Purtell wrote: > Now that HBASE-21464 is in it is time for 1.4.9 RC0. Preparing and > testing tomorrow. Should have a vote on it next

[jira] [Created] (HBASE-21548) CLONE - WAL writer for recovered.edits file in WalSplitting should not require hflush from filesystem

2018-12-04 Thread Josh Elser (JIRA)
Josh Elser created HBASE-21548: -- Summary: CLONE - WAL writer for recovered.edits file in WalSplitting should not require hflush from filesystem Key: HBASE-21548 URL: https://issues.apache.org/jira/browse/HBASE-21548

[jira] [Created] (HBASE-21547) Precommit uses master flaky list for other branches

2018-12-04 Thread Peter Somogyi (JIRA)
Peter Somogyi created HBASE-21547: - Summary: Precommit uses master flaky list for other branches Key: HBASE-21547 URL: https://issues.apache.org/jira/browse/HBASE-21547 Project: HBase Issue

[jira] [Created] (HBASE-21546) ConnectException in TestThriftHttpServer

2018-12-04 Thread Peter Somogyi (JIRA)
Peter Somogyi created HBASE-21546: - Summary: ConnectException in TestThriftHttpServer Key: HBASE-21546 URL: https://issues.apache.org/jira/browse/HBASE-21546 Project: HBase Issue Type: Bug