[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814435#comment-16814435 ] Balazs Meszaros commented on HBASE-20934: - Hi [~stack], can we close this issue? > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.3.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571854#comment-16571854 ] stack commented on HBASE-20934: --- Thank you [~elserj]. Make a new issue filed against hbase-connectors? I can take your suggestions to the hbase-operator-tools repo too. Thanks > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.2.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[
https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571723#comment-16571723
]
Josh Elser commented on HBASE-20934:
{quote} * The poms could do w/ a review. Hacked them over from
hbase-thirdparty.{quote}
I can glance at them [~stack]. How would you like feedback?
> Create an hbase-connectors repository; commit new kafka connect here
>
>
> Key: HBASE-20934
> URL: https://issues.apache.org/jira/browse/HBASE-20934
> Project: HBase
> Issue Type: Bug
> Components: kafka, mapreduce, REST, spark, Thrift
>Affects Versions: 2.1.0
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.2.0
>
>
> Create a new repository at hbase.apache.org and commit the new kafka proxy
> here (HBASE-15320). Make sure it plays nicely with hbase core making use of
> public-apis only (It does as best as I can see... but saying this anyways).
> Once the kafka proxy is working, as subissue, move REST and thrift over...
> SPARK too.
> This might be better done for an hbase3 target. I filed it against hbase2.2
> for now.
> See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320",
> https://s.apache.org/RQcC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567575#comment-16567575 ] stack commented on HBASE-20934: --- I pushed the v19 patch from HBASE-15320 HBase connector for Kafka Connect to this new repository. TODO as subtasks: * Figure how to do start scripts. E.g. we need to start up the kafka proxy. It wants some hbase jars and others on the CLASSPATH. In the v19 patch, it just added a keyword => proxy server class name which has a main. Needs to put in place the conf dir too. * Can any of the connectors make-do with the shaded client? * Need to do an assembly. * Move over REST and thrift. * The poms could do w/ a review. Hacked them over from hbase-thirdparty. > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.2.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564527#comment-16564527 ] stack commented on HBASE-20934: --- Or via here: https://github.com/apache/hbase-connectors > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.2.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564505#comment-16564505 ] stack commented on HBASE-20934: --- Created. I made (INFRA-16847) Please create two new repositories for hbase project but infra sent me to https://gitbox.apache.org/ where I did the damage. Our new repo is here, rather than at git.apache.org; i.e. it is not mirrored from svn. https://gitbox.apache.org/repos/asf?p=hbase-connectors.git;a=summary > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, mapreduce, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.2.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20934) Create an hbase-connectors repository; commit new kafka connect here
[ https://issues.apache.org/jira/browse/HBASE-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555680#comment-16555680 ] Sean Busbey commented on HBASE-20934: - mapreduce stuff too? > Create an hbase-connectors repository; commit new kafka connect here > > > Key: HBASE-20934 > URL: https://issues.apache.org/jira/browse/HBASE-20934 > Project: HBase > Issue Type: Bug > Components: kafka, REST, spark, Thrift >Affects Versions: 2.1.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.2.0 > > > Create a new repository at hbase.apache.org and commit the new kafka proxy > here (HBASE-15320). Make sure it plays nicely with hbase core making use of > public-apis only (It does as best as I can see... but saying this anyways). > Once the kafka proxy is working, as subissue, move REST and thrift over... > SPARK too. > This might be better done for an hbase3 target. I filed it against hbase2.2 > for now. > See discussion up on dev list, "[DISCUSS] Kafka Connection, HBASE-15320", > https://s.apache.org/RQcC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
