Access to ASF Jenkins
Hi, I'd be interested to work on precommit integration for hbase-connectors repository. (HBASE-21432) Can I request access to make modifications to Apache Jenkins in order to create new job for this integration? Thanks, Peter
Re: Access to ASF Jenkins
Sounds good to me. FYI, this is something the PMC Chair does via the Whimsy roster tool: https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount https://whimsy.apache.org/roster/group/hudson-jobadmin Misty, give a shout if you'd like some help. On Tue, Nov 6, 2018 at 9:15 AM Peter Somogyi wrote: > > Hi, > > I'd be interested to work on precommit integration for hbase-connectors > repository. (HBASE-21432) > Can I request access to make modifications to Apache Jenkins in order to > create new job for this integration? > > Thanks, > Peter
[jira] [Reopened] (HBASE-21247) Custom Meta WAL Provider doesn't default to custom WAL Provider whose configuration value is outside the enums in Providers
[ https://issues.apache.org/jira/browse/HBASE-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu reopened HBASE-21247: > Custom Meta WAL Provider doesn't default to custom WAL Provider whose > configuration value is outside the enums in Providers > --- > > Key: HBASE-21247 > URL: https://issues.apache.org/jira/browse/HBASE-21247 > Project: HBase > Issue Type: Bug > Components: wal >Affects Versions: 3.0.0, 2.2.0, 2.1.1, 2.0.2 >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Major > Fix For: 3.0.0 > > Attachments: 21247.branch-2.patch, 21247.v1.txt, 21247.v10.txt, > 21247.v11.txt, 21247.v2.txt, 21247.v3.txt, 21247.v4.tst, 21247.v4.txt, > 21247.v5.txt, 21247.v6.txt, 21247.v7.txt, 21247.v8.txt, 21247.v9.txt > > > Currently all the WAL Providers acceptable to hbase are specified in > Providers enum of WALFactory. > This restricts the ability for custom Meta WAL Provider to default to the > custom WAL Provider which is supplied by class name. > This issue fixes the bug by allowing the specification of new WAL Provider > class name using the config "hbase.wal.provider". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21430) [hbase-connectors] Move hbase-spark* modules to hbase-connectors repo
[ https://issues.apache.org/jira/browse/HBASE-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21430. --- Resolution: Fixed Fix Version/s: 2.2.0 3.0.0 Release Note: hbase-spark* modules have been cloned to https://github.com/apache/hbase-connectors All spark connector dev is to happen in that repo from here on out. Let me file a subtask to remove hbase-spark* modules from hbase core. > [hbase-connectors] Move hbase-spark* modules to hbase-connectors repo > - > > Key: HBASE-21430 > URL: https://issues.apache.org/jira/browse/HBASE-21430 > Project: HBase > Issue Type: Bug > Components: hbase-connectors, spark >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Exploring moving the spark modules out of core hbase and into > hbase-connectors. Perhaps spark is deserving of its own repo (I think > [~busbey] was on about this) but meantime, experimenting w/ having it out in > hbase-connectors. > Here is thread on spark integration > https://lists.apache.org/thread.html/fd74ef9b9da77abf794664f06ea19c839fb3d543647fb29115081683@%3Cdev.hbase.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] Gitbox<-> JIRA (WAS: [DISCUSS] Kafka Connection, HBASE-15320)
https://issues.apache.org/jira/browse/INFRA-17217 Ongoing. S On Mon, Nov 5, 2018 at 12:17 PM Andrew Purtell wrote: > +1, please do > > On Mon, Nov 5, 2018 at 9:55 AM Stack wrote: > > > I was going to file an issue w/ INFRA this evening asking that they > disable > > github comment/commits being added as JIRA comments (See HBASE-21435 for > an > > innocuous example of this feature in action and HBASE-21430 for an > > illustration of how it can quickly turn silly). While I could see > > github-comments-appearing-as-JIRA comments working if the changesets were > > small, it blows away JIRA if the change has any weight at all. > > > > I was going to ask that the github/gitbox commentary instead go to > issues@ > > mailing list (Sean suggestion. Duo and our Peter asked off-list suggested > > we not fill JIRA comments). Shout if you are against or have any > > preferences. > > > > Yours, > > S > > > > > > > > On Fri, Nov 2, 2018 at 11:43 AM Stack wrote: > > > > > Related, interesting thread on how various projects are doing the > > > github<->asf connection has just started[1]. > > > > > > A few have a notifications list that gets the github notification > emails. > > > Email clients make parseable threads of the firehose apparently. We > might > > > do same. > > > > > > S > > > 1. > > > > > > http://mail-archives.apache.org/mod_mbox/community-dev/201811.mbox/browser > > > > > > On Fri, Nov 2, 2018 at 10:37 AM Josh Elser wrote: > > > > > >> > > >> > > >> On 11/2/18 11:20 AM, Stack wrote: > > >> > On Fri, Nov 2, 2018 at 7:30 AM Josh Elser > wrote: > > >> > > > >> >> Nice stuff, Stack! > > >> >> > > >> >> > > >> > Not me. It Mike's work. > > >> > > > >> > > >> Sorry, didn't mean it that way. Was happy to see you pushing the > > >> hbase-connectors repo forward :) > > >> > > >> Obviously kudos to MikeW for the code itself! > > >> > > >> >> Two quick questions: > > >> >> > > >> >> First, on provenance: this codebase primarily came from Mike > Wingert > > on > > >> >> https://issues.apache.org/jira/browse/HBASE-15320? Just saw that > the > > >> >> commit came from your email addr -- wasn't sure if that Mike was > > still > > >> >> involved (or you took it to completion). > > >> >> > > >> >> > > >> > You talking about the merge done over on the hbase-connectors? > > >> > > > >> > Looks like I get blamed for the merge -- if I do a show on the merge > > >> > commit, it is nothing but the merge note "Merge pull request #3 from > > >> > hbasejanitor/master" where hbasejanitor is Mike's handle -- but then > > the > > >> > merge note is followed by Mikes' work, properly attributed to him. > > >> > > > >> > I did not pay close attention to this aspect of how git boxing does > > it. > > >> > Seems fine to me. What you think? > > >> > > >> Ahh, no, this was just me. I think I only looked at the first > commit(s), > > >> and not far enough down the list. No concerns. > > >> > > >> >> Second, I assume this new Git repo had all of the normal > email-hooks > > >> set > > >> >> up. Do you know where they are being sent (dev, commit, or issues)? > > I'm > > >> >> also assuming that this is a Gitbox repo -- are we OK with > > >> pull-requests > > >> >> to this repo (as well as operator-tools) but still create a Jira > > issue? > > >> >> > > >> >> > > >> > Yep, gitbox. It has whatever infra set it up as. > > >> > > > >> > Back and forth was dumped into HBASE-21002 (We changed this config > on > > >> > hbase-operator-tools config to not do this? I should look). > > >> > > > >> > Regards pull requests, etc., email configs., etc., we are in > > >> experimental > > >> > mode around all this stuff trying to figure it out so > > >> > suggestions/help/exercising the possibilities are all welcome. > > >> > > > >> > Thanks, > > >> > S > > >> > > >> Grand. Thanks for the reminder. Had a random question in Slack the > other > > >> day about contributions -- will keep the "pave your own road" mindset > in > > >> the fore-front :) > > >> > > >> >> - Josh > > >> >> > > >> >> On 10/31/18 6:43 PM, Stack wrote: > > >> >>> To tie-off this thread, this nice feature was just pushed on > > >> >>> hbase-connector. See > > >> >>> https://github.com/apache/hbase-connectors/tree/master/kafka for > > >> how-to. > > >> >>> Review and commentary welcome. > > >> >>> > > >> >>> Thanks, > > >> >>> S > > >> >>> > > >> >>> On Fri, Aug 3, 2018 at 6:32 AM Hbase Janitor < > > hbasejani...@gmail.com> > > >> >> wrote: > > >> >>> > > >> I opened hbase-21002 to start the scripts and assembly. > > >> > > >> Mike > > >> > > >> On Thu, Aug 2, 2018, 19:29 Stack wrote: > > >> > > >> > Up in https://issues.apache.org/jira/browse/HBASE-20934 I > created > > >> an > > >> > hbase-connectors repo. I put some form on it using the v19 patch > > >> from > > >> > HBASE-15320 "HBase connector for Kafka Connect". It builds and > > tests > > >> > pass. Here are some remaining TODOs: > > >> > > > >> >* Figure how to do start
[DISCUSS] Kafka Connection, HBASE-15320
Continuing the consensus on this thread, I'm now working on moving the spark connector out of core. HBASE-21430 clones our current modules (after some pom cleanup and dependency messing). I'm now working on subtask to purge them from our main repo. Will put more info on our old hbase-spark integration DISCUSS thread from a while back. S On Fri, Nov 2, 2018 at 11:43 AM Stack wrote: > Related, interesting thread on how various projects are doing the > github<->asf connection has just started[1]. > > A few have a notifications list that gets the github notification emails. > Email clients make parseable threads of the firehose apparently. We might > do same. > > S > 1. > http://mail-archives.apache.org/mod_mbox/community-dev/201811.mbox/browser > > On Fri, Nov 2, 2018 at 10:37 AM Josh Elser wrote: > >> >> >> On 11/2/18 11:20 AM, Stack wrote: >> > On Fri, Nov 2, 2018 at 7:30 AM Josh Elser wrote: >> > >> >> Nice stuff, Stack! >> >> >> >> >> > Not me. It Mike's work. >> > >> >> Sorry, didn't mean it that way. Was happy to see you pushing the >> hbase-connectors repo forward :) >> >> Obviously kudos to MikeW for the code itself! >> >> >> Two quick questions: >> >> >> >> First, on provenance: this codebase primarily came from Mike Wingert on >> >> https://issues.apache.org/jira/browse/HBASE-15320? Just saw that the >> >> commit came from your email addr -- wasn't sure if that Mike was still >> >> involved (or you took it to completion). >> >> >> >> >> > You talking about the merge done over on the hbase-connectors? >> > >> > Looks like I get blamed for the merge -- if I do a show on the merge >> > commit, it is nothing but the merge note "Merge pull request #3 from >> > hbasejanitor/master" where hbasejanitor is Mike's handle -- but then the >> > merge note is followed by Mikes' work, properly attributed to him. >> > >> > I did not pay close attention to this aspect of how git boxing does it. >> > Seems fine to me. What you think? >> >> Ahh, no, this was just me. I think I only looked at the first commit(s), >> and not far enough down the list. No concerns. >> >> >> Second, I assume this new Git repo had all of the normal email-hooks >> set >> >> up. Do you know where they are being sent (dev, commit, or issues)? I'm >> >> also assuming that this is a Gitbox repo -- are we OK with >> pull-requests >> >> to this repo (as well as operator-tools) but still create a Jira issue? >> >> >> >> >> > Yep, gitbox. It has whatever infra set it up as. >> > >> > Back and forth was dumped into HBASE-21002 (We changed this config on >> > hbase-operator-tools config to not do this? I should look). >> > >> > Regards pull requests, etc., email configs., etc., we are in >> experimental >> > mode around all this stuff trying to figure it out so >> > suggestions/help/exercising the possibilities are all welcome. >> > >> > Thanks, >> > S >> >> Grand. Thanks for the reminder. Had a random question in Slack the other >> day about contributions -- will keep the "pave your own road" mindset in >> the fore-front :) >> >> >> - Josh >> >> >> >> On 10/31/18 6:43 PM, Stack wrote: >> >>> To tie-off this thread, this nice feature was just pushed on >> >>> hbase-connector. See >> >>> https://github.com/apache/hbase-connectors/tree/master/kafka for >> how-to. >> >>> Review and commentary welcome. >> >>> >> >>> Thanks, >> >>> S >> >>> >> >>> On Fri, Aug 3, 2018 at 6:32 AM Hbase Janitor >> >> wrote: >> >>> >> I opened hbase-21002 to start the scripts and assembly. >> >> Mike >> >> On Thu, Aug 2, 2018, 19:29 Stack wrote: >> >> > Up in https://issues.apache.org/jira/browse/HBASE-20934 I created >> an >> > hbase-connectors repo. I put some form on it using the v19 patch >> from >> > HBASE-15320 "HBase connector for Kafka Connect". It builds and tests >> > pass. Here are some remaining TODOs: >> > >> >* Figure how to do start scripts: e.g. we need to start up the >> kafka >> > proxy. It wants some hbase jars, conf dir, and others on the >> CLASSPATH >> > (Depend on an HBASE_HOME and then source bin/hbase?) >> >* Can any of the connectors make-do with the shaded client? >> >* Make connectors standalone or have them share conf, bin, etc? >> >* Need to do an assembly. Not done. >> >* Move over REST and thrift next. Mapreduce after? >> > >> > The poms could do w/ a review. Hacked them over from >> hbase-thirdparty. >> > >> > File issues and apply patches up in JIRA if your up for any of the >> >> above. >> > >> > Thanks, >> > S >> > >> > On Wed, Jul 25, 2018 at 10:46 PM Stack wrote: >> >> >> >> >> >> On Tue, Jul 24, 2018 at 10:01 PM Misty Linville >> > wrote: >> >>> >> >>> I like the idea of a separate connectors repo/release vehicle, but >> I'm a >> >>> little concerned about the need to release all together to update >> >> just >> > one >> >>> of the connectors. How would t
[jira] [Reopened] (HBASE-21396) Create 2.1.1 release
[ https://issues.apache.org/jira/browse/HBASE-21396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey reopened HBASE-21396: - > Create 2.1.1 release > > > Key: HBASE-21396 > URL: https://issues.apache.org/jira/browse/HBASE-21396 > Project: HBase > Issue Type: Task > Components: rm >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21442) Update branch-2.1 for next development cycle
Sean Busbey created HBASE-21442: --- Summary: Update branch-2.1 for next development cycle Key: HBASE-21442 URL: https://issues.apache.org/jira/browse/HBASE-21442 Project: HBase Issue Type: Sub-task Components: build Affects Versions: 2.1.1 Reporter: Sean Busbey Assignee: Sean Busbey Fix For: 2.1.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21442) Update branch-2.1 for next development cycle
[ https://issues.apache.org/jira/browse/HBASE-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-21442. - Resolution: Fixed > Update branch-2.1 for next development cycle > > > Key: HBASE-21442 > URL: https://issues.apache.org/jira/browse/HBASE-21442 > Project: HBase > Issue Type: Sub-task > Components: build >Affects Versions: 2.1.1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 2.1.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21396) Create 2.1.1 release
[ https://issues.apache.org/jira/browse/HBASE-21396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-21396. - Resolution: Fixed all set now, re-resolving. > Create 2.1.1 release > > > Key: HBASE-21396 > URL: https://issues.apache.org/jira/browse/HBASE-21396 > Project: HBase > Issue Type: Task > Components: rm >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21443) [hbase-connectors] Purge hbase-* modules from core now they've been moved to hbase-connectors
stack created HBASE-21443: - Summary: [hbase-connectors] Purge hbase-* modules from core now they've been moved to hbase-connectors Key: HBASE-21443 URL: https://issues.apache.org/jira/browse/HBASE-21443 Project: HBase Issue Type: Sub-task Components: hbase-connectors, spark Affects Versions: 3.0.0, 2.2.0 Reporter: stack Assignee: stack Fix For: 3.0.0, 2.2.0 The parent copied the spark modules over to hbase-connectors. Here we purge them from hbase core repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] status of and plans for our hbase-spark integration
I've been doing a bit of work on this old project. Added a doc of notes that come of revisiting this effort to the HBASE-18405 issue. My first step is moving the hbase-spark* modules out of hbase core repo to sit under hbase-connectors (HBASE-21443). Moving out of core will help w/ some of the items raised above. Will be back. S On Wed, Jun 21, 2017 at 9:31 AM Sean Busbey wrote: > Hi Folks! > > We've had integration with Apache Spark lingering in trunk for quite > some time, and I'd like us to push towards firming it up. I'm going to > try to cover a lot of ground below, so feel free to respond to just > pieces and I'll write up a doc on things afterwards. > > For background, the hbase-spark module currently exists in trunk, > branch-2, and the 2.0.0-alpha-1 release. Importantly, it has been in > no "ready to use" release so far. It's been in master for ~2 years and > has had a total of nearly 70 incremental changes. Right now it shows > up in Stack’s excellent state of 2.0 doc ( https://s.apache.org/1mB4 ) > as a nice-to-have. I’d like to get some consensus on either getting it > into release trains or officially move it out of scope for 2.0. > > > > 1) Branch-1 releases > > In July 2015 we started tracking what kind of polish was needed for > this code to make it into our downstream facing release lines in > HBASE-14160. Personally, I think if the module isn't ready for a > branch-1 release than it shouldn't be in a branch-2 release either. > > The only things still tracked as required are some form of published > API docs (HBASE-17766) and an IT that we can run (HBASE-18175). Our Yi > Liang has been working on both of these, and I think we have a good > start on them. > > Is there anything else we ought to be tracking here? I notice the > umbrella "make the connector better" issue (HBASE-14789) has only > composite row key support still open (HBASE-15335). It looks like that > work stalled out last summer after an admirable effort by our Zhan > Zhang. Can this wait for a future minor release? > > Personally, I'd like to see HBASE-17766 and HBASE-18175 closed out and > then our existing support backported to branch-1 in time for whenever > we get HBase 1.4 started. > > 2) What Spark version(s) do we care about? > > The hbase-spark module originally started with support for Spark 1.3. > It currently sits at supporting just 1.6. Our Ted Yu has been > dutifully trying to find consensus on how we handle Spark 2.0 over in > HBASE-16179 for nearly a year. > > AFAICT the Spark community has no more notion of what version(s) their > downstream users are relying on than we do. It appears that Spark 1.6 > will be their last 1.y release and at least the dev community is > largely moving on to 2.y releases now. > > What version(s) do we want to handle and thus encourage our downstream > folks to use? > > Just as a point of reference, Spark 1.6 doesn't have any proper > handling of delegation tokens and our current do-it-ourselves > workaround breaks in the presence of the support introduced in Spark > 2. > > The way I see it, the options are a) ship both 1.6 and 2.y support, b) > ship just 2.y support, c) ship 1.6 in branch-1 and ship 2.y in > branch-2. Does anyone have preferences here? > > Personally, I think I favor option b for simplicity, though I don't > care for more possible delay in getting stuff out in branch-1. > Probably option a would be best for our downstreamers. > > Related, while we've been going around on HBASE-16179 the Apache Spark > community started shipping 2.1 releases and is now in the process of > finalizing 2.2. Do we need to do anything different for these > versions? > > Spark’s versioning policy suggests “not unless we want to support > newer APIs or used alpha stuff”. But I don’t have practical experience > with how this plays out in yet. > > http://spark.apache.org/versioning-policy.html > > > 3) What scala version(s) do we care about? > > For those who aren't aware, Scala compatibility is a nightmare. Since > Scala is still the primary language for implementation of Spark jobs, > we have to care more about this than I'd like. (the only way out, I > think, would be to implement our integration entirely in some other > JVM language) > > The short version is that each minor version of scala (we care about) > is mutually incompatible with all others. Right now both Spark 1.6 and > Spark 2.y work with each of Scala 2.10 and 2.11. There's talk of > adding support for Scala 2.12, but it will not happen until after > Spark 2.2. > > (for those looking for a thread on Scala versions in Spark, I think > this is the most recent: https://s.apache.org/IW4D ) > > Personally, I think we serve our downstreamers best when we ship > artifacts that work with each of the scala versions a given version of > Spark supports. It's painful to have to do something like upgrade your > scala version just because the storage layer you want to use requires > a particular version. It's also painful to have
Re: HBase developer meetup
No such luck. I have rooms in the tower, but not on the top floor (which closes at 4pm anyway). Also this will likely slip to after Thanksgiving now. I'll send out a data as soon as I have.Once I have the logistics worked out I intend to make this a more regular occurrence. -- Lars On Saturday, October 27, 2018, 5:07:59 PM PDT, Stack wrote: I think that a meeting at the top of the salesforce tower will have a markedly better attendance than one held elsewhere (Its cool being able to look down on the helicopters circling below you!). S On Tue, Oct 23, 2018 at 4:01 PM la...@apache.org wrote: > This is still on. > I'm trying to get us a spot in the Salesforce tower top floor. As you can > imagine it's a coveted spot.If I can't get a time slot there in the next > week I'll book a "usual" conference room. > Stay tuned. > Thanks. > -- Lars > > On Friday, October 5, 2018, 1:00:42 PM PDT, la...@apache.org < > la...@apache.org> wrote: > > Last call :) > On Monday, October 1, 2018, 10:08:13 AM PDT, la...@apache.org < > la...@apache.org> wrote: > > 9 people signed up so far.This is a good chance to make your voice > heard, give input, and help point the project in the right direction going > forward. > -- Lars > On Friday, September 28, 2018, 10:37:02 AM PDT, la...@apache.org < > la...@apache.org> wrote: > > Hi all, > I'm planning to put together an HBase developer meetup at the Salesforce > office (with video conference for those who cannot attend in person) in the > next few weeks. > If you're interested please put your name in this spreadsheet: > https://docs.google.com/spreadsheets/d/13eIMItFbM35K_lfn9woGGObW-12tfyOVLqZi8X4p5PM/edit#gid=0 > > This is a chance to get all those who contribute to HBase together. There > will also be food. :)I will leave the spreadsheet up for one week - until > Friday October 5th. > Possible agenda:- Round-table- Status of branch-1, branch-2, and master- > Current challenges (operations?, public cloud?, availability?, > performance?, community?)- Future direction. Where do we want HBase to be > in 1 years, 2 years, 5 years?- more... > Thanks. > -- Lars >
[jira] [Created] (HBASE-21444) Recover meta in case of long ago dead region server appear in meta znode
Ankit Singhal created HBASE-21444: - Summary: Recover meta in case of long ago dead region server appear in meta znode Key: HBASE-21444 URL: https://issues.apache.org/jira/browse/HBASE-21444 Project: HBase Issue Type: Bug Affects Versions: 2.0.2 Reporter: Ankit Singhal Assignee: Ankit Singhal -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21445) CopyTable by bulkload will write hfile into yarn's HDFS
Zheng Hu created HBASE-21445: Summary: CopyTable by bulkload will write hfile into yarn's HDFS Key: HBASE-21445 URL: https://issues.apache.org/jira/browse/HBASE-21445 Project: HBase Issue Type: Bug Components: mapreduce Reporter: Zheng Hu Assignee: Zheng Hu When using CopyTable with bulkload, I found that all hfile's are written in our Yarn's HDFS cluster. and failed to load hfiles into HBase cluster, because we use different HDFS between yarn cluster and hbase cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21446) [hbase-connectors] Update spark and scala versions; add some doc on how to generate artifacts with different versions
stack created HBASE-21446: - Summary: [hbase-connectors] Update spark and scala versions; add some doc on how to generate artifacts with different versions Key: HBASE-21446 URL: https://issues.apache.org/jira/browse/HBASE-21446 Project: HBase Issue Type: Bug Components: hbase-connectors, spark Reporter: stack Assignee: stack Fix For: connector-1.0.0 Our spark version was 2.1.1. and scala 2.11.1. Update to 2.4.0/2.11.12. Add doc on how to generate artifacts that use different spark and scala. Scala 2.10.x and 2.12.x need work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21446) [hbase-connectors] Update spark and scala versions; add some doc on how to generate artifacts with different versions
[ https://issues.apache.org/jira/browse/HBASE-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21446. --- Resolution: Fixed Release Note: Updates our hbase-spark integration so defaults spark 2.4.0 (October 2018) from 2.1.1 and Scala 2.11.12 (from 2.11.8). Merged. Resolving. > [hbase-connectors] Update spark and scala versions; add some doc on how to > generate artifacts with different versions > - > > Key: HBASE-21446 > URL: https://issues.apache.org/jira/browse/HBASE-21446 > Project: HBase > Issue Type: Bug > Components: hbase-connectors, spark >Reporter: stack >Assignee: stack >Priority: Major > Fix For: connector-1.0.0 > > > Our spark version was 2.1.1. and scala 2.11.8. Update to 2.4.0/2.11.12. > Add doc on how to generate artifacts that use different spark and scala. > Scala 2.10.x and 2.12.x need work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
