[
https://issues.apache.org/jira/browse/PHOENIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated PHOENIX-5905:
-
Attachment: (was: PHOENIX-5905.master.addendum3.patch)
> Reset
[
https://issues.apache.org/jira/browse/PHOENIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated PHOENIX-5905:
-
Comment: was deleted
(was: Attached addendum simplified the testcases
HBase 2.0 and 2.1 has been EOL now. Does phoenix need to support them?
swaroopa kadam 于2020年6月17日周三 上午12:32写道：
> yes, that’s a good idea.
>
> On Tue, Jun 16, 2020 at 9:29 AM Josh Elser wrote:
>
> > Sounds like we should try to update precommit to at least compile
> > against _a version_ in
[
https://issues.apache.org/jira/browse/PHOENIX-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan reassigned PHOENIX-5960:
--
Assignee: Xinyi Yan
> Creating a view on a non-existent table throws the wrong exception
>
[
https://issues.apache.org/jira/browse/PHOENIX-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir OZDEMIR updated PHOENIX-5928:
---
Attachment: PHOENIX-5928.4.x.007.patch
> Index rebuilds without replaying data table
[
https://issues.apache.org/jira/browse/PHOENIX-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser reassigned PHOENIX-5901:
---
Assignee: Josh Elser (was: Istvan Toth)
> Add LICENSE and NOTICE files to
[
https://issues.apache.org/jira/browse/PHOENIX-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated PHOENIX-5905:
-
Attachment: PHOENIX-5905.master.addendum3.patch
> Reset user to hbase
[
https://issues.apache.org/jira/browse/PHOENIX-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-5730:
--
Labels: phoenix-hardening quality-improvement (was: )
> Stabilize tests on master
yes, that’s a good idea.
On Tue, Jun 16, 2020 at 9:29 AM Josh Elser wrote:
> Sounds like we should try to update precommit to at least compile
> against _a version_ in each line 2.1/2.2/2.3 for master. Thoughts?
>
> On 6/16/20 11:57 AM, swaroopa kadam wrote:
> > Thank you for the replies
Sounds like we should try to update precommit to at least compile
against _a version_ in each line 2.1/2.2/2.3 for master. Thoughts?
On 6/16/20 11:57 AM, swaroopa kadam wrote:
Thank you for the replies everyone!
It puts me at ease by knowing the issue has been identified and being
fixed.
Yup, let's just draw a number (whatever we'd like, as long as it follows
the standard PEP for versioning). When we release it, we can advertise
whatever level of stability we expect it to have (i.e. "This is an
alpha, you can try it if you want").
ASF is very strict when it comes to releases
Thank you for the replies everyone!
It puts me at ease by knowing the issue has been identified and being
fixed.
Thanks!
On Tue, Jun 16, 2020 at 4:11 AM rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:
> I am on the PHOENIX-5905 compilation issue and will fix it today.
>
> On Tue, Jun
[
https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-5962:
Assignee: Richard Antal
> Stabilize builds
>
>
> Key:
[
https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5962:
---
Attachment: PHOENIX-5962.master.v2.patch
> Stabilize builds
>
>
>
[
https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5962:
---
Attachment: PHOENIX-5962.master.v1.patch
> Stabilize builds
>
>
>
[
https://issues.apache.org/jira/browse/PHOENIX-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5962:
---
Attachment: (was: PHOENIX-5962.master.v1.patch)
> Stabilize builds
>
Richard Antal created PHOENIX-5962:
--
Summary: Stabilize builds
Key: PHOENIX-5962
URL: https://issues.apache.org/jira/browse/PHOENIX-5962
Project: Phoenix
Issue Type: Task
I am on the PHOENIX-5905 compilation issue and will fix it today.
On Tue, Jun 16, 2020 at 3:07 PM cheng...@apache.org
wrote:
>
>
>
> PHOENIX-5905 caused the master branch compile broken, because
> org.apache.hadoop.hbase.security.access.GetUserPermissionsRequest is only
> available in hbase
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-5956:
--
Description: When LHS left semi join RHS through {{SortMergeJoinPlan}}, if
RHS is end and returns
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei reassigned PHOENIX-5956:
-
Assignee: chenglei
> Optimize LeftSemiJoin For SortMergeJoin
>
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-5956:
--
Attachment: PHOENIX-5956_v1-4.x.patch
> Optimize LeftSemiJoin For SortMergeJoin
>
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-5956:
--
Description: When LHS left semi join RHS through SortMergeJoin, if RHS is
end and returns null, then
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-5956:
--
Fix Version/s: 4.16.0
> Optimize LeftSemiJoin For SortMergeJoin
>
[
https://issues.apache.org/jira/browse/PHOENIX-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-5956:
--
Fix Version/s: 5.1.0
> Optimize LeftSemiJoin For SortMergeJoin
>
PHOENIX-5905 caused the master branch compile broken, because
org.apache.hadoop.hbase.security.access.GetUserPermissionsRequest is only
available in hbase 2.2.x,
so when the hbase.profile=2.0 or hbase.profile=2.1, the compiler boken,
Should we revert PHOENIX-5905 for the moment?
The error
PHOENIX-5905 caused the master branch compile broken, because
org.apache.hadoop.hbase.security.access.GetUserPermissionsRequest is only
available in hbase 2.2.x,
so when the hbase.profile=2.0 or hbase.profile=2.1, the compiler boken,
Should we revert PHOENIX-5905 for the moment?
The error
The Beam guide looks interesting, we could certainly borrow from it.
I'm fine with your suggested process. Here's my interpretation of it:
- No dev releases on PyPI
- Decoupling PhoenixDB versioning from PQS versioning
- Making a proper minor/patch release when important features/fixes
Hi!
In some cases specifying non-default HBase and Hadoop versions can cause
this.
Please report your full maven command line, and I'll look into it.
In the meantime you can disable the dependency check with -D
mdep.analyze.skip=true
Istvan
On Mon, Jun 15, 2020 at 7:57 PM swaroopa kadam
wrote:
What we really need is getting our test suite (and infra) sorted out.
Your suggestions are already part of the process, it's just that lately
everyone ignores them, because the precommit tests have been next to
useless for a good while.
I think that if developers can be reasonably sure that the
29 matches
Mail list logo
