[jira] [Assigned] (HBASE-27397) Spark-hbase support for 'startWith' predicate.
[ https://issues.apache.org/jira/browse/HBASE-27397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-27397: Assignee: Richárd Antal > Spark-hbase support for 'startWith' predicate. > -- > > Key: HBASE-27397 > URL: https://issues.apache.org/jira/browse/HBASE-27397 > Project: HBase > Issue Type: New Feature > Components: hbase-connectors >Affects Versions: 3.0.0-alpha-3 >Reporter: Sergey Soldatov >Assignee: Richárd Antal >Priority: Minor > > Currently, spark-hbase connector doesn't support stringStartWith predicate > and completely ignores it. This is a disadvantage compared to the Apache > Phoenix connector and the old SHC (Hortonworks spark-hbase connector). It > would be nice if we also have this functionality in the actual connector. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27397) Spark-hbase support for 'startWith' predicate.
[ https://issues.apache.org/jira/browse/HBASE-27397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-27397: - Labels: usability (was: ) > Spark-hbase support for 'startWith' predicate. > -- > > Key: HBASE-27397 > URL: https://issues.apache.org/jira/browse/HBASE-27397 > Project: HBase > Issue Type: New Feature > Components: hbase-connectors >Affects Versions: 3.0.0-alpha-3 >Reporter: Sergey Soldatov >Assignee: Richárd Antal >Priority: Minor > Labels: usability > > Currently, spark-hbase connector doesn't support stringStartWith predicate > and completely ignores it. This is a disadvantage compared to the Apache > Phoenix connector and the old SHC (Hortonworks spark-hbase connector). It > would be nice if we also have this functionality in the actual connector. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-22972) [JDK11] Support JDK11 LTS in HBase
[ https://issues.apache.org/jira/browse/HBASE-22972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528364#comment-17528364 ] Tamas Penzes commented on HBASE-22972: -- [~zhangduo] afaik building with JDK11 to JDK8 works only until you start using JDK11 features in the code. As soon as you use any bits of JDK11 only code snippets in the application it cannot be built to run on JDK8. I would still support this step, but I'm not even a committer. The best would be to start a [DISCUSS] thread in the dev mailing list. > [JDK11] Support JDK11 LTS in HBase > -- > > Key: HBASE-22972 > URL: https://issues.apache.org/jira/browse/HBASE-22972 > Project: HBase > Issue Type: Umbrella >Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0 >Reporter: Duo Zhang >Priority: Major > Labels: jdk11 > > This is an umbrella issue for tracking all the problems for JDK11 in HBase. > And we also rely on hadoop and zookeeper. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-25684) Dependency manage log4j in hbase-connectors
[ https://issues.apache.org/jira/browse/HBASE-25684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-25684: - Status: Patch Available (was: Open) > Dependency manage log4j in hbase-connectors > --- > > Key: HBASE-25684 > URL: https://issues.apache.org/jira/browse/HBASE-25684 > Project: HBase > Issue Type: Improvement > Components: hbase-connectors >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Minor > > HBase-connectors has many dependencies which might get different versions of > log4j transitively. To ensure we always use the same version we should > "dependency manage" it in the main pom.xml file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25684) Dependency manage log4j in hbase-connectors
Tamas Penzes created HBASE-25684: Summary: Dependency manage log4j in hbase-connectors Key: HBASE-25684 URL: https://issues.apache.org/jira/browse/HBASE-25684 Project: HBase Issue Type: Improvement Components: hbase-connectors Reporter: Tamas Penzes Assignee: Tamas Penzes HBase-connectors has many dependencies which might get different versions of log4j transitively. To ensure we always use the same version we should "dependency manage" it in the main pom.xml file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-20598) Upgrade to JRuby 9.2
[ https://issues.apache.org/jira/browse/HBASE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193483#comment-17193483 ] Tamas Penzes commented on HBASE-20598: -- https://github.com/apache/hbase/pull/2308 > Upgrade to JRuby 9.2 > > > Key: HBASE-20598 > URL: https://issues.apache.org/jira/browse/HBASE-20598 > Project: HBase > Issue Type: Bug > Components: dependencies, shell >Reporter: Josh Elser >Assignee: Jack Bearden >Priority: Major > Fix For: 3.0.0-alpha-1 > > Attachments: HBASE-20598.001.patch, HBASE-20598.002.patch > > > [~mdrob] pointed out that there's a JRuby 9.2 release. We should see if we > can get ourselves onto that from our current 9.1 release line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24753) HA masters based on raft
[ https://issues.apache.org/jira/browse/HBASE-24753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166294#comment-17166294 ] Tamas Penzes commented on HBASE-24753: -- [~zhangduo] Ozone uses Ratis 1.0.0 according to their pom.xml [https://github.com/apache/hadoop-ozone/blob/master/pom.xml#L82] Looks like it's stable enough for them. > HA masters based on raft > > > Key: HBASE-24753 > URL: https://issues.apache.org/jira/browse/HBASE-24753 > Project: HBase > Issue Type: New Feature > Components: master >Reporter: Duo Zhang >Priority: Major > > For better availability, for moving bootstrap information from zookeeper to > our own service so finally we could remove the dependency on zookeeper > completely. > This has been in my mind for a long time, and since the there is a dicussion > in HBASE-11288 about how to storing root table, and also in HBASE-24749, we > want to have better performance on a filesystem can not support list and > rename well, where requires a storage engine at the bottom to store the > storefiles information for meta table, I think it is the time to throw this > idea out. > The basic solution is to build a raft group to store the bootstrap > information, for now it is cluster id(it is on the file system already?) and > the root table. For region servers they will always go to the leader to ask > for the information so they can always see the newest data, and for client, > we enable 'follower read', to reduce the load of the leader(and there are > some solutions to even let 'follower read' to always get the newest data in > raft). > With this solution in place, as long as root table will not be in a format of > region(we could just use rocksdb to store it locally), the cyclic dependency > in HBASE-24749 has also been solved, as we do not need to find a place to > store the storefiles information for root table any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-20598) Upgrade to JRuby 9.2
[ https://issues.apache.org/jira/browse/HBASE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165663#comment-17165663 ] Tamas Penzes commented on HBASE-20598: -- [~jackbearden] do you have a plan to finish this task? > Upgrade to JRuby 9.2 > > > Key: HBASE-20598 > URL: https://issues.apache.org/jira/browse/HBASE-20598 > Project: HBase > Issue Type: Bug > Components: dependencies, shell >Reporter: Josh Elser >Assignee: Jack Bearden >Priority: Major > Fix For: 3.0.0-alpha-1 > > Attachments: HBASE-20598.001.patch, HBASE-20598.002.patch > > > [~mdrob] pointed out that there's a JRuby 9.2 release. We should see if we > can get ourselves onto that from our current 9.1 release line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[ https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reopened HBASE-23896: -- getRandomUUID is static in master branch but not in branch-2.2: See: [https://github.com/apache/hbase/blob/branch-2.2/hbase-common/src/test/java/org/apache/hadoop/hbase/HBaseCommonTestingUtility.java#L158] [https://github.com/apache/hbase/blob/master/hbase-common/src/test/java/org/apache/hadoop/hbase/HBaseCommonTestingUtility.java#L156] Please fix branch 2.2. > Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not > enabled > - > > Key: HBASE-23896 > URL: https://issues.apache.org/jira/browse/HBASE-23896 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0, 2.2.3 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5 > > > When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot > delete the snapshot. This is because the owner of the snapshot cannot be > taken during permission verification. By investigation, found that only after > HBase has enabled security authentication, the owner will be set when doing > snapshot. > SnapshotManager#takeSnapshotInternal > {code:title=SnapshotManager.java|borderStyle=solid} > RpcServer.getRequestUser().ifPresent(user -> { > if (User.isHBaseSecurityEnabled(master.getConfiguration())) { > builder.setOwner(user.getShortName()); > } > }); > {code} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24148) Upgrade Thrift to 0.13.0: 0.12.0 has outstanding CVEs.
[ https://issues.apache.org/jira/browse/HBASE-24148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084376#comment-17084376 ] Tamas Penzes commented on HBASE-24148: -- Thanks [~stack], sorry I was busy on other tasks recently, couldn't go forward with this one. > Upgrade Thrift to 0.13.0: 0.12.0 has outstanding CVEs. > -- > > Key: HBASE-24148 > URL: https://issues.apache.org/jira/browse/HBASE-24148 > Project: HBase > Issue Type: Improvement > Components: Thrift >Affects Versions: 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > In Apache Thrift all versions up to and including 0.12.0, a server or client > may run into an endless loop when feed with specific input data. Because the > issue had already been partially fixed in version 0.11.0, depending on the > installed version it affects only certain language bindings. > To be on the safe side, we could update to 0.13.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24149) Bump netty version to 4.1.48.Final
[ https://issues.apache.org/jira/browse/HBASE-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-24149: - Status: Patch Available (was: Open) > Bump netty version to 4.1.48.Final > -- > > Key: HBASE-24149 > URL: https://issues.apache.org/jira/browse/HBASE-24149 > Project: HBase > Issue Type: Improvement > Components: thirdparty >Affects Versions: thirdparty-3.2.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > There is a new netty version to fix some bugs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24149) Bump netty version to 4.1.48.Final
Tamas Penzes created HBASE-24149: Summary: Bump netty version to 4.1.48.Final Key: HBASE-24149 URL: https://issues.apache.org/jira/browse/HBASE-24149 Project: HBase Issue Type: Improvement Components: thirdparty Affects Versions: thirdparty-3.2.0 Reporter: Tamas Penzes Assignee: Tamas Penzes There is a new netty version to fix some bugs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24148) Upgrade Thrift to 0.13.0
[ https://issues.apache.org/jira/browse/HBASE-24148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-24148: - Status: Patch Available (was: Open) > Upgrade Thrift to 0.13.0 > > > Key: HBASE-24148 > URL: https://issues.apache.org/jira/browse/HBASE-24148 > Project: HBase > Issue Type: Improvement > Components: Thrift >Affects Versions: 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > In Apache Thrift all versions up to and including 0.12.0, a server or client > may run into an endless loop when feed with specific input data. Because the > issue had already been partially fixed in version 0.11.0, depending on the > installed version it affects only certain language bindings. > To be on the safe side, we could update to 0.13.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24148) Upgrade Thrift to 0.13.0
Tamas Penzes created HBASE-24148: Summary: Upgrade Thrift to 0.13.0 Key: HBASE-24148 URL: https://issues.apache.org/jira/browse/HBASE-24148 Project: HBase Issue Type: Improvement Components: Thrift Affects Versions: 3.0.0 Reporter: Tamas Penzes Assignee: Tamas Penzes In Apache Thrift all versions up to and including 0.12.0, a server or client may run into an endless loop when feed with specific input data. Because the issue had already been partially fixed in version 0.11.0, depending on the installed version it affects only certain language bindings. To be on the safe side, we could update to 0.13.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-24124) hbase-filesystem to use guava from hbase-thirdparty
[ https://issues.apache.org/jira/browse/HBASE-24124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-24124: Assignee: Wei-Chiu Chuang (was: Tamas Penzes) > hbase-filesystem to use guava from hbase-thirdparty > --- > > Key: HBASE-24124 > URL: https://issues.apache.org/jira/browse/HBASE-24124 > Project: HBase > Issue Type: Task > Components: Filesystem Integration >Affects Versions: 1.0.0-alpha1 >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Fix For: 1.0.0-alpha2 > > > hbase-filesystem repo is on guava23.0: > {noformat} > $ grep -r "guava" . > ./pom.xml:23.0 > ./hbase-oss/pom.xml: com.google.guava > ./hbase-oss/pom.xml: guava > ./hbase-oss/pom.xml: ${guava.version} > ./hbase-oss/pom.xml:
[jira] [Assigned] (HBASE-24124) hbase-filesystem to use guava from hbase-thirdparty
[ https://issues.apache.org/jira/browse/HBASE-24124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-24124: Assignee: Tamas Penzes > hbase-filesystem to use guava from hbase-thirdparty > --- > > Key: HBASE-24124 > URL: https://issues.apache.org/jira/browse/HBASE-24124 > Project: HBase > Issue Type: Task > Components: Filesystem Integration >Affects Versions: 1.0.0-alpha1 >Reporter: Wei-Chiu Chuang >Assignee: Tamas Penzes >Priority: Major > Fix For: 1.0.0-alpha2 > > > hbase-filesystem repo is on guava23.0: > {noformat} > $ grep -r "guava" . > ./pom.xml:23.0 > ./hbase-oss/pom.xml: com.google.guava > ./hbase-oss/pom.xml: guava > ./hbase-oss/pom.xml: ${guava.version} > ./hbase-oss/pom.xml:
[jira] [Updated] (HBASE-23790) Bump netty version to 4.1.45.Final in hbase-thirdparty
[ https://issues.apache.org/jira/browse/HBASE-23790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-23790: - Affects Version/s: (was: thirdparty-3.0.0) hbase-thirdparty-3.2.0 > Bump netty version to 4.1.45.Final in hbase-thirdparty > -- > > Key: HBASE-23790 > URL: https://issues.apache.org/jira/browse/HBASE-23790 > Project: HBase > Issue Type: Improvement > Components: hbase-thirdparty >Affects Versions: hbase-thirdparty-3.2.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23790) Bump netty version to 4.1.45.Final in hbase-thirdparty
[ https://issues.apache.org/jira/browse/HBASE-23790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-23790: - Affects Version/s: thirdparty-3.0.0 > Bump netty version to 4.1.45.Final in hbase-thirdparty > -- > > Key: HBASE-23790 > URL: https://issues.apache.org/jira/browse/HBASE-23790 > Project: HBase > Issue Type: Improvement > Components: hbase-thirdparty >Affects Versions: thirdparty-3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23790) Bump netty version to 4.1.45.Final in hbase-thirdparty
[ https://issues.apache.org/jira/browse/HBASE-23790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-23790: - Summary: Bump netty version to 4.1.45.Final in hbase-thirdparty (was: Bump netty version to 4.1.45.Final) > Bump netty version to 4.1.45.Final in hbase-thirdparty > -- > > Key: HBASE-23790 > URL: https://issues.apache.org/jira/browse/HBASE-23790 > Project: HBase > Issue Type: Improvement > Components: hbase-thirdparty >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-23790) Bump netty version to 4.1.45.Final
[ https://issues.apache.org/jira/browse/HBASE-23790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-23790 started by Tamas Penzes. > Bump netty version to 4.1.45.Final > -- > > Key: HBASE-23790 > URL: https://issues.apache.org/jira/browse/HBASE-23790 > Project: HBase > Issue Type: Improvement > Components: hbase-thirdparty >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-23790) Bump netty version to 4.1.45.Final
[ https://issues.apache.org/jira/browse/HBASE-23790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-23790: Assignee: Tamas Penzes > Bump netty version to 4.1.45.Final > -- > > Key: HBASE-23790 > URL: https://issues.apache.org/jira/browse/HBASE-23790 > Project: HBase > Issue Type: Improvement > Components: hbase-thirdparty >Reporter: Tamas Penzes >Assignee: Tamas Penzes >Priority: Major > > We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23790) Bump netty version to 4.1.45.Final
Tamas Penzes created HBASE-23790: Summary: Bump netty version to 4.1.45.Final Key: HBASE-23790 URL: https://issues.apache.org/jira/browse/HBASE-23790 Project: HBase Issue Type: Improvement Components: hbase-thirdparty Reporter: Tamas Penzes We do have a new netty version 4.1.45.Final which we could update to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-23305) Master based registry implementation
[ https://issues.apache.org/jira/browse/HBASE-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017795#comment-17017795 ] Tamas Penzes commented on HBASE-23305: -- [~bharathv] this change looks really cool, may I ask you if you plan to land it on version 2.2.x or only on 2.3? > Master based registry implementation > > > Key: HBASE-23305 > URL: https://issues.apache.org/jira/browse/HBASE-23305 > Project: HBase > Issue Type: Sub-task > Components: master >Reporter: Bharath Vissapragada >Assignee: Bharath Vissapragada >Priority: Major > Fix For: HBASE-18095 > > > Once we have all the RPCs in place (via HBASE-23304), implement a pluggable > master based AsyncRegistry (like ZKAsyncRegistry) which clients can use to > directly connect to master and fetch all the meta information needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23032) Upgrade to Curator 4.2.0
[ https://issues.apache.org/jira/browse/HBASE-23032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-23032: - Description: Curator 4.0 is quite old, it's time to jump to 4.2.0. We should do it in hbase-connectors and hbase-filesystem too. [http://curator.apache.org/zk-compatibility.html] was: Curator 4.0 is quite old, it's time to jump to 4.2.0. We should do it in hbase-connectors and hbase-filesystem too. > Upgrade to Curator 4.2.0 > > > Key: HBASE-23032 > URL: https://issues.apache.org/jira/browse/HBASE-23032 > Project: HBase > Issue Type: Improvement >Reporter: Tamas Penzes >Priority: Major > > Curator 4.0 is quite old, it's time to jump to 4.2.0. > We should do it in hbase-connectors and hbase-filesystem too. > [http://curator.apache.org/zk-compatibility.html] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (HBASE-23032) Upgrade to Curator 4.2.0
[ https://issues.apache.org/jira/browse/HBASE-23032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-23032: - Description: Curator 4.0 is quite old, it's time to jump to 4.2.0. We should do it in hbase-connectors and hbase-filesystem too. was:Curator 4.0 is quite old, it's time to jump to 4.2.0. > Upgrade to Curator 4.2.0 > > > Key: HBASE-23032 > URL: https://issues.apache.org/jira/browse/HBASE-23032 > Project: HBase > Issue Type: Improvement >Reporter: Tamas Penzes >Priority: Major > > Curator 4.0 is quite old, it's time to jump to 4.2.0. > We should do it in hbase-connectors and hbase-filesystem too. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (HBASE-23032) Upgrade to Curator 4.2.0
Tamas Penzes created HBASE-23032: Summary: Upgrade to Curator 4.2.0 Key: HBASE-23032 URL: https://issues.apache.org/jira/browse/HBASE-23032 Project: HBase Issue Type: Improvement Reporter: Tamas Penzes Curator 4.0 is quite old, it's time to jump to 4.2.0. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-15751) Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use zookeeper 3.5
[ https://issues.apache.org/jira/browse/HBASE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893849#comment-16893849 ] Tamas Penzes commented on HBASE-15751: -- ZooKeeper 3.5.5 GA is a stable release. Should we re-animate this ticket? > Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use > zookeeper 3.5 > > > Key: HBASE-15751 > URL: https://issues.apache.org/jira/browse/HBASE-15751 > Project: HBase > Issue Type: Improvement > Components: dependencies, Zookeeper >Reporter: Yufeng Jiang >Assignee: Yufeng Jiang >Priority: Critical > Attachments: HBASE-15751.patch > > > From zookeeper 3.5 and onwards, runFromConfig(QuorumPeerConfig config) method > throws AdminServerException. > HBase uses runFromConfig in HQuorumPeer.java and hence needs to throw this > exception as well. > I've created a patch to make HBase compatible with zookeeper-3.5.1-alpha. > However, since zookeeper 3.5+ does not have a stable version yet, I don't > think we should commit this patch. Instead, I suggest using this JIRA to > track this issue. Once zookeeper releases stable version of 3.5+, I could > create another patch to bump the zookeeper version in HBase trunk. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22053) zookeeper URL links in documentation are failing with 404
[ https://issues.apache.org/jira/browse/HBASE-22053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803727#comment-16803727 ] Tamas Penzes commented on HBASE-22053: -- Since we use ZooKeeper version 3.4.10 within HBase it would have been better to point to that version in the documentation too. [https://github.com/apache/hbase/blob/master/pom.xml#L1547] [https://zookeeper.apache.org/doc/r3.4.10/index.html] > zookeeper URL links in documentation are failing with 404 > - > > Key: HBASE-22053 > URL: https://issues.apache.org/jira/browse/HBASE-22053 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Subrat Mishra >Assignee: Subrat Mishra >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.1.5, 2.2.1 > > Attachments: HBASE-22053.master.001.patch, > HBASE-22053.master.002.patch > > > zookeeper URL changed from hadoop.apache.org to zookeeper.apache.org > E.g: Below URL failing with 404 > http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions > should be changed to: > https://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_zkSessions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20994) Clean up manual array to collection copy, trivial
[ https://issues.apache.org/jira/browse/HBASE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568058#comment-16568058 ] Tamas Penzes edited comment on HBASE-20994 at 8/3/18 10:27 AM: --- [~jleach4] could you please fix the checkstyle issues? Otherwise it looks okay for me. Please always assign the ticket to yourself when you start working on it. Thanks. was (Author: tamaas): [~jleach4] could you please fix the checkstyle issues? Otherwise it looks okay for me. > Clean up manual array to collection copy, trivial > - > > Key: HBASE-20994 > URL: https://issues.apache.org/jira/browse/HBASE-20994 > Project: HBase > Issue Type: Bug >Reporter: John Leach >Assignee: John Leach >Priority: Trivial > Attachments: HBASE-20994.patch > > > Remove for loops adding to collections. (Style) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-20994) Clean up manual array to collection copy, trivial
[ https://issues.apache.org/jira/browse/HBASE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-20994: Assignee: John Leach > Clean up manual array to collection copy, trivial > - > > Key: HBASE-20994 > URL: https://issues.apache.org/jira/browse/HBASE-20994 > Project: HBase > Issue Type: Bug >Reporter: John Leach >Assignee: John Leach >Priority: Trivial > Attachments: HBASE-20994.patch > > > Remove for loops adding to collections. (Style) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20995) Clean Up Manual Array Copies, trivial
[ https://issues.apache.org/jira/browse/HBASE-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568062#comment-16568062 ] Tamas Penzes commented on HBASE-20995: -- Looks okay for me. Please always assign the ticket to yourself when you start working on it. Thanks. > Clean Up Manual Array Copies, trivial > - > > Key: HBASE-20995 > URL: https://issues.apache.org/jira/browse/HBASE-20995 > Project: HBase > Issue Type: Improvement >Reporter: John Leach >Assignee: John Leach >Priority: Trivial > Attachments: HBASE-20995.patch > > > Clean up manual array copies in code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-20995) Clean Up Manual Array Copies, trivial
[ https://issues.apache.org/jira/browse/HBASE-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-20995: Assignee: John Leach > Clean Up Manual Array Copies, trivial > - > > Key: HBASE-20995 > URL: https://issues.apache.org/jira/browse/HBASE-20995 > Project: HBase > Issue Type: Improvement >Reporter: John Leach >Assignee: John Leach >Priority: Trivial > Attachments: HBASE-20995.patch > > > Clean up manual array copies in code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20994) Clean up manual array to collection copy, trivial
[ https://issues.apache.org/jira/browse/HBASE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568058#comment-16568058 ] Tamas Penzes commented on HBASE-20994: -- [~jleach4] could you please fix the checkstyle issues? Otherwise it looks okay for me. > Clean up manual array to collection copy, trivial > - > > Key: HBASE-20994 > URL: https://issues.apache.org/jira/browse/HBASE-20994 > Project: HBase > Issue Type: Bug >Reporter: John Leach >Priority: Trivial > Attachments: HBASE-20994.patch > > > Remove for loops adding to collections. (Style) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch, HBASE-18601.master.012.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch, HBASE-18601.master.012.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221275#comment-16221275 ] Tamas Penzes commented on HBASE-18601: -- submitted version 12 to test, still has issues on my machine > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch, HBASE-18601.master.012.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Comment: was deleted (was: submitted version 12 to test, still has issues on my machine) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch, HBASE-13346.master.011.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221267#comment-16221267 ] Tamas Penzes commented on HBASE-13346: -- submitted version 12 to test, still has issues on my machine > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch, HBASE-13346.master.011.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch, HBASE-13346.master.011.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch, HBASE-13346.master.011.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.012.patch > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch, HBASE-18601.master.012.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219458#comment-16219458 ] Tamas Penzes commented on HBASE-13346: -- hi [~openinx], fixed. Also other places where I've added IOException without a real cause. Thanks for pointing it out. > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.011.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch, > HBASE-13346.master.011.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218785#comment-16218785 ] Tamas Penzes commented on HBASE-14093: -- not really, we use maven-dependency-plugin 3.0.1 in branch-2 as well, should work > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, direct_extract.log, indirect_extract.log, > patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218785#comment-16218785 ] Tamas Penzes edited comment on HBASE-14093 at 10/25/17 2:41 PM: not really, we use maven-dependency-plugin 3.0.1 in branch-2 as well, should work, I'll try to find out was (Author: tamaas): not really, we use maven-dependency-plugin 3.0.1 in branch-2 as well, should work > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, direct_extract.log, indirect_extract.log, > patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218778#comment-16218778 ] Tamas Penzes commented on HBASE-13346: -- rebased, fix where it was needed > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.010.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch, HBASE-13346.master.010.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218595#comment-16218595 ] Tamas Penzes commented on HBASE-13346: -- HBASE-18410 merged, I start rebasing this now. > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16217511#comment-16217511 ] Tamas Penzes edited comment on HBASE-13346 at 10/24/17 7:26 PM: Rebased and FilterWrapper moved. New patch created, added to review board. was (Author: tamaas): Rebased and FilterWrapper moved. > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16217511#comment-16217511 ] Tamas Penzes commented on HBASE-13346: -- Rebased and FilterWrapper moved. > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.009.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch, > HBASE-13346.master.009.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16217387#comment-16217387 ] Tamas Penzes commented on HBASE-13346: -- As I see, I can move the FilterWrapper tomorrow. Which package do you propose? > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215819#comment-16215819 ] Tamas Penzes commented on HBASE-18601: -- Hi [~stack], [~mdrob] Sorry guys, I've just rebased. Patch version 11 uploaded. I've set ticket to "submit patch", so it should run soon. > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.011.patch > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, > HBASE-18601.master.011.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209573#comment-16209573 ] Tamas Penzes edited comment on HBASE-14093 at 10/18/17 6:28 PM: Hi [~mdrob], Looks like I have misunderstand you. I've thought you want to move the download to hbase-assembly, which I would not do, but you only want to spare the move task from the download/extract/move. I've checked it, and I would also not work. If we extract the webjars directly we get a different directory structure, which includes bootstrap/jquery version number and additional files too. Please check direct_extract.log and indirect_extract.log attached to the ticket. This is why I have to extract it to a tmp dir and only copy the relevant part to the final place. Thanks, Tamaas was (Author: tamaas): Hi [~mdrob], Looks like I have misunderstand you. I've thought you want to move the download to hbase-assembly, which I would not do, but you only want to spare the move task from the download/extract/move. I've checked it, and I would also not work. If we extract the webjars directly we get a different directory structure, which includes bootstrap/jquery version number. Please check direct_extract.log and indirect_extract.log attached to the ticket. This is why I have to extract it to a tmp dir and only copy the relevant part to the final place. Thanks, Tamaas > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, direct_extract.log, indirect_extract.log, > patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209573#comment-16209573 ] Tamas Penzes edited comment on HBASE-14093 at 10/18/17 6:27 PM: Hi [~mdrob], Looks like I have misunderstand you. I've thought you want to move the download to hbase-assembly, which I would not do, but you only want to spare the move task from the download/extract/move. I've checked it, and I would also not work. If we extract the webjars directly we get a different directory structure, which includes bootstrap/jquery version number. Please check direct_extract.log and indirect_extract.log attached to the ticket. This is why I have to extract it to a tmp dir and only copy the relevant part to the final place. Thanks, Tamaas was (Author: tamaas): Hi [~mdrob], Looks like I have misunderstand you. I've thought you want to move the download to hbase-assembly, which I would not do, but you only want to spare the move task from the download/extract/move. I'll do a fix soon. Regards, Tamaas > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, direct_extract.log, indirect_extract.log, > patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-14093: - Attachment: indirect_extract.log direct_extract.log > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, direct_extract.log, indirect_extract.log, > patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209573#comment-16209573 ] Tamas Penzes commented on HBASE-14093: -- Hi [~mdrob], Looks like I have misunderstand you. I've thought you want to move the download to hbase-assembly, which I would not do, but you only want to spare the move task from the download/extract/move. I'll do a fix soon. Regards, Tamaas > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208604#comment-16208604 ] Tamas Penzes edited comment on HBASE-18601 at 10/17/17 11:47 PM: - Hi, Does anybody have some idea why we get this: {code} [INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ hbase-rest --- [INFO] Compiling 70 source files to /testptch/hbase/hbase-rest/target/classes [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Some input files use or override a deprecated API. [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Recompile with -Xlint:deprecation for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[23,31] cannot find symbol symbol: class CompatibilitySingletonFactory location: package org.apache.hadoop.hbase [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[25,36] cannot find symbol symbol: class MetricsRESTSource location: package org.apache.hadoop.hbase.rest [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[30,10] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[34,11] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,57] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,15] cannot find symbol symbol: variable CompatibilitySingletonFactory location: class org.apache.hadoop.hbase.rest.MetricsREST [INFO] 6 errors {code} It builds/runs for me locally, if we didn't have these resources, it would not build for me either. Thanks. was (Author: tamaas): Hi, Does anybody have some idea why we get this: {code} [INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ hbase-rest --- [INFO] Compiling 70 source files to /testptch/hbase/hbase-rest/target/classes [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Some input files use or override a deprecated API. [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Recompile with -Xlint:deprecation for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[23,31] cannot find symbol symbol: class CompatibilitySingletonFactory location: package org.apache.hadoop.hbase [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[25,36] cannot find symbol symbol: class MetricsRESTSource location: package org.apache.hadoop.hbase.rest [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[30,10] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[34,11] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,57] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,15] cannot find symbol symbol: variable CompatibilitySingletonFactory location: class org.apache.hadoop.hbase.rest.MetricsREST [INFO] 6 errors {code} It builds/runs for me locally, if we didn't have these resources, it would not build for me either. > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments:
[jira] [Commented] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208604#comment-16208604 ] Tamas Penzes commented on HBASE-18601: -- Hi, Does anybody have some idea why we get this: {code} [INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ hbase-rest --- [INFO] Compiling 70 source files to /testptch/hbase/hbase-rest/target/classes [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Some input files use or override a deprecated API. [INFO] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java: Recompile with -Xlint:deprecation for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[23,31] cannot find symbol symbol: class CompatibilitySingletonFactory location: package org.apache.hadoop.hbase [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[25,36] cannot find symbol symbol: class MetricsRESTSource location: package org.apache.hadoop.hbase.rest [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[30,10] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[34,11] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,57] cannot find symbol symbol: class MetricsRESTSource location: class org.apache.hadoop.hbase.rest.MetricsREST [ERROR] /testptch/hbase/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MetricsREST.java:[37,15] cannot find symbol symbol: variable CompatibilitySingletonFactory location: class org.apache.hadoop.hbase.rest.MetricsREST [INFO] 6 errors {code} It builds/runs for me locally, if we didn't have these resources, it would not build for me either. > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch, HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.008.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch, HBASE-13346.master.008.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204326#comment-16204326 ] Tamas Penzes commented on HBASE-14093: -- [~mdrob] tab.js fixed maven hack removed (I've checked it, it's not needed any more) bootstrap updated to latest I haven't moved the logic of downloading and extracting bootstrap and jquery to hbase-assembly, because this way we have a simple, easy to test web module, which doesn't depend on anything. The files fit into this project, and hbase-assembly can stay consistent. Opinion? > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-14093: - Status: Patch Available (was: Open) > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-14093: - Status: Open (was: Patch Available) > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-14093) deduplicate copies of bootstrap files
[ https://issues.apache.org/jira/browse/HBASE-14093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-14093: - Attachment: HBASE-14093.master.004.patch > deduplicate copies of bootstrap files > - > > Key: HBASE-14093 > URL: https://issues.apache.org/jira/browse/HBASE-14093 > Project: HBase > Issue Type: Improvement > Components: build >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-14093.master.001.patch, > HBASE-14093.master.002.patch, HBASE-14093.master.002.patch, > HBASE-14093.master.003.patch, HBASE-14093.master.003.patch, > HBASE-14093.master.004.patch, patch-shadedjars.txt > > > right now we have a couple of different copies of the bootstrap js and css > files. It'll be easier to maintain them later if we can centralize. > Move them to a common location and use maven to populate them as needed in > various component build directories. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.007.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch, > HBASE-13346.master.007.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: In Progress) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.006.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch, HBASE-13346.master.006.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202324#comment-16202324 ] Tamas Penzes edited comment on HBASE-18601 at 10/12/17 5:31 PM: Yeah, most of them. I've found one more NPE, but otherwise my test results look good. Some tests were failing because of AssertionErrors, but I don't think it is connected to my changes. Hard to prove... New patch uploaded. was (Author: tamaas): Yeah, most of them. I've found one more NPE, but otherwise my test results look good. Some tests were failing because of AssertionErrors, but I don't think it is connected to my changes. Hard to prove... > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202324#comment-16202324 ] Tamas Penzes commented on HBASE-18601: -- Yeah, most of them. I've found one more NPE, but otherwise my test results look good. Some tests were failing because of AssertionErrors, but I don't think it is connected to my changes. Hard to prove... > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.010.patch > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, > HBASE-18601.master.010.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18797) Deprecate Filter#filterKeyValue and add Filter#filterCell
[ https://issues.apache.org/jira/browse/HBASE-18797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199080#comment-16199080 ] Tamas Penzes commented on HBASE-18797: -- Since, the patch is added to the parent, this one should be closed > Deprecate Filter#filterKeyValue and add Filter#filterCell > - > > Key: HBASE-18797 > URL: https://issues.apache.org/jira/browse/HBASE-18797 > Project: HBase > Issue Type: Sub-task > Components: API, Filters >Reporter: Abhishek Singh Chouhan >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > > Part of filter package cleanup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18797) Deprecate Filter#filterKeyValue and add Filter#filterCell
[ https://issues.apache.org/jira/browse/HBASE-18797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes resolved HBASE-18797. -- Resolution: Duplicate Release Note: Since, the patch is added to the parent, this one should be closed > Deprecate Filter#filterKeyValue and add Filter#filterCell > - > > Key: HBASE-18797 > URL: https://issues.apache.org/jira/browse/HBASE-18797 > Project: HBase > Issue Type: Sub-task > Components: API, Filters >Reporter: Abhishek Singh Chouhan >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > > Part of filter package cleanup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.009.patch retry > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch, HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.009.patch > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, > HBASE-18601.master.009.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Patch Available (was: Open) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Status: Open (was: Patch Available) > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194964#comment-16194964 ] Tamas Penzes commented on HBASE-13346: -- Thanks guys for the help, fixed the issue. Now it looks like it is finished. And I've forgotten to push it to rb again, but created the rb request manually: https://reviews.apache.org/r/62813/ > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13346) Clean up Filter package for post 1.0 s/KeyValue/Cell/g
[ https://issues.apache.org/jira/browse/HBASE-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-13346: - Attachment: HBASE-13346.master.005.patch > Clean up Filter package for post 1.0 s/KeyValue/Cell/g > -- > > Key: HBASE-13346 > URL: https://issues.apache.org/jira/browse/HBASE-13346 > Project: HBase > Issue Type: Bug > Components: API, Filters >Affects Versions: 2.0.0 >Reporter: Lars George >Assignee: Tamas Penzes >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-13346.master.001.patch, > HBASE-13346.master.002.patch, HBASE-13346.master.003.patch, > HBASE-13346.master.003.patch, HBASE-13346.master.004.patch, > HBASE-13346.master.005.patch > > > Since we have a bit of a messy Filter API with KeyValue vs Cell reference > mixed up all over the place, I recommend cleaning this up once and for all. > There should be no {{KeyValue}} (or {{kv}}, {{kvs}} etc.) in any method or > parameter name. > This includes deprecating and renaming filters too, for example > {{FirstKeyOnlyFilter}}, which really should be named {{FirstKeyValueFilter}} > as it does _not_ just return the key, but the entire cell. It should be > deprecated and renamed to {{FirstCellFilter}} (or {{FirstColumnFilter}} if > you prefer). > In general we should clarify and settle on {{KeyValue}} vs {{Cell}} vs > {{Column}} in our naming. The latter two are the only ones going forward with > the public API, and are used synonymous. We should carefully check which is > better suited (is it really a specific cell, or the newest cell, aka the > newest column value) and settle on a naming schema. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Patch Available (was: Open) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Status: Open (was: Patch Available) > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18601) Update Htrace to 4.2
[ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HBASE-18601: - Attachment: HBASE-18601.master.008.patch > Update Htrace to 4.2 > > > Key: HBASE-18601 > URL: https://issues.apache.org/jira/browse/HBASE-18601 > Project: HBase > Issue Type: Task >Affects Versions: 2.0.0, 3.0.0 >Reporter: Tamas Penzes >Assignee: Tamas Penzes > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18601.master.001.patch, > HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, > HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, > HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, > HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, > HBASE-18601.master.007.patch, HBASE-18601.master.008.patch > > > HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, > the upgrade to 4.x is not trivial and would take time. It might not worth to > keep it in this state, so would be better to remove it. > Of course it doesn't mean tracing would be useless, just that in this form > the use of HTrace 3.2 might not add any value to the project and fixing it > would be far too much effort. > - > Based on the decision of the community we keep htrace now and update version -- This message was sent by Atlassian JIRA (v6.4.14#64029)