[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Summary: Phoenix may incorrectly replace TableResultIterators after HBase
region splits
You're right, Josh, I was mistaken, there was indeed a 5.0.0 release. But
I meant the same as your last bit - branch off 5.0.0 and only put in HBase
2.0.2 and critical fixes for 5.0.1.
On Wed, Sep 26, 2018 at 6:40 PM Josh Elser wrote:
> No, Vincent, that is wrong. There *was* a 5.0.0-alpha
No, Vincent, that is wrong. There *was* a 5.0.0-alpha release. Then,
there was a 5.0.0 release (not called alpha).
To Thomas' original question: I don't think we need to keep 4.15 in
lock-step with 5.x, but if 5.x isn't ready for release for the same
reason 4.15 is not ready for release, then
[
https://issues.apache.org/jira/browse/PHOENIX-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated PHOENIX-4930:
Attachment: PHOENIX-4930.patch
> Add test for a simple SELECT query during a split
>
Thomas D'Silva created PHOENIX-4930:
---
Summary: Add test for a simple SELECT query during a split
Key: PHOENIX-4930
URL: https://issues.apache.org/jira/browse/PHOENIX-4930
Project: Phoenix
The 5.0.0 release apparently was an 'alpha'. I think we should do a 5.0.1
which can work with HBase 2.0.2 and remove the 'alpha'.
5.0 has feature parity with 4.14.
5.1 would have feature parity with 4.15, the main addition being splittable
syscat
On a sidenote, I've been planning a 4.14.1
If possible please continue to release for one or more of the HBase 1.x
code lines. I have a feeling the HBase 1.xes will be in production for a
long time yet.
On Wed, Sep 26, 2018 at 11:42 AM Thomas D'Silva
wrote:
> Would we also release 4.15, or just a new 5.x release to support HBase
>
[
https://issues.apache.org/jira/browse/PHOENIX-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Poon updated PHOENIX-4929:
--
Attachment: QueryCompilerTest.java
> IndexOutOfBoundsException when casting timestamp to
Vincent Poon created PHOENIX-4929:
-
Summary: IndexOutOfBoundsException when casting timestamp to date
Key: PHOENIX-4929
URL: https://issues.apache.org/jira/browse/PHOENIX-4929
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva resolved PHOENIX-4097.
-
Resolution: Fixed
> Ensure new rows not seen if split occurs during UPSERT SELECT to
Would we also release 4.15, or just a new 5.x release to support HBase
2.0.1/2.0.2 ? PHOENIX-3534 has a few follow-up JIRAs that are needed for
splittable system catalog.
On Tue, Sep 25, 2018 at 7:56 PM, Josh Elser wrote:
> On the user@phoenix list, Francis pointed out how Phoenix 5.0.0 only
>
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Fix Version/s: 5.1.0
4.14.1
4.15.0
> Phoenix may
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Summary: Phoenix may generate incorrectly replace TableResultIterators
after HBase region
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Attachment: PHOENIX-4849-master-v7.patch
> UPSERT SELECT fails with stale region boundary
[
https://issues.apache.org/jira/browse/PHOENIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-4849:
---
Attachment: PHOENIX-4849-4.x-HBase-1.4-v7.patch
> UPSERT SELECT fails with stale region
Aman Poonia created PHOENIX-4928:
Summary: Local index is always in building state
Key: PHOENIX-4928
URL: https://issues.apache.org/jira/browse/PHOENIX-4928
Project: Phoenix
Issue Type: Bug
16 matches
Mail list logo
