Re: [DISCUSS] 5.0.0-beta release before month's end?

Time is running short for that "end of month", but here's some progress. I've been able to run through most of the ITs on a linux box. Yay! * There are known local index issues PHOENIX-4440. I saw LocalIndexIT, LocalIndexSplitMergeIT, and MutableRollbackIT all fail. Are you tracking PHOENIX-4440

Re: [DISCUSS] 5.0.0-beta release before month's end?

I don't think so. We (I use that loosely -- I'd hardly lump my contributions to this effort in the same room as the contributions of the others) have been moving fast to get back to functional state. This have definitely lapsed. It is a blocker to make sure 5.x isn't missing stuff from 4.x

Re: [DISCUSS] 5.0.0-beta release before month's end?

Have you guys back ported the removal of deprecated APIs patches to the 4.x branches? That'll probably help minimize the merge conflicts we see going forward. On Thu, Jan 18, 2018 at 1:03 PM, James Taylor wrote: > Awesome! That's great work!! > > On Thu, Jan 18, 2018 at

Re: [DISCUSS] 5.0.0-beta release before month's end?

Awesome! That's great work!! On Thu, Jan 18, 2018 at 1:00 PM, Josh Elser wrote: > Hah, funny you should ask! I was just thinking that I should send out a > note. > > * Rajeshbabu and Sergey are trying to track down a nasty issue that the > IndexScrutiny tool has caught where

Re: [DISCUSS] 5.0.0-beta release before month's end?

Hah, funny you should ask! I was just thinking that I should send out a note. * Rajeshbabu and Sergey are trying to track down a nasty issue that the IndexScrutiny tool has caught where there are dangling index records (PHOENIX-4534) * Rajeshbabu is also looking into some local index

Re: [DISCUSS] 5.0.0-beta release before month's end?

How are things looking with the 5.0.0 alpha/beta on HBase 2.x? On Thu, Jan 4, 2018 at 10:57 AM, Josh Elser wrote: > Good point. Perhaps "alpha" would be a better label? > > IIUC, the issue is that we need the HBase release, and then a Tephra > release, and then we can get

Re: [DISCUSS] 5.0.0-beta release before month's end?

Good point. Perhaps "alpha" would be a better label? IIUC, the issue is that we need the HBase release, and then a Tephra release, and then we can get Tephra fixed for Phoenix5. Perhaps Ankit can provide some more color to the situation. On 1/4/18 12:07 PM, Nick Dimiduk wrote: Isn't Tephra

Re: [DISCUSS] 5.0.0-beta release before month's end?

Isn't Tephra integration mandatory for transaction support? What happens to a user who has TRANSACTIONAL=true tables when they upgrade? This can't really fail gracefully. I guess transaction support is still marked 'beta', but still, this would be a regression of functionality in "base Phoenix".

Re: [DISCUSS] 5.0.0-beta release before month's end?

Talked to Rajeshbabu and Ankit offline this morning. Sounds like there are a few integration points which are still lacking: * phoenix-hive: PHOENIX-4423 * phoenix-spark: untested (probably broken against newest Spark) * phoenix-kafka: untested (probably broken against newest Kafka -- see

[DISCUSS] 5.0.0-beta release before month's end?

Happy New Year folks! I'd like to test the waters: what do people think about trying to get a 5.0.0 "beta" release out to the community before the end of January? HBase is doing the same right now with 2.0.0. My thinking is that if things are stable "enough", getting a base for people to use