To close the loop on this one, I created a label for the candidate list of
patches:
https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.6.1-candidatehttps://issues.apache.org/jira/issues/?jql=labels%20=%202.6.1-candidate,
in order to make progress while the issue is still hot.
The
Srikanth Srungarapu created HBASE-14097:
---
Summary: Log link to client scan troubleshooting section when
scanner exceptions happen.
Key: HBASE-14097
URL: https://issues.apache.org/jira/browse/HBASE-14097
On Wed, Jul 15, 2015 at 5:28 PM, Sean Busbey bus...@cloudera.com wrote:
I think the main problem is that the vector free user didn't have
sufficient rights to license it under CC-BY-3.0 in the first place.
The vector portal license says it's nontransferable, for example.
I wrote vector
Thanks Stack!
--
Sean
On Jul 15, 2015 8:00 PM, Stack st...@duboce.net wrote:
On Wed, Jul 15, 2015 at 5:28 PM, Sean Busbey bus...@cloudera.com wrote:
I think the main problem is that the vector free user didn't have
sufficient rights to license it under CC-BY-3.0 in the first place.
Inline
On Wed, Jul 15, 2015 at 5:22 PM, Vinod Kumar Vavilapalli
vino...@hortonworks.com wrote:
I can understand these (sort of newish) questions from hbase-dev. We
already have a well laid-out release-management process. If people want to
learn more about how it works, please head over to
Sean Busbey created HBASE-14085:
---
Summary: Correct LICENSE and NOTICE files in artifacts
Key: HBASE-14085
URL: https://issues.apache.org/jira/browse/HBASE-14085
Project: HBase
Issue Type: Task
Yu Li created HBASE-14084:
-
Summary: Observe some out-of-date doc on Integration Tests part
Key: HBASE-14084
URL: https://issues.apache.org/jira/browse/HBASE-14084
Project: HBase
Issue Type: Task
On the time topic, let's look at Enis' HLC proposal.
Doc:
https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit#
JIRA: https://issues.apache.org/jira/browse/HBASE-14070
Covers exactly making space for local bits in the timestamps, but to
implement HLC not something
BTW, we can look into hosting if no other volunteer.
Enis
On Wed, Jul 15, 2015 at 11:10 AM, Enis Söztutar enis@gmail.com wrote:
Works for me as well. I'll be back by 15th of Aug.
Enis
On Tue, Jul 14, 2015 at 8:52 PM, Stack st...@duboce.net wrote:
On Tue, Jul 14, 2015 at 8:36 PM, Dima
Andrew Purtell created HBASE-14089:
--
Summary: Remove unused draw of system entropy from
RecoverableZooKeeper
Key: HBASE-14089
URL: https://issues.apache.org/jira/browse/HBASE-14089
Project: HBase
Works for me as well. I'll be back by 15th of Aug.
Enis
On Tue, Jul 14, 2015 at 8:52 PM, Stack st...@duboce.net wrote:
On Tue, Jul 14, 2015 at 8:36 PM, Dima Spivak dspi...@cloudera.com wrote:
Works for me. I'd love to talk about some upstream integration testing
stuff.
Chalk it down!
Hi
What time will it be on August 26th?
@Lars
Ya. I know that you are not generally in favour of this offheaping stuff.
May be if we (from India) can attend this meeting remotely your thoughts
can be discussed and also the current state of this work.
Regards
Ram
On Wed, Jul 15, 2015 at 9:28
Andrew Purtell created HBASE-14091:
--
Summary: Update site documentation with code of conduct and
project policy for transgressions
Key: HBASE-14091
URL: https://issues.apache.org/jira/browse/HBASE-14091
Elliott Clark created HBASE-14092:
-
Summary: Add --no-lock and --no-balancer options to hbck
Key: HBASE-14092
URL: https://issues.apache.org/jira/browse/HBASE-14092
Project: HBase
Issue
Sean Busbey created HBASE-14087:
---
Summary: Add missing ASL headers
Key: HBASE-14087
URL: https://issues.apache.org/jira/browse/HBASE-14087
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-14086:
---
Summary: remove unused bundled dependencies
Key: HBASE-14086
URL: https://issues.apache.org/jira/browse/HBASE-14086
Project: HBase
Issue Type: Sub-task
Why not just have the discussion here? It seems integral to the matter of
having more maintenance releases on those versions.
On Wed, Jul 15, 2015 at 11:39 AM, Karthik Kambatla ka...@cloudera.com
wrote:
I believe there was general consensus to do more maintenance releases, as
witnessed in the
Sean Busbey created HBASE-14093:
---
Summary: deduplicate copies of bootstrap files
Key: HBASE-14093
URL: https://issues.apache.org/jira/browse/HBASE-14093
Project: HBase
Issue Type: Improvement
Yeah, I started a thread while back on this one
(http://markmail.org/message/sbykjn5xgnksh6wg) and had many offline discussions
re 2.6.1.
The biggest problem I found offline was about what bug-fixes are acceptable and
what aren’t for everyone wishing to consume 2.6.1. Given the number of
Is there anyone interested in volunteering to run a 2.6.1 release (Akira?)?
You'd get some help (especially if the bar is set high and only critical
bug fixes are allowed in: i.e. no features, no 'perf' fixes, no jar
updates, and so on).
St.Ack
On Wed, Jul 15, 2015 at 3:07 PM, Chris Douglas
stack created HBASE-14090:
-
Summary: Redo FS layout; let go of tables/regions/stores directory
hierarchy in DFS
Key: HBASE-14090
URL: https://issues.apache.org/jira/browse/HBASE-14090
Project: HBase
Hi Folks!
Working through HBASE-14085 and I was verifying license version/text for
our bundled works in the source distribution.
We have an entry for our logo that points to
http://www.vectorfree.com/jumping-orca as the source and CC-BY 3.0 as the
license.
Looking at the source site, that work
As I proposed in the other thread, how about we adopting the following
model:
x.y.1 releases have all Blocker, Critical, Major bug fixes applied to the
next minor release.
x.y.2 releases have all Blocker, Critical bug fixes applied to the next
minor release.
x.y.3 releases have all Blocker bug
I think the bar for making the maintenance releases should be set
reasonably high, and the main reason is the concern for
stability/regression. Unfortunately there have been cases where a seemingly
innocuous bug fix introduced regressions, small or large. And that defeats
the purpose of a
Why not just include all backwards compatible bug fixes?
Alternatively, why not appoint a Release Manager for the minor release line
and then allow them to arbitrate when there's disagreement about inclusion?
This has worked well in the HBase community.
On Wed, Jul 15, 2015 at 3:49 PM, Karthik
Every new patch potentially brings in new bugs. So, if we want to limit the
kinds of potential bugs introduced in point releases, we might want to
limit what gets in.
Would be nice to make sure a point release is more stable than a previous
point release in that line.
On Wed, Jul 15, 2015 at
If people are concerned about regression then just don't install new
versions, or install a vendor tested stable version. Giving users choices
is a good thing for stability.
On Wed, Jul 15, 2015 at 2:17 PM, Sangjin Lee sjl...@gmail.com wrote:
I think the bar for making the maintenance releases
On Wed, Jul 15, 2015 at 1:20 PM, Sean Busbey bus...@cloudera.com wrote:
Hi Folks!
Working through HBASE-14085 and I was verifying license version/text for
our bundled works in the source distribution.
We have an entry for our logo that points to
http://www.vectorfree.com/jumping-orca as
Sean Busbey created HBASE-14096:
---
Summary: add license information to images
Key: HBASE-14096
URL: https://issues.apache.org/jira/browse/HBASE-14096
Project: HBase
Issue Type: Sub-task
I can understand these (sort of newish) questions from hbase-dev. We already
have a well laid-out release-management process. If people want to learn more
about how it works, please head over to http://hadoop.apache.org/bylaws.html.
In terms of 2.6.1 release management, it wasn’t stuck for lack
On Wed, Jul 15, 2015 at 2:07 PM, Sean Busbey bus...@cloudera.com wrote:
Alternatively, why not appoint a Release Manager for the minor release line
and then allow them to arbitrate when there's disagreement about inclusion?
This has worked well in the HBase community.
Release managers aren't
+1 Chris is right.
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email:
Samir Ahmic created HBASE-14088:
---
Summary: Close Connection in LoadTestTool#applyColumnFamilyOptions
Key: HBASE-14088
URL: https://issues.apache.org/jira/browse/HBASE-14088
Project: HBase
Yuhao Bi created HBASE-14083:
Summary: Fix separator width in Backup Masters of WebUI
Key: HBASE-14083
URL: https://issues.apache.org/jira/browse/HBASE-14083
Project: HBase
Issue Type: Bug
Works for me. I'll be back in the Bay Area the week of August 9th.
We have done a _lot_ of work on backups as well - ours are more complicated as
we wanted fast per-tenant restores, so data is grouped by tenant. Would like
to sync up on that (hopefully some of the folks who wrote most of the
Strong +1 for having a 2.6.1 release. I understand Vinod has been trying to
get that effort going but it's been stalled a little bit. It would be good
to rekindle that effort.
Companies with big hadoop 2.x deployments (including mine) have always
tried to stabilize a 2.x release by
[
https://issues.apache.org/jira/browse/HBASE-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved HBASE-11482.
---
Resolution: Duplicate
Fix Version/s: (was: 2.0.0)
Closing as dupe of HBASE-13992.
I believe there was general consensus to do more maintenance releases, as
witnessed in the other thread.
There have been discussions on what should go into 2.x.1, 2.x.2, etc., but
I don't think we have a clear proposal. It would be nice to put that
together, so committers know where all to commit
38 matches
Mail list logo
