Pratap created PHOENIX-4281:
---
Summary: Unable to connect apache Phoenix-4.10.0 to Hbase-1.1.1
Key: PHOENIX-4281
URL: https://issues.apache.org/jira/browse/PHOENIX-4281
Project: Phoenix
Issue Type:
Heh. I just remember that last time in August you said that you already
migrating to more recent version of HBase and have no problems to maintain
0.98 internally during for short time. As an alternative can we add shims,
so most of the difference in API can be grouped there and will be easy to
Until we migrate our production at Salesforce off of 0.98 we will still
have to support 0.98 internally, and a number of our staff are committers,
so I suspect there will be adequate support for the 0.98 branch for another
couple of releases.
On Mon, Oct 9, 2017 at 12:36 PM, Sergey Soldatov
I remember that we discussed that a couple times already without any final
decision, so let me raise this question again. HBase 2.0 is getting close
to the release and to support it we will need to do a lot of refactoring in
the code even just to get Phoenix compiled. And already we may start to
James Taylor created PHOENIX-4280:
-
Summary: Delete doesn't work when immutable indexes are in
building state
Key: PHOENIX-4280
URL: https://issues.apache.org/jira/browse/PHOENIX-4280
Project:
With 5 binding +1 votes and no -1 or +0 votes, the vote passes. I'll work
on getting the bits pushed out as needed.
Thanks,
James
On Mon, Oct 9, 2017 at 9:59 AM, James Taylor wrote:
> +1
>
> * Unit tests all pass
> * Rat check passes
> * All my manual tests pass
>
> On
+1
* Unit tests all pass
* Rat check passes
* All my manual tests pass
On Mon, Oct 9, 2017 at 8:47 AM, Ankit Singhal
wrote:
> +1
>
> -- Tested for any namespace mapping regression from 4.11 to 4.12.
> -- Upgrade from 4.11 to 4.12 is fine (vigilant testing, as we don't
+1
-- Tested for any namespace mapping regression from 4.11 to 4.12.
-- Upgrade from 4.11 to 4.12 is fine (vigilant testing, as we don't have
upgrade code this time)
-- Confirmed backward compatibility (Able to connect and do CRUD operations
with 4.11 client).
-- UT/ITs came clean.
On Mon,
+1 (binding)
* apache-rat:check OK
* Couldn't find any unexpected binaries
* Could build from source
* xsums/sigs OK
* Could run all UTs
Will try to do some more later today. Thanks all for getting this put
together.
On 10/4/17 3:46 AM, James Taylor wrote:
Hello Everyone,
This is a call
[
https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-4198:
---
Attachment: PHOENIX-4198_v4.patch
> Remove the need for users to have access to the Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-4198:
---
Attachment: (was: PHOENIX-4198_v4.patch)
> Remove the need for users to have access to
[
https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197052#comment-16197052
]
Ankit Singhal edited comment on PHOENIX-4198 at 10/9/17 2:27 PM:
-
bq.
[
https://issues.apache.org/jira/browse/PHOENIX-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197052#comment-16197052
]
Ankit Singhal commented on PHOENIX-4198:
I'm not sure we should require that a user who creates
+1
- built from source
- successfully ran all unit and integration tests
- collected stats using major compaction and update stats - estimates look
correct
- ran some basic manual tests involving global mutable and immutable
secondary indexes, looks good.
On Fri, Oct 6, 2017 at 1:03 PM, lars
14 matches
Mail list logo