Guanghao Zhang created HBASE-15515:
--
Summary: Improve LocalityBasedCandidateGenerator in Balancer
Key: HBASE-15515
URL: https://issues.apache.org/jira/browse/HBASE-15515
Project: HBase
Issue
Vladimir Rodionov created HBASE-15514:
-
Summary: Single (or small number) of Column Family in Mutation
optimization
Key: HBASE-15514
URL: https://issues.apache.org/jira/browse/HBASE-15514
Project:
At least include HBASE-15400 in 1.3 please...
Otherwise these things can only be integrated in 1.4 since DTCP can not be
used together with DefaultStoreEngine after HBASE-15400 getting in.
2016-03-22 2:03 GMT+08:00 Enis Söztutar :
> You may want to track https://issues.apache.org/jira/browse/HBAS
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reopened HBASE-15360:
> Fix flaky TestSimpleRpcScheduler
>
>
> Key: HBASE-15360
>
Vladimir Rodionov created HBASE-15513:
-
Summary: hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
Key: HBASE-15513
URL: https://issues.apache.org/jira/browse/HBASE-15513
Project: HBase
Vladimir Rodionov created HBASE-15512:
-
Summary: Avoid cell allocation on Store.add(Cell)
Key: HBASE-15512
URL: https://issues.apache.org/jira/browse/HBASE-15512
Project: HBase
Issue Type
Esteban Gutierrez created HBASE-15511:
-
Summary: ClusterStatus should be able
Key: HBASE-15511
URL: https://issues.apache.org/jira/browse/HBASE-15511
Project: HBase
Issue Type: Improveme
bq. the branch "hbase-6721" is not related to the actual patch(es)
In that case, it is Okay to drop this branch.
On Mon, Mar 21, 2016 at 11:51 AM, Sean Busbey wrote:
> We should not accumulate feature branches indefinitely as it makes the repo
> increasingly unwieldy.
>
> AFAICT, the branch "hb
Vladimir Rodionov created HBASE-15510:
-
Summary: Reuse buffer inside RpcServer$Connection.readAndProcess
Key: HBASE-15510
URL: https://issues.apache.org/jira/browse/HBASE-15510
Project: HBase
Vladimir Rodionov created HBASE-15509:
-
Summary: Avoid copy of block data in HFileBlock$Writer.finishBlock
Key: HBASE-15509
URL: https://issues.apache.org/jira/browse/HBASE-15509
Project: HBase
Yufeng Jiang created HBASE-15508:
Summary: Add command for exporting snapshot in hbase command script
Key: HBASE-15508
URL: https://issues.apache.org/jira/browse/HBASE-15508
Project: HBase
Is
Geoffrey Jacoby created HBASE-15507:
---
Summary: Online modification of enabled ReplicationPeerConfig
Key: HBASE-15507
URL: https://issues.apache.org/jira/browse/HBASE-15507
Project: HBase
Is
Vladimir Rodionov created HBASE-15506:
-
Summary: FSDataOutputStream.write() allocates new byte buffer on
each operation
Key: HBASE-15506
URL: https://issues.apache.org/jira/browse/HBASE-15506
Proj
Enis Soztutar created HBASE-15505:
-
Summary: ReplicationPeerConfig should be builder-style
Key: HBASE-15505
URL: https://issues.apache.org/jira/browse/HBASE-15505
Project: HBase
Issue Type: S
bq. we instead focus on a releasable master
+1
One of the hurdles to the above is that some unit tests in master are more
flaky compared to their counterparts in branch-1.
Smoothing out the flaky tests is non-trivial effort.
On Mon, Mar 21, 2016 at 12:52 PM, Gary Helmling wrote:
> >
> > Tho b
On Mon, Mar 21, 2016 at 2:05 PM, Mikhail Antonov
wrote:
> At this point branch-1.3 is very close (if different from at all) to
> branch-1, so that's probably the same discussion.
>
>
Fair enough. Is the previous discussion and documented gates (along with
Andrew's assertion of users) sufficient?
>
> Tho based on this discussion there's a bunch of good features that users
> want that won't fit the criteria for #1 and #2. So allowing a backport of
> the few that can fit into the criteria shouldn't significantly affect
> future release from trunk. This way we can have some progress on some
>
FWIW, I'd like to see the Spark connector get in. We have users who will be
interested in it.
On Mon, Mar 21, 2016 at 12:05 PM, Mikhail Antonov
wrote:
> At this point branch-1.3 is very close (if different from at all) to
> branch-1, so that's probably the same discussion.
>
> -Mikhail
>
> On Mo
At this point branch-1.3 is very close (if different from at all) to
branch-1, so that's probably the same discussion.
-Mikhail
On Mon, Mar 21, 2016 at 11:47 AM, Sean Busbey wrote:
> Is the spark connector thread specifically about 1.3? or branch-1? because
> we already had the branch-1 convers
We should not accumulate feature branches indefinitely as it makes the repo
increasingly unwieldy.
AFAICT, the branch "hbase-6721" is not related to the actual patch(es) that
went in to master for the HBASE-6721 implementation. It will not help with
an accurate backport.
On Mon, Mar 21, 2016 at 1
Elliott Clark created HBASE-15504:
-
Summary: Fix Balancer in 1.3 not moving regions off overloaded
regionserver
Key: HBASE-15504
URL: https://issues.apache.org/jira/browse/HBASE-15504
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-15502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15502.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
Thanks [~misty] Pushed...to master
Is the spark connector thread specifically about 1.3? or branch-1? because
we already had the branch-1 conversation. the specific gates were tracked
in the umbrella jira.
-Sean
On Mon, Mar 21, 2016 at 1:33 PM, Mikhail Antonov
wrote:
> Yeah, we probably should start discussion thread about Spark
Yeah, we probably should start discussion thread about Spark connector.
Anyone wants to start the thread and push it forward?
Regarding date-tiered compactions - since first impl already went in 1.3,
would be good to get any possible improvements in 1.3 as well, as long as
they are stable, IMO.
-
Misty Stanley-Jones created HBASE-15503:
---
Summary: Document REST endpoints for namespaces
Key: HBASE-15503
URL: https://issues.apache.org/jira/browse/HBASE-15503
Project: HBase
Issue Ty
I see, that is indeed undesirable.
Tho based on this discussion there's a bunch of good features that users want
that won't fit the criteria for #1 and #2. So allowing a backport of the few
that can fit into the criteria shouldn't significantly affect future release
from trunk. This way we can
stack created HBASE-15502:
-
Summary: Skeleton unit test to copy/paste
Key: HBASE-15502
URL: https://issues.apache.org/jira/browse/HBASE-15502
Project: HBase
Issue Type: Task
Components: doc
Vladimir Rodionov created HBASE-15501:
-
Summary: MultiAction.add creates unnecessary temporary objects
Key: HBASE-15501
URL: https://issues.apache.org/jira/browse/HBASE-15501
Project: HBase
For HBASE-6721, is there definitive decision not to backport to branch-1 ?
If not, keeping history for its branch is very helpful for backport.
On Mon, Mar 21, 2016 at 11:14 AM, Enis Söztutar wrote:
> What is our policy for deleting feature branches? For example, HBASE-10070,
> HBASE-6721, etc
What is our policy for deleting feature branches? For example, HBASE-10070,
HBASE-6721, etc are all committed, so we do not need the branches. We
should only keep them around if we think that keeping history is important
(which I am not so sure).
Enis
On Mon, Mar 21, 2016 at 11:03 AM, Sean Busbey
You may want to track https://issues.apache.org/jira/browse/HBASE-15339 as
a parent for date-tiered compaction improvements. Current compaction policy
is useful in its own, but handling existing data, bulk loading etc will be
improved with these subtasks. I think the patches can land before the 1.3
I'd like to clean out some of our defunct git branches.
The current list I'm proposing is in JIRA:
https://issues.apache.org/jira/browse/HBASE-15006
If you have a branch you're keeping around and haven't touched in some
time, please take a look and make sure I'm not including it.
Similarly, i
Hadoop's trunk branch hasn't had a release in a very very long time. So it
continues to accumulate changes that aren't in a release while folks drive
their particular desired features back into branch-2.
On Mon, Mar 21, 2016 at 12:01 PM, Francis Liu wrote:
> To summarize so far it seems the conc
To summarize so far it seems the concerns for backporting are:
1. compatibility - api, wire, rolling upgradeabability2. stability -
destabilizing code and deploys for those that don't want the new feature
Is there anything else?
Elliot what happened to hadoop? Is it neither of the two?
Francis
Sean Busbey created HBASE-15500:
---
Summary: Cut HBase 1.2.1 release
Key: HBASE-15500
URL: https://issues.apache.org/jira/browse/HBASE-15500
Project: HBase
Issue Type: Task
Components:
Build status: Successful
If successful, the website and docs have been generated. If failed, skip to the
bottom of this email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site. If you prefer to keep the hbase-site repo around
permanently,
Build status: Successful
If successful, the website and docs have been generated. If failed, skip to the
bottom of this email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site. If you prefer to keep the hbase-site repo around
permanently,
He Liangliang created HBASE-15499:
-
Summary: Add multiple data type support for increment
Key: HBASE-15499
URL: https://issues.apache.org/jira/browse/HBASE-15499
Project: HBase
Issue Type: Ne
He Liangliang created HBASE-15498:
-
Summary: Add conditions in MultiRowMutationService
Key: HBASE-15498
URL: https://issues.apache.org/jira/browse/HBASE-15498
Project: HBase
Issue Type: New F
Jianwei Cui created HBASE-15497:
---
Summary: Incorrect javadoc for atomicity guarantee of Increment
and Append
Key: HBASE-15497
URL: https://issues.apache.org/jira/browse/HBASE-15497
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi resolved HBASE-11684.
---
Resolution: Duplicate
Assignee: (was: Tianying Chang)
Duplicate of HBASE-12988
> H
Guanghao Zhang created HBASE-15496:
--
Summary: Throw RowTooBigException only for user scan/get
Key: HBASE-15496
URL: https://issues.apache.org/jira/browse/HBASE-15496
Project: HBase
Issue Typ
Successful
If successful, the HTML and link-checking report for http://hbase.apache.org is
available at
https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/31/artifact/link_report/index.html.
If failed, see
https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/31/console.
For Spark connector, we should start a separate discussion thread about
backporting to branch-1.
Zhan has a bug fix coming this week which deals with how negative numbers
are handled in comparison.
FYI
On Mon, Mar 21, 2016 at 1:35 AM, Mikhail Antonov
wrote:
> Hi folks,
>
> bringing this topic
Duo Zhang created HBASE-15495:
-
Summary: Connection leak in FanOutOneBlockAsyncDFSOutputHelper
Key: HBASE-15495
URL: https://issues.apache.org/jira/browse/HBASE-15495
Project: HBase
Issue Type: S
Hi folks,
bringing this topic up again. I'm planning to start spinning 1.3 builds and
see if/where they break in a week or two, and (depending on how it does)
start preparing RCs in a month or maybe two. So, let's see where we are.
Big items first. There were long debates around three big items -
46 matches
Mail list logo