[jira] [Created] (HBASE-13443) Hadoop-qa misreports failed tests when zombies have hung

Mikhail Antonov created HBASE-13443: --- Summary: Hadoop-qa misreports failed tests when zombies have hung Key: HBASE-13443 URL: https://issues.apache.org/jira/browse/HBASE-13443 Project: HBase

Re: remove scanner caching?

Yes also on keeping the default configuration (rowLimit = Integer.MAX_VALUE, bufferSize = 2MB, allowPartialResults = false).

Re: remove scanner caching?

Sounds like you and others are already ahead of me. Thanks for opening HBASE-13441 and your related work. Some responses below: > Nice idea! I agree that the Scan API would be cleaned up by your > suggestions, especially the doc updates. Some comments below: > > > Scan.bufferSize (instead of max

[jira] [Created] (HBASE-13442) Rename scanner caching to a more semantically correct term such as row limit

Jonathan Lawlor created HBASE-13442: --- Summary: Rename scanner caching to a more semantically correct term such as row limit Key: HBASE-13442 URL: https://issues.apache.org/jira/browse/HBASE-13442 Pr

[jira] [Created] (HBASE-13441) Scan API improvements

Jonathan Lawlor created HBASE-13441: --- Summary: Scan API improvements Key: HBASE-13441 URL: https://issues.apache.org/jira/browse/HBASE-13441 Project: HBase Issue Type: Umbrella

Re: remove scanner caching?

On Thu, Apr 9, 2015 at 6:25 AM, Dave Latham wrote: > We definitely wouldn't want to remove it too soon, for compatibility > reasons. > > Adding a "limitRows" notion sounds reasonable, but I'd argue is actually > something different than caching was. If an app is relying on the scanner > to actua

Re: remove scanner caching?

Nice idea! I agree that the Scan API would be cleaned up by your suggestions, especially the doc updates. Some comments below: > Scan.bufferSize (instead of maxResultSize for the target over-the-wire size - though this is still confusing because it's common to go over this size) Ya this setting wi

[jira] [Created] (HBASE-13440) ExportSnapshot doesn't preserve attributes of snapshot's files.

Ivan Orlov created HBASE-13440: -- Summary: ExportSnapshot doesn't preserve attributes of snapshot's files. Key: HBASE-13440 URL: https://issues.apache.org/jira/browse/HBASE-13440 Project: HBase

Re: [VOTE] First release candidate for HBase 1.0.1 (RC0) is available. Please vote by April 8 2015

I'll spin up another RC later today. Let me know if you want to include a specific issue. Sent from my iPhone > On Apr 8, 2015, at 1:38 PM, Enis Söztutar wrote: > > Good find. We do not have compat coverage for shell API it seems. > > Enis > >> On Wed, Apr 8, 2015 at 1:17 PM, Sean Busbey

Re: Monitoring tools for Hbase

Thanks Nick for your suggestions. On Wed, Apr 8, 2015 at 1:34 PM, Nick Dimiduk wrote: > On the OSS side, have a look at Bosun [0]. I haven't used it myself, but it > builds on OpenTSDB, which itself is an HBase application. It looks like the > just-released Ambari 2.0 [1] also has improved metri

[jira] [Resolved] (HBASE-9147) Mechanism to limit system table deletion and creation in non-secure mode

[ https://issues.apache.org/jira/browse/HBASE-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-9147. --- Resolution: Duplicate > Mechanism to limit system table deletion and creation in non-secure mo

Re: remove scanner caching?

We definitely wouldn't want to remove it too soon, for compatibility reasons. Adding a "limitRows" notion sounds reasonable, but I'd argue is actually something different than caching was. If an app is relying on the scanner to actually limit the number of rows returned, the current caching limit

[jira] [Created] (HBASE-13439) Filter to output only selected key-value pair from a row.

Pragalbh Garg created HBASE-13439: - Summary: Filter to output only selected key-value pair from a row. Key: HBASE-13439 URL: https://issues.apache.org/jira/browse/HBASE-13439 Project: HBase I

Re: COMPRESS_TAGS missing from HCD RESERVED_KEYWORDS?

+1. I think it should be added. Regards Ram On Thu, Apr 9, 2015 at 2:56 PM, Lars George wrote: > Hi, > > Looking into this and it seems in HCD, it is missing the COMPRESS_TAGS for > reserved keys and default values. Is this on purpose? If not, I am happy to > create a JIRA, since this looks lik

[jira] [Created] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces

Ashish Singhi created HBASE-13438: - Summary: [branch-1] Backport Basic quota support for namespaces Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issu

COMPRESS_TAGS missing from HCD RESERVED_KEYWORDS?

Hi, Looking into this and it seems in HCD, it is missing the COMPRESS_TAGS for reserved keys and default values. Is this on purpose? If not, I am happy to create a JIRA, since this looks like an oversight. Andy? Cheers, Lars

Re: Removal of deprecated features

I'm probably late to this thread, but just given some comments to HBASE-13395 wanted to follow up here. Semver states that "MAJOR version when you make incompatible API changes". I read it literally as "in 2.0 you can remove anything compared to 1.0". Realistically, that probably means we can at

Re: New 0.98 RC tonight

Actually let's do this tomorrow. I'd like to consider HBASE-13420 for it. I just posted microbrenchmark results to the issue. On Wed, Apr 8, 2015 at 10:19 PM, Andrew Purtell wrote: > Yes, still waiting, but for another hour maybe. > > On Wed, Apr 8, 2015 at 10:04 PM, lars hofhansl wrote: > >> L