[
https://issues.apache.org/jira/browse/HBASE-21080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21080.
---
Resolution: Duplicate
Release Note: Dupe of HBASE-21080
Dupe of HBASE-21080
> Collectors.toMap uses
stack created HBASE-21081:
-
Summary: Trim Master memory usage, part 2
Key: HBASE-21081
URL: https://issues.apache.org/jira/browse/HBASE-21081
Project: HBase
Issue Type: Bug
Affects Versions:
stack created HBASE-21080:
-
Summary: Collectors.toMap uses a byte [] for key
Key: HBASE-21080
URL: https://issues.apache.org/jira/browse/HBASE-21080
Project: HBase
Issue Type: Bug
A couple of other contribution concerns:
a) Yetus Precommit works with github PRs, but the ASF Jenkins admin
job that sends requests over to our job that runs the precommit tests
does not. It's a minor issue (in that collectively we know what has to
change), but someone will have to do the work.
This came up at the recent devs meeting: could we move to github flow
committing to Apache HBase? Do folks want this? If so, what would it take?
What would it look like?
The new gitbox repos at apache allow contribution back into apache via
github tooling: PRs can be merged into apache repos with
Agree with Andrew, adding SQL capability to HBase will be little messy task and
not much value added to HBase when solutions like phoenix already available.
>>> If SQL support is really the goal it would be better to assist there. Or,
>>> if the goal is the barest minimal SQL-like thing
On Mon, Aug 20, 2018 at 6:36 PM Sean Busbey wrote:
> On Mon, Aug 20, 2018 at 11:33 AM, Josh Elser wrote:
> > Thanks for writing this up, Stack. Very nice read.
> >
> > Snipping out some subjects to reply to directly:
> >
> > On 8/19/18 6:48 AM, Stack wrote:
> >
> >> GITHUB
> >> Can hbase adopt
On Mon, Aug 20, 2018 at 11:33 AM, Josh Elser wrote:
> Thanks for writing this up, Stack. Very nice read.
>
> Snipping out some subjects to reply to directly:
>
> On 8/19/18 6:48 AM, Stack wrote:
>
>> GITHUB
>> Can hbase adopt the github dev flow? Support PRs?
>> Its a case of just starting the
Krish Dey created HBASE-21079:
-
Summary: Non admin can split or compact from master UI even when
the cluster is secured
Key: HBASE-21079
URL: https://issues.apache.org/jira/browse/HBASE-21079
Project:
stack created HBASE-21078:
-
Summary: [amv2] CODE-BUG NPE in RTP doing Unassign
Key: HBASE-21078
URL: https://issues.apache.org/jira/browse/HBASE-21078
Project: HBase
Issue Type: Bug
Great. I'll take that as an action-item.
HBase'rs. Please follow along on dev@phoenix (now with 90% fewer emails
if you haven't yet noticed!) if you're interested in giving us your
opinions.
On 8/20/18 4:45 PM, Andrew Purtell wrote:
Yes I think it would be worthwhile. Would-be user feedback
Yes I think it would be worthwhile. Would-be user feedback on usability is
the best kind of feedback a project can get.
On Mon, Aug 20, 2018 at 1:21 PM Josh Elser wrote:
> Strong agree on your points here. You cover a lot of the intricacies
> that I glossed over. Thank you for taking the time
[
https://issues.apache.org/jira/browse/HBASE-21043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21043.
---
Resolution: Duplicate
Release Note: Dupe of HBASE-21043
Resolved as dupe of HBASE-21043.
> TestShell
Strong agree on your points here. You cover a lot of the intricacies
that I glossed over. Thank you for taking the time to write that all down.
I am happy to spin out the points I identified to dev@phoenix if you (or
others) think that they are all worthwhile discussions to have.
On 8/20/18
I'm on Eclipse, but I think I'm an "old dog" for not having switched
over by now ;). To my knowledge, more devs are using Intellij than
Eclipse/other.
If you stumble onto anything that would be good for other devs, I think
that would be a nice addition to the HBase book.
On 8/19/18 2:43 PM,
A fair point indeed.
On Mon, Aug 20, 2018 at 12:32 PM Vladimir Rodionov
wrote:
> C* fares much better with their (very limited) CQL than HBase with its
> advanced Phoenix.
> Just saying.
>
> My 2c
>
> -Vlad
>
>
>
> On Mon, Aug 20, 2018 at 12:06 PM, Andrew Purtell
> wrote:
>
> > It would be
C* fares much better with their (very limited) CQL than HBase with its
advanced Phoenix.
Just saying.
My 2c
-Vlad
On Mon, Aug 20, 2018 at 12:06 PM, Andrew Purtell
wrote:
> It would be helpful if someone could forward the relevant bits of Phoenix
> discussion to the Phoenix dev list. One
Vladimir Rodionov created HBASE-21077:
-
Summary: MR job launched by hbase incremental backup command
failed with FileNotFoundException
Key: HBASE-21077
URL: https://issues.apache.org/jira/browse/HBASE-21077
It would be helpful if someone could forward the relevant bits of Phoenix
discussion to the Phoenix dev list. One thing I know that project lacks is
usability feedback. I don't see anyone writing in with suggestions, mainly
complaining about it on a HBase list somewhere. Could just be I lack
Thanks for writing this up, Stack. Very nice read.
Snipping out some subjects to reply to directly:
On 8/19/18 6:48 AM, Stack wrote:
GITHUB
Can hbase adopt the github dev flow? Support PRs?
Its a case of just starting the discussion on the dev list?
Do we lose review/commentary information if
On 8/19/18 11:51 PM, Yu Li wrote:
bq. One attendee asked where does hbase want to go? Is it storage or a db
system? Need to draw a sharp line. Do what we are good at.
Wish more people could respond to this question, maybe throwing a separate
thread even to the @user list? Shall we have some
This was done by someone already.
On 8/17/18 12:45 PM, Abhishek Goyal wrote:
Hi,
I was hoping to get an invite to the HBase Slack channel. Thanks a lot!
Best,
Abhishek
Ted Yu created HBASE-21076:
--
Summary: TestTableResource fails with NPE
Key: HBASE-21076
URL: https://issues.apache.org/jira/browse/HBASE-21076
Project: HBase
Issue Type: Test
Reporter:
[
https://issues.apache.org/jira/browse/HBASE-21006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon resolved HBASE-21006.
-
Resolution: Duplicate
> Balancer - data locality drops 30-40% across all nodes after every
>
[
https://issues.apache.org/jira/browse/HBASE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-21016.
---
Resolution: Fixed
Included in the latest patch of HBASE-20881.
> Find another way to test the
Duo Zhang created HBASE-21075:
-
Summary: Confirm that we can rolling upgrade from 2.0.x and 2.1.x
to 2.2.x after HBASE-20881
Key: HBASE-21075
URL: https://issues.apache.org/jira/browse/HBASE-21075
26 matches
Mail list logo
