Jonathan Hsieh created HBASE-11168:
--
Summary: [docs] Remove references to RowLocks in post 0.96 docs.
Key: HBASE-11168
URL: https://issues.apache.org/jira/browse/HBASE-11168
Project: HBase
Demai Ni created HBASE-11174:
Summary: show backup/restore progress
Key: HBASE-11174
URL: https://issues.apache.org/jira/browse/HBASE-11174
Project: HBase
Issue Type: New Feature
Affects
[
https://issues.apache.org/jira/browse/HBASE-10661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-10661.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks Devaraj. I've committed this to
Jean-Daniel Cryans created HBASE-11188:
--
Summary: Inconsistent configuration for SchemaMetrics is always
shown
Key: HBASE-11188
URL: https://issues.apache.org/jira/browse/HBASE-11188
Project:
Devaraj Das created HBASE-11149:
---
Summary: Wire encryption is broken
Key: HBASE-11149
URL: https://issues.apache.org/jira/browse/HBASE-11149
Project: HBase
Issue Type: Bug
My 2 ¢... Teeth mean aggressiveness. For me it gives a negative sense. I
tend to prefer something like
http://4.bp.blogspot.com/_HBjr0PcdZW4/TIge5Uok9eI/A8Q/0AdMNtuhRaY/s400/pm006-orca7.png.
JM
2014-05-13 20:57 GMT-04:00 Stack st...@duboce.net:
Any more comments here? I'd like to go
Anoop Sam John created HBASE-11194:
--
Summary: [AccessController] issue with covering permission check
in case of concurrent op on same row
Key: HBASE-11194
URL: https://issues.apache.org/jira/browse/HBASE-11194
On Wed, May 14, 2014 at 6:13 PM, Andrew Purtell apurt...@apache.org wrote:
Because coprocessor APIs are so tightly bound with internals, if we apply
suggested rules like as mentioned on HBASE-11054:
I'd say policy should be no changes to method apis across minor
versions
This will
Guo Ruijing created HBASE-11193:
---
Summary: hbase web UI show wrong Catalog Table Description
Key: HBASE-11193
URL: https://issues.apache.org/jira/browse/HBASE-11193
Project: HBase
Issue Type:
Hi,
(With Apache still lagging on mails, it may be difficult to have a
discussion...)
For 1.0+, I think that registering observer as proposed in 11125 works well.
For 0.98, could we do something like this?
- new coprocessor hooks can be added between minor releases
- existing coprocessors
sunjingtao created HBASE-11192:
--
Summary: HBase ClusterId File Empty Check Loggic
Key: HBASE-11192
URL: https://issues.apache.org/jira/browse/HBASE-11192
Project: HBase
Issue Type: Bug
churro morales created HBASE-11195:
--
Summary: Potentially improve block locality during major
compaction for old regions
Key: HBASE-11195
URL: https://issues.apache.org/jira/browse/HBASE-11195
Li Jiajia created HBASE-11144:
-
Summary: Filter to support scan multiple row key ranges
Key: HBASE-11144
URL: https://issues.apache.org/jira/browse/HBASE-11144
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-11184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-11184.
---
Resolution: Invalid
Resolving as invalid.
This kind of question best belongs on the user or dev lists.
Below is a summary from a follow up conversation to the previous pow-wow
[1] at the post hbasecon 2014 hackthon about an interoperable proposed
encoding scheme for storing typed data in hbase. [2] Raw notes available
here [3].
Thanks,
Jon.
5/14/14
Attendees via phone: Nick Dimiduk, Ryan
Misty Stanley-Jones created HBASE-11190:
---
Summary: Fix easy typos in documentation
Key: HBASE-11190
URL: https://issues.apache.org/jira/browse/HBASE-11190
Project: HBase
Issue Type:
Dima Spivak created HBASE-11196:
---
Summary: Update description of -ROOT- in ref guide
Key: HBASE-11196
URL: https://issues.apache.org/jira/browse/HBASE-11196
Project: HBase
Issue Type: Bug
Until you move the coprocessor out of the RS space and into its own sandbox…
saying security and coprocessor in the same sentence is a joke.
Oh wait… you were serious… :-(
I’d say there’s a significant rethink on coprocessors that’s required.
Anyone running a secure (kerberos) cluster, will
[
https://issues.apache.org/jira/browse/HBASE-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved HBASE-11188.
Resolution: Fixed
Release Note:
Region servers with the default value for
+1 to HBASE-11125. Current incarnation of coprocessors expose too much of
the guts of the implementation.
On Wed, May 14, 2014 at 6:13 PM, Andrew Purtell apurt...@apache.org wrote:
Because coprocessor APIs are so tightly bound with internals, if we apply
suggested rules like as mentioned on
[
https://issues.apache.org/jira/browse/HBASE-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-10513.
---
Resolution: Fixed
Fix Version/s: (was: 0.99.0)
hbase-10070
Nicolas:
Can you give an example of using @since to tag new hooks ?
I searched hadoop and hbase codebase but didn't seem to find such
annotation.
Cheers
On Fri, May 16, 2014 at 1:18 AM, Nicolas Liochon nkey...@gmail.com wrote:
Hi,
(With Apache still lagging on mails, it may be difficult to
[
https://issues.apache.org/jira/browse/HBASE-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved HBASE-10946.
Resolution: Duplicate
I'm fixing this in HBASE-11188.
Matteo Bertozzi created HBASE-11186:
---
Summary: Improve TestExportSnapshot verifications
Key: HBASE-11186
URL: https://issues.apache.org/jira/browse/HBASE-11186
Project: HBase
Issue Type:
Elliott Clark created HBASE-11187:
-
Summary: [89-fb] Limit the number of client threads per
regionserver
Key: HBASE-11187
URL: https://issues.apache.org/jira/browse/HBASE-11187
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-10810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-10810.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Committed this to branch. Thanks Nick and
1) Have default implementations (abstract classes) for every interface from
Coprocessor API.
2) Advise coprocessor users not to implement interface directly but sub
class default impl.
3) Preserve backward compatibility by adding only new hooks/methods
4) DO NOT CHANGE existing API (no method
[
https://issues.apache.org/jira/browse/HBASE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4259.
--
Resolution: Later
Resolving later. No movement in years.
Investigate different memory allocation models for
Gaurav Menghani created HBASE-11138:
---
Summary: [0.89-fb] Check for an empty split key before creating a
table
Key: HBASE-11138
URL: https://issues.apache.org/jira/browse/HBASE-11138
Project: HBase
On 05/15/2014 09:32 AM, James Taylor wrote:
@Ryan Jon - thanks again for pursuing this - I think it'll be a big
improvement.
IMHO, it'd be good to add a Requirements section to the doc. If the
current Phoenix type system meets those requirements, then why not just
go with that?
Good idea.
Ted Yu created HBASE-11189:
--
Summary: Subprocedure should be marked as complete upon failure
Key: HBASE-11189
URL: https://issues.apache.org/jira/browse/HBASE-11189
Project: HBase
Issue Type: Bug
Matteo Bertozzi created HBASE-11185:
---
Summary: Parallelize Snapshot operations
Key: HBASE-11185
URL: https://issues.apache.org/jira/browse/HBASE-11185
Project: HBase
Issue Type: Bug
Andrew Purtell created HBASE-11142:
--
Summary: Taking snapshots can leave sockets on the master stuck in
CLOSE_WAIT state
Key: HBASE-11142
URL: https://issues.apache.org/jira/browse/HBASE-11142
HADOOP-10075 is not integrated yet.
It doesn't have Fix Version(s) either.
For HBase, you can change the version strings in pom.xml to match the ones
from your hadoop build :
jetty.version6.1.26/jetty.version
jetty.jspapi.version6.1.14/jetty.jspapi.version
Cheers
On Fri, May 16, 2014
@Ryan Jon - thanks again for pursuing this - I think it'll be a big
improvement.
IMHO, it'd be good to add a Requirements section to the doc. If the current
Phoenix type system meets those requirements, then why not just go with
that?
I think we need a binary serialization spec that includes
hi, folks,
wondering anyone already began to use Jetty 9 with HBase. We are trying to
use Jetty9 in hadoop, and got the following exceptions when start HBase:
...
java.lang.ClassCastException:
org.eclipse.jetty.servlet.ServletContextHandler incompatible with
org.mortbay.jetty.servlet.Context
I'd like to do an RC for 0.94.20 soon. Looks like it'd be a nice and small
release, only 7 fixes so far. 0.94 is maturing. :)
Anything that should get pulled in?
Thanks.
-- Lars
Doing some local testing I noticed that replication does not work with Hadoop
1.0.x or Hadoop 1.1.x when SSR is enabled.
Was banging my head at it for a while and until I realize what the issues was,
then I also came across this: https://issues.apache.org/jira/browse/HDFS-2757
(which J-D
Ted Yu created HBASE-11147:
--
Summary: Avoid creating List of KeyValue in
FilterBase#filterRowCells(ListCell)
Key: HBASE-11147
URL: https://issues.apache.org/jira/browse/HBASE-11147
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-10990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved HBASE-10990.
Resolution: Duplicate
I'm fixing this in HBASE-11188.
Running CompressionTest
[
https://issues.apache.org/jira/browse/HBASE-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-10357.
---
Resolution: Fixed
Fix Version/s: (was: 0.99.0)
Hadoop Flags: Reviewed
Ok,
[
https://issues.apache.org/jira/browse/HBASE-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari resolved HBASE-11193.
-
Resolution: Duplicate
Like Ted said, duplicate of HBASE-10611. Closing as
Jimmy Xiang created HBASE-11197:
---
Summary: Region could remain unassigned if regionserver crashes
Key: HBASE-11197
URL: https://issues.apache.org/jira/browse/HBASE-11197
Project: HBase
Issue
Ted,
Thanks. I am changing the poms (both top and the one under Hbase- server). Due
to the incompatible btw jetty 6 and 9, infoserver and RESTserver need code
changes too. Well, something to play with this weekend.
Demai on the run
On May 16, 2014, at 4:11 PM, Ted Yu yuzhih...@gmail.com
Thanks Vladimir, I added your points to the discussion on HBASE-11125.
On Sat, May 17, 2014 at 1:59 AM, Vladimir Rodionov
vladrodio...@gmail.comwrote:
1) Have default implementations (abstract classes) for every interface from
Coprocessor API.
2) Advise coprocessor users not to implement
You may want to open a JIRA with your findings.
Cheers
On Fri, May 16, 2014 at 7:49 PM, Demai Ni nid...@gmail.com wrote:
Ted,
Thanks. I am changing the poms (both top and the one under Hbase- server).
Due to the incompatible btw jetty 6 and 9, infoserver and RESTserver need
code changes
Michael,
As you know, we have implemented security features with coprocessors
precisely because they can be interposed on internal actions to make
authoritative decisions in-process. Coprocessors are a way to have
composable internal extensions. They don't have and probably never will
have magic
On Fri, May 16, 2014 at 1:47 AM, Stack st...@duboce.net wrote:
I had just read a user mail on the phoenix list where someone thought that
phoenix had been broken going from 0.98.1 to 0.98.2 (apparently its fine).
Lets write up agreement. We've talked this topic a bunch.
1. No guarantees
48 matches
Mail list logo
