As described in HBASE-22728, are we planning to get a 1.5 branch for 4.14
or are we targeting 4.15 and 5.x for HBase 1.5?
On Tue, Aug 6, 2019, 5:01 PM swaroopa kadam
wrote:
> non-binding -1
>
> Uncovered a blocker Jira PHOENIX-5348.
> I will be back with RC2 soon.
>
> Thank you.
>
> On Tue, Aug
[
https://issues.apache.org/jira/browse/PHOENIX-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam resolved PHOENIX-5429.
-
Resolution: Not A Bug
> IndexTool doesn't rebuild indexes from data table after truncat
[
https://issues.apache.org/jira/browse/PHOENIX-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-5170:
--
Fix Version/s: 4.15.0
> Update meta timestamp of parent table when dropping index
> -
[
https://issues.apache.org/jira/browse/PHOENIX-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved PHOENIX-5394.
-
Resolution: Fixed
> Integration tests not running for phoenix-queryserver, general build cruft.
Can we target 4.15 for HBase 1.5 branch to have at least one branch
compatible with the incoming 1.x HBase release? HBase 1.3 and 1.4 are being
discussed for EOL and also depends on an EOL version of Hadoop (2.7) so
HBase 1.5 seems to be the bridge release.
On Thu, Jul 18, 2019, 2:40 PM la...@apac
If HBase does not patch 1.3 or 1.4 for the Jackson CVE, the recommendation
for concerned users would be to use 1.5. I think that sounds like we would
want to get a 1.5 branch for 4.14, unless we think 4.15 is almost ready?
Either way, I am not sure if this would need to block 4.14.3, since it will
Hi Artem,
The 4.15.0 release will be done for HBase-1.3, 1.4 and 1.5.
Thanks,
Chinmay
On Wed, Aug 7, 2019 at 2:35 PM Artem Ervits wrote:
> Can we target 4.15 for HBase 1.5 branch to have at least one branch
> compatible with the incoming 1.x HBase release? HBase 1.3 and 1.4 are being
> discuss
I agree with William that there's no need to block 4.14.3's 1.3 and
1.4-based releases on HBase 1.5. Soon-but-later, when HBase 1.5 lands I
think we should do a followup 4.14.3 (or .4, if other critical JIRAs are
necessary) release based on 1.5.
Then, based on the branch EOL discussions the HBase
[
https://issues.apache.org/jira/browse/PHOENIX-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miles Spielberg updated PHOENIX-5136:
-
Attachment: PHOENIX-5136.master.v4.patch
> Rows with null values inserted by UPSERT ..
Didn't mean to insinuate to block 4.14.3, just wanted to understand where
community is focusing. Thank you all for chiming in.
On Wed, Aug 7, 2019, 6:30 PM Geoffrey Jacoby wrote:
> I agree with William that there's no need to block 4.14.3's 1.3 and
> 1.4-based releases on HBase 1.5. Soon-but-lat
[
https://issues.apache.org/jira/browse/PHOENIX-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Gupta updated PHOENIX-5390:
Attachment: PHOENIX-5390.v2.patch
> Cleanup anonymous inner classes in phoenix-core/main
> --
Thanks Artem for bringing up HBASE-22728 to help Phoenix stay ahead of the
game :)
On Wed, Aug 7, 2019 at 3:41 PM Artem Ervits wrote:
> Didn't mean to insinuate to block 4.14.3, just wanted to understand where
> community is focusing. Thank you all for chiming in.
>
> On Wed, Aug 7, 2019, 6:30 P
12 matches
Mail list logo
