Re: [VOTE] Apache Bahir Flink 1.1.0 (RC2)
Hi, My bad, an upgrade ended up mucking up the acls on /var/run/docker.sock on my box and so other problems. With that fixed, rest looks good to me. Signatures, digests, etc check out fine. Checked out tag and build/tested. +1 for release. Regards, Mridul On Sat, Jul 30, 2022 at 9:22 AM João Boto wrote: > Hi Mridul, > > Thanks for checking.. > Do you have installed on your computer a docker environment? > This is needed for testcontainers that we use on testing.. > > Le me know if is that > > On 2022/07/29 15:11:21 Mridul Muralidharan wrote: > > The tests failed for me with [1] > > I also saw this at the top of build [2], but dont think it was related. > > > > Any pointers ? > > > > Thanks, > > Mridul > > > > [1] > > > > [INFO] Running org.apache.flink.streaming.connectors.flume.FlumeSinkTest > > > > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > > > > SLF4J: Defaulting to no-operation (NOP) logger implementation > > > > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for > further > > details. > > > > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > > 0.132 s <<< FAILURE! - in > > org.apache.flink.streaming.connectors.flume.FlumeSinkTest > > > > [ERROR] testSink Time elapsed: 0.09 s <<< ERROR! > > > > java.lang.IllegalStateException: Could not find a valid Docker > environment. > > Please see logs and check configuration > > > > > > [INFO] Running org.apache.flink.streaming.connectors.flume.FlumeUtilsTest > > > > [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: > > 0.004 s <<< FAILURE! - in > > org.apache.flink.streaming.connectors.flume.FlumeUtilsTest > > > > [ERROR] testGetRpcClient Time elapsed: 0.001 s <<< ERROR! > > > > java.lang.IllegalStateException: Previous attempts to find a Docker > > environment failed. Will not retry. Please see logs and check > configuration > > > > > > [ERROR] testDestroy Time elapsed: 0.002 s <<< ERROR! > > > > java.lang.IllegalStateException: Previous attempts to find a Docker > > environment failed. Will not retry. Please see logs and check > configuration > > > > > > [INFO] > > > > [INFO] Results: > > > > [INFO] > > > > [ERROR] Errors: > > > > [ERROR] FlumeSinkTest>FlumeServerTest.init:43 » IllegalState Could not > > find a valid Do... > > > > [ERROR] FlumeUtilsTest>FlumeServerTest.init:43 » IllegalState Previous > > attempts to fin... > > > > [ERROR] FlumeUtilsTest>FlumeServerTest.init:43 » IllegalState Previous > > attempts to fin... > > > > [INFO] > > > > [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0 > > > > [2] > > > > [WARNING] > > > > [WARNING] Some problems were encountered while building the effective > model > > for org.apache.bahir:flink-connector-pinot_2.11:jar:1.1.0 > > > > [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' > must > > be unique but found duplicate declaration of plugin > > org.apache.maven.plugins:maven-enforcer-plugin @ line 193, column 25 > > > > [WARNING] > > > > [WARNING] It is highly recommended to fix these problems because they > > threaten the stability of your build. > > > > [WARNING] > > > > [WARNING] For this reason, future Maven versions might no longer support > > building such malformed projects. > > > > [WARNING] > > > > On Wed, Jul 27, 2022 at 6:45 AM Joao Boto wrote: > > > > > Dear community member, > > > > > > Please vote to approve the release of Apache Bahir Flink 1.1.0 (RC2) > based > > > on > > > Apache Flink 1.14.5. > > > > > > Tag: v1.1.0-rc2 > > > (38092f025046fd4850c49a943e9197f67aabda54) > > > https://github.com/apache/bahir-flink/tree/v1.1.0-rc2 > > > > > > Release files: > > > https://repository.apache.org/content/repositories/orgapachebahir-1033 > > > > > > Source distribution: > > > https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1.1.0-rc2/ > > > > > > > > > The vote is open for at least 72 hours and passes if a majority of at > least > > > 3 +1 PMC votes are cast. > > > > > > [ ] +1 Release this package as Apache Bahir Flink 1.1.0 > > > [ ] -1 Do not release this package because ... > > > > > > > > > Thanks for your vote! > > > > > >
Re: [VOTE] Apache Bahir Flink 1.1.0 (RC2)
The tests failed for me with [1] I also saw this at the top of build [2], but dont think it was related. Any pointers ? Thanks, Mridul [1] [INFO] Running org.apache.flink.streaming.connectors.flume.FlumeSinkTest SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.132 s <<< FAILURE! - in org.apache.flink.streaming.connectors.flume.FlumeSinkTest [ERROR] testSink Time elapsed: 0.09 s <<< ERROR! java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration [INFO] Running org.apache.flink.streaming.connectors.flume.FlumeUtilsTest [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in org.apache.flink.streaming.connectors.flume.FlumeUtilsTest [ERROR] testGetRpcClient Time elapsed: 0.001 s <<< ERROR! java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration [ERROR] testDestroy Time elapsed: 0.002 s <<< ERROR! java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] FlumeSinkTest>FlumeServerTest.init:43 » IllegalState Could not find a valid Do... [ERROR] FlumeUtilsTest>FlumeServerTest.init:43 » IllegalState Previous attempts to fin... [ERROR] FlumeUtilsTest>FlumeServerTest.init:43 » IllegalState Previous attempts to fin... [INFO] [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0 [2] [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.bahir:flink-connector-pinot_2.11:jar:1.1.0 [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-enforcer-plugin @ line 193, column 25 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] On Wed, Jul 27, 2022 at 6:45 AM Joao Boto wrote: > Dear community member, > > Please vote to approve the release of Apache Bahir Flink 1.1.0 (RC2) based > on > Apache Flink 1.14.5. > > Tag: v1.1.0-rc2 > (38092f025046fd4850c49a943e9197f67aabda54) > https://github.com/apache/bahir-flink/tree/v1.1.0-rc2 > > Release files: > https://repository.apache.org/content/repositories/orgapachebahir-1033 > > Source distribution: > https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1.1.0-rc2/ > > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir Flink 1.1.0 > [ ] -1 Do not release this package because ... > > > Thanks for your vote! >
Re: [DISCUSS][bahir-flink] Drop Java 7 support
Thanks for clarifying Robert ! Given this, I am +1 on removing support too. Regards, Mridul On Mon, Sep 18, 2017 at 11:02 AM, Robert Metzger wrote: > Thanks all for the overwhelming support to drop Java7. > > @Mridul: I don't know for sure what the schedule for Flink 1.4 is. I > believe it'll come out in the next 1-2 months. > I don't think its necessary to do a bahir-flink release before Flink 1.4. > > On Sun, Sep 17, 2017 at 9:02 AM, Luciano Resende > wrote: > >> +1 >> >> On Sat, Sep 16, 2017 at 2:04 AM, Robert Metzger >> wrote: >> >> > Hi, >> > >> > In the Flink InfluxDB Sink PR [1], there is a little discussion regarding >> > Java 7 support in bahir-flink. >> > >> > I'm proposing to drop Java 7 support in bahir-flink. As of the upcoming >> > Flink 1.4 release, Flink will also drop Java 7 support. >> > >> > Let me know if somebody has any concerns, otherwise, we'll probably drop >> > the Java7 travis checks in the mentioned PR. >> > >> > >> > Regards, >> > Robert >> > >> > >> > [1] https://github.com/apache/bahir-flink/pull/21 >> > >> >> >> >> -- >> Luciano Resende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ >>
Re: [DISCUSS][bahir-flink] Drop Java 7 support
Do we know when Flink 1.4 is expected to be out ? Will we be making any intermediate Bahir release for flink before then ? If we are not making any, then dropping java 7 will have no impact for our users. On spark side, jdk 7 support has already been dropped. Regards, Mridul On Sat, Sep 16, 2017 at 2:04 AM, Robert Metzger wrote: > Hi, > > In the Flink InfluxDB Sink PR [1], there is a little discussion regarding > Java 7 support in bahir-flink. > > I'm proposing to drop Java 7 support in bahir-flink. As of the upcoming > Flink 1.4 release, Flink will also drop Java 7 support. > > Let me know if somebody has any concerns, otherwise, we'll probably drop > the Java7 travis checks in the mentioned PR. > > > Regards, > Robert > > > [1] https://github.com/apache/bahir-flink/pull/21
Re: [VOTE] Apache Bahir 2.2.0 (RC1)
Build works fine, signatures check out, tests run successfully. +1 for release. Btw, I dont recall RAT check failing build earlier, very nice touch to enforce it as part of build ! Regards, Mridul On Wed, Aug 16, 2017 at 10:17 PM, Luciano Resende wrote: > Dear community member, > > Please vote to approve the release of Apache Bahir 2.2.0 (RC1) based on > Apache Spark 2.2.0. > > Tag: v2.2.0-rc1 (d927289fdad0e66953606869639fe2f153c37b05) > > https://github.com/apache/bahir/tree/v2.2.0-rc1 > > Release files: > > https://repository.apache.org/content/repositories/orgapachebahir-1020 > > Source distribution: > > https://dist.apache.org/repos/dist/dev/bahir/bahir-spark/2.2.0-rc1/ > > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir 2.2.0 > [ ] -1 Do not release this package because ... > > > Thanks for your vote! > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [VOTE] Apache Bahir Flink extensions 1.0 (RC5)
If it is a known issue which is yet to be fixed (and not a regression), then it is fine - since we had it earlier as well I guess. Given that, I am +1 on release; though it would be nice to get it resolved given the mismatch in release artifacts. Thanks, Mridul On Tue, May 23, 2017 at 12:38 PM, Ted Yu wrote: > I suggest getting BAHIR-88 > <https://issues.apache.org/jira/browse/BAHIR-88> fixed > - this may affect future release(s). > > On Tue, May 23, 2017 at 12:29 PM, Luciano Resende > wrote: > >> The issue reported was for Spark extensions >> https://issues.apache.org/jira/browse/BAHIR-88 >> >> >> And I guess it is also applicable for Flink extensions >> >> >> But the issue is still open. >> >> >> On Tue, May 23, 2017 at 12:08 PM, Mridul Muralidharan < >> mridul...@apache.org> >> wrote: >> >> > Hi Luciano, >> > >> > I would not consider them blocking - but I wanted clarity about >> > them, since I had seen jira's to the effect that they were fixed ? >> > Not sure if I am misremembering ! >> > >> > Regards, >> > Mridul >> > >> > >> > On Tue, May 23, 2017 at 12:01 PM, Luciano Resende >> > wrote: >> > > On Sun, May 21, 2017 at 11:50 PM, Mridul Muralidharan < >> > mridul...@apache.org> >> > > wrote: >> > > >> > >> Hi, >> > >> >> > >> From the release tag, clean build and tests work fine, signatures >> > match. >> > >> >> > >> The source at https://dist.apache.org/repos/ >> > dist/dev/bahir/bahir-flink/1. >> > >> 0-rc5/ >> > >> has additional files which are not in repo: >> > >> >> > >> Not in repo ./distribution/pom.xml.releaseBackup >> > >> Not in repo ./flink-connector-activemq/pom.xml.releaseBackup >> > >> Not in repo ./flink-connector-akka/pom.xml.releaseBackup >> > >> Not in repo ./flink-connector-flume/pom.xml.releaseBackup >> > >> Not in repo ./flink-connector-netty/pom.xml.releaseBackup >> > >> Not in repo ./flink-connector-redis/pom.xml.releaseBackup >> > >> Not in repo ./pom.xml.releaseBackup >> > >> Not in repo ./release.properties >> > >> >> > >> I thought this was fixed, but I could be remembering wrong ? >> > >> >> > >> >> > >> >> > > That's what I thought as well, but it might have been for the Spark >> > > release. >> > > >> > > Are you considering this blocking ? Or would it be ok to continue with >> > the >> > > approval of the release ? >> > > >> > > -- >> > > Luciano Resende >> > > http://twitter.com/lresende1975 >> > > http://lresende.blogspot.com/ >> > >> >> >> >> -- >> Luciano Resende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ >>
Re: [VOTE] Apache Bahir Flink extensions 1.0 (RC5)
Hi Luciano, I would not consider them blocking - but I wanted clarity about them, since I had seen jira's to the effect that they were fixed ? Not sure if I am misremembering ! Regards, Mridul On Tue, May 23, 2017 at 12:01 PM, Luciano Resende wrote: > On Sun, May 21, 2017 at 11:50 PM, Mridul Muralidharan > wrote: > >> Hi, >> >> From the release tag, clean build and tests work fine, signatures match. >> >> The source at https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1. >> 0-rc5/ >> has additional files which are not in repo: >> >> Not in repo ./distribution/pom.xml.releaseBackup >> Not in repo ./flink-connector-activemq/pom.xml.releaseBackup >> Not in repo ./flink-connector-akka/pom.xml.releaseBackup >> Not in repo ./flink-connector-flume/pom.xml.releaseBackup >> Not in repo ./flink-connector-netty/pom.xml.releaseBackup >> Not in repo ./flink-connector-redis/pom.xml.releaseBackup >> Not in repo ./pom.xml.releaseBackup >> Not in repo ./release.properties >> >> I thought this was fixed, but I could be remembering wrong ? >> >> >> > That's what I thought as well, but it might have been for the Spark > release. > > Are you considering this blocking ? Or would it be ok to continue with the > approval of the release ? > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [VOTE] Apache Bahir Flink extensions 1.0 (RC5)
Hi, From the release tag, clean build and tests work fine, signatures match. The source at https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1.0-rc5/ has additional files which are not in repo: Not in repo ./distribution/pom.xml.releaseBackup Not in repo ./flink-connector-activemq/pom.xml.releaseBackup Not in repo ./flink-connector-akka/pom.xml.releaseBackup Not in repo ./flink-connector-flume/pom.xml.releaseBackup Not in repo ./flink-connector-netty/pom.xml.releaseBackup Not in repo ./flink-connector-redis/pom.xml.releaseBackup Not in repo ./pom.xml.releaseBackup Not in repo ./release.properties I thought this was fixed, but I could be remembering wrong ? Regards, Mridul On Wed, May 17, 2017 at 1:11 PM, Luciano Resende wrote: > Please vote to approve the release of the following candidate as Apache > Bahir Flink extensions 1.0 based on Apache Flink 1.2.0. > > The tag to be voted on is v1.0-rc4 > (9350cb5f2871df2b2e03f33c5fa1239ca044505a) > > https://github.com/apache/ > bahir-flink/commit/9350cb5f2871df2b2e03f33c5fa1239ca044505a > > The release files, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachebahir-1017/ > > The source distribution is also available at: > > https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1.0-rc5/ > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir Flink extensions 1.0 > [ ] -1 Do not release this package because ... > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [VOTE] Apache Bahir Flink extensions 1.0 (RC3)
+1 for release. Tag checks out fine - full build and tests go through fine. Signatures validated. Regards, Mridul On Thu, Apr 6, 2017 at 4:08 PM, Luciano Resende wrote: > Please vote to approve the release of the following candidate as Apache > Bahir Flink extensions 1.0 based on Apache Flink 1.2.0. > > The tag to be voted on is v1.0-rc3 > (447c2158be7e3c6efb12324b0efc627d276dc828) > > https://github.com/apache/bahir-flink/commit/447c2158be7e3c6efb12324b0efc627d276dc828 > > The release files, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachebahir-1015 > > The source distribution is also available at: > > https://dist.apache.org/repos/dist/dev/bahir/bahir-flink/1.0-rc3/ > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir Flink extensions 1.0 > [ ] -1 Do not release this package because ... > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [VOTE] Apache Bahir 2.1.0 (RC1)
Thanks Christian ! +1 for release. Regards, Mridul On Tue, Feb 7, 2017 at 11:59 AM, Christian Kadner wrote: > Good catch. We appear to be missing to run the mvn `release:clean` > target after `release:prepare`. We should fix that for the next release. > All prior Apache Bahir source distributions contained these release > build artifacts. > > I created https://issues.apache.org/jira/browse/BAHIR-88 to track it. > > Thanks, Christian > >> ---- >> From: Mridul Muralidharan >> To: dev@bahir.apache.org >> Date: 02/07/2017 10:53 AM >> Subject: Re: [VOTE] Apache Bahir 2.1.0 (RC1) >> >> >> >> The tests pass, and the signatures check out. >> >> I noticed that there are a few 'releaseBackup' files and >> 'release.properties' in the 'source distribution' which are not from >> our repo (probably some artifact of the build process ?). >> I am +1 assuming this is not an issue : have not noticed (or probably >> checked) this in earlier releases. >> >> >> Regards, >> Mridul >> >> >> On Sat, Feb 4, 2017 at 2:21 AM, Christian Kadner wrote: >> > Dear community member, >> > >> > please vote to approve the release of Apache Bahir 2.1.0 (RC1) based on >> > Apache Spark 2.1.0. >> > >> > Changes: >> > >> > https://github.com/apache/bahir/compare/v2.0.2-rc3...v2.1.0-rc1 >> > >> > Tag: v2.1.0-rc1 (e61cc3d) >> > >> > https://github.com/apache/bahir/tree/v2.1.0-rc1 >> > >> > Release files: >> > >> > https://repository.apache.org/content/repositories/orgapachebahir-1012 >> > >> > Source distribution: >> > >> > https://dist.apache.org/repos/dist/dev/bahir/2.1.0-rc1/ >> > >> > >> > The vote is open for at least 72 hours and passes if a majority of at > least >> > 3 +1 PMC votes are cast. >> > >> > [ ] +1 Release this package as Apache Bahir 2.1.0 >> > [ ] -1 Do not release this package because ... >> > >> > >> > Thanks for you vote! >> >>
Re: [VOTE] Apache Bahir 2.1.0 (RC1)
The tests pass, and the signatures check out. I noticed that there are a few 'releaseBackup' files and 'release.properties' in the 'source distribution' which are not from our repo (probably some artifact of the build process ?). I am +1 assuming this is not an issue : have not noticed (or probably checked) this in earlier releases. Regards, Mridul On Sat, Feb 4, 2017 at 2:21 AM, Christian Kadner wrote: > Dear community member, > > please vote to approve the release of Apache Bahir 2.1.0 (RC1) based on > Apache Spark 2.1.0. > > Changes: > > https://github.com/apache/bahir/compare/v2.0.2-rc3...v2.1.0-rc1 > > Tag: v2.1.0-rc1 (e61cc3d) > > https://github.com/apache/bahir/tree/v2.1.0-rc1 > > Release files: > > https://repository.apache.org/content/repositories/orgapachebahir-1012 > > Source distribution: > > https://dist.apache.org/repos/dist/dev/bahir/2.1.0-rc1/ > > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir 2.1.0 > [ ] -1 Do not release this package because ... > > > Thanks for you vote!
Re: [VOTE] Apache Bahir 2.0.2 (RC3)
+1 Build succeeds and tests run fine from the tag. Signature's check out fine. Regards, Mridul On Fri, Jan 20, 2017 at 6:31 PM, Christian Kadner wrote: > Please vote to approve the third release candidate for Apache Bahir > version 2.0.2 based on Apache Spark 2.0.2. > > The difference between 2.0.1 and 2.0.2 RC3 can be visualized at: > > https://github.com/apache/bahir/compare/v2.0.1-rc1...v2.0.2-rc3 > > The tag to be voted on is v2.0.2-rc3 > (477ca1b556d2486b8c9ddbfb7a327ed8245066c4) > > https://github.com/apache/bahir/tree/477ca1b556d2486b8c9ddbfb7a327ed8245066c4 > > The release files, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachebahir-1011 > > The source distribution is also available at: > > https://dist.apache.org/repos/dist/dev/bahir/2.0.2-rc3/ > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir 2.0.2 > [ ] -1 Do not release this package because ... > > Thanks for you vote!
Re: [ANNOUNCE] New Apache Bahir Committer : Christian Kadner
Congratulations Christian ! Regards, Mridul On Wed, Nov 30, 2016 at 5:17 PM, Luciano Resende wrote: > The Project Management Committee (PMC) for Apache Bahir > has invited Christian Kadner to become a committer and we are pleased > to announce that he has accepted. > > Christian has been a key community member contributing to Bahir since it's > inception and has continuously helped and reviewed contribution from others > on the Bahir community. > > Welcome Christian > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [VOTE] Apache Bahir 2.0.1 (RC1)
+1 for release. Tests pass. Signatures checkout. Great work everybody ! Regards, Mridul On Sat, Oct 15, 2016 at 11:16 AM, Luciano Resende wrote: > Please vote to approve the release of the following candidate as Apache > Bahir version 2.0.1 based on Apache Spark 2.0.1. > > The tag to be voted on is v2.0.1-rc1 > (bd00d2e4aa8c4cc8837bcaa1d0d95d3e8997ac8c) > > https://github.com/apache/bahir/tree/ > bd00d2e4aa8c4cc8837bcaa1d0d95d3e8997ac8c > > The release files, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachebahir-1004 > > The source distribution is also available at: > > https://dist.apache.org/repos/dist/dev/bahir/2.0.1-rc1/ > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Bahir 2.0.1 > [ ] -1 Do not release this package because ... > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: [ANNOUNCE] New Apache Bahir Committer : Robert Metzger
Congratulations Robert ! Regards Mridul On Oct 19, 2016 2:54 PM, "Luciano Resende" wrote: > The Project Management Committee (PMC) for Apache Bahirhas invited > Robert Metzger to become a committer and we are pleased to announce > that he has accepted. > > Robert has been a key community member championing the extensions > related to Apache Flink. > > > Welcome Robert > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
Re: Documentation for Bahir Flink extensions
+1 sounds good. Regards Mridul On Friday, August 26, 2016, Luciano Resende wrote: > For the Spark extensions we currently have a README.md on each extension > project which helps users accessing github to easily find out how to use > the extension, and we also use that to "copy" to the website and add some > style to it, so it can also be used as the website documentation. > > Here is a readme.md > > https://github.com/apache/bahir/tree/master/sql-streaming-mqtt > > And then it gets copied to the website as > > http://bahir.apache.org/docs/spark/current/spark-sql-streaming-mqtt/ > > I would like to propose a similar approach for creating documentation for > the Bahir flink extensions. > > Thoughts ? > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
Re: [ANNOUNCE] Apache Bahir 2.0.0
Congratulations, great job everyone ! Regards, Mridul On Mon, Aug 15, 2016 at 2:19 PM, Luciano Resende wrote: > The Apache Bahir PMC is pleased to announce the release of Apache Bahir > 2.0.0 which is our first major release and provides the following > extensions for Apache Spark 2.0.0 : > > Akka Streaming > MQTT Streaming and Structured Streaming > Twitter Streaming > ZeroMQ Streaming > > For more information about Apache Bahir and to download the release: > > http://bahir.apache.org > > Thanks, > > The Apache Bahir PMC
Re: [ANNOUNCE] Apache Bahir 2.0.0
Congratulations, great job everyone ! Regards Mridul On Monday, August 15, 2016, Luciano Resende wrote: > The Apache Bahir PMC is pleased to announce the release of Apache Bahir > 2.0.0 which is our first major release and provides the following > extensions for Apache Spark 2.0.0 : > > Akka Streaming > MQTT Streaming and Structured Streaming > Twitter Streaming > ZeroMQ Streaming > > For more information about Apache Bahir and to download the release: > > http://bahir.apache.org > > Thanks, > > The Apache Bahir PMC >
Re: [VOTE] Apache Bahir 2.0.0 (RC1)
Continuing with my earlier mail : Signatures check out +1 for release. If we do cut another RC, would be great to include Prashant's doc changes - but agree that we dont want to block release on that. Regards, Mridul On Tue, Aug 9, 2016 at 9:47 PM, Mridul Muralidharan wrote: > > > On Tuesday, August 9, 2016, Luciano Resende wrote: >> >> On Tuesday, August 9, 2016, Mridul Muralidharan wrote: >> >> > - Built from source successfully. >> > - Tests run successfully. >> > - README.md still has "Coming Soon." for sections 'Online >> > Documentation' and 'A Note About Apache Spark Integration'. >> > - md5 signatures validated - I did not find the key used to sign >> > artifacts, so did not validate that. >> > >> > >> > Queries: >> > >> > a) Do we plan to update README.md before release ? >> >> >> I don't think this is a blocker and we could update in master Patches >> welcome... >> > > Since it is the first release, would be nice if it was reasonably complete. > >> >> b) Where can I get the key used to sign artifacts ? >> >> >> Key is published on public server, i will add a keys file to master as >> well > > > > We can simply add a link to it in the vote mail in future. > > Will update with sig check tomorrow. > > Regards > Mridul > > > >> >> >> > >> > >> > Thanks, >> > Mridul >> > >> > >> > >> > >> > On Tue, Aug 9, 2016 at 11:21 AM, Luciano Resende > > > wrote: >> > > Off course my +1 >> > > >> > > Have tested most of the extensions and samples, focusing on making >> > > sure >> > > MQTT Structured Streaming basic functionality is working. >> > > >> > > On Sat, Aug 6, 2016 at 11:11 AM, Luciano Resende > > > >> > > wrote: >> > > >> > >> >> > >> Please vote to approve the release of the following candidate as >> > >> Apache >> > >> Bahir version 2.0.0 based on Apache Spark 2.0.0. >> > >> >> > >> The tag to be voted on is v2.0.0-rc1 (368c436ae2ad34b3ca64d11801aee6 >> > >> 9e478555f7) >> > >> >> > >> https://github.com/apache/bahir/tree/368c436ae2ad34b3ca64d11801aee6 >> > >> 9e478555f7 >> > >> >> > >> The release files, including signatures, digests, etc. can be found >> > >> at: >> > >> >> > >> >> > >> https://repository.apache.org/content/repositories/orgapachebahir-1001 >> > >> >> > >> The source distribution is also available at: >> > >> >> > >> https://dist.apache.org/repos/dist/dev/bahir/2.0.0-rc1/ >> > >> >> > >> The vote is open for at least 72 hours and passes if a majority of at >> > >> least 3 +1 PMC votes are cast. >> > >> >> > >> [ ] +1 Release this package as Apache Bahir 2.0.0-preview >> > >> [ ] -1 Do not release this package because ... >> > >> >> > >> -- >> > >> Luciano Resende >> > >> http://twitter.com/lresende1975 >> > >> http://lresende.blogspot.com/ >> > >> >> > > >> > > >> > > >> > > -- >> > > Luciano Resende >> > > http://twitter.com/lresende1975 >> > > http://lresende.blogspot.com/ >> > >> >> >> -- >> Sent from my Mobile device
Re: [VOTE] Apache Bahir 2.0.0 (RC1)
On Tuesday, August 9, 2016, Luciano Resende wrote: > On Tuesday, August 9, 2016, Mridul Muralidharan > wrote: > > > - Built from source successfully. > > - Tests run successfully. > > - README.md still has "Coming Soon." for sections 'Online > > Documentation' and 'A Note About Apache Spark Integration'. > > - md5 signatures validated - I did not find the key used to sign > > artifacts, so did not validate that. > > > > > > Queries: > > > > a) Do we plan to update README.md before release ? > > > I don't think this is a blocker and we could update in master Patches > welcome... > > Since it is the first release, would be nice if it was reasonably complete. > b) Where can I get the key used to sign artifacts ? > > > Key is published on public server, i will add a keys file to master as well We can simply add a link to it in the vote mail in future. Will update with sig check tomorrow. Regards Mridul > > > > > > > Thanks, > > Mridul > > > > > > > > > > On Tue, Aug 9, 2016 at 11:21 AM, Luciano Resende > > > wrote: > > > Off course my +1 > > > > > > Have tested most of the extensions and samples, focusing on making sure > > > MQTT Structured Streaming basic functionality is working. > > > > > > On Sat, Aug 6, 2016 at 11:11 AM, Luciano Resende > > > > > > wrote: > > > > > >> > > >> Please vote to approve the release of the following candidate as > Apache > > >> Bahir version 2.0.0 based on Apache Spark 2.0.0. > > >> > > >> The tag to be voted on is v2.0.0-rc1 (368c436ae2ad34b3ca64d11801aee6 > > >> 9e478555f7) > > >> > > >> https://github.com/apache/bahir/tree/368c436ae2ad34b3ca64d11801aee6 > > >> 9e478555f7 > > >> > > >> The release files, including signatures, digests, etc. can be found > at: > > >> > > >> https://repository.apache.org/content/repositories/ > orgapachebahir-1001 > > >> > > >> The source distribution is also available at: > > >> > > >> https://dist.apache.org/repos/dist/dev/bahir/2.0.0-rc1/ > > >> > > >> The vote is open for at least 72 hours and passes if a majority of at > > >> least 3 +1 PMC votes are cast. > > >> > > >> [ ] +1 Release this package as Apache Bahir 2.0.0-preview > > >> [ ] -1 Do not release this package because ... > > >> > > >> -- > > >> Luciano Resende > > >> http://twitter.com/lresende1975 > > >> http://lresende.blogspot.com/ > > >> > > > > > > > > > > > > -- > > > Luciano Resende > > > http://twitter.com/lresende1975 > > > http://lresende.blogspot.com/ > > > > > -- > Sent from my Mobile device >
Re: [VOTE] Apache Bahir 2.0.0 (RC1)
- Built from source successfully. - Tests run successfully. - README.md still has "Coming Soon." for sections 'Online Documentation' and 'A Note About Apache Spark Integration'. - md5 signatures validated - I did not find the key used to sign artifacts, so did not validate that. Queries: a) Do we plan to update README.md before release ? b) Where can I get the key used to sign artifacts ? Thanks, Mridul On Tue, Aug 9, 2016 at 11:21 AM, Luciano Resende wrote: > Off course my +1 > > Have tested most of the extensions and samples, focusing on making sure > MQTT Structured Streaming basic functionality is working. > > On Sat, Aug 6, 2016 at 11:11 AM, Luciano Resende > wrote: > >> >> Please vote to approve the release of the following candidate as Apache >> Bahir version 2.0.0 based on Apache Spark 2.0.0. >> >> The tag to be voted on is v2.0.0-rc1 (368c436ae2ad34b3ca64d11801aee6 >> 9e478555f7) >> >> https://github.com/apache/bahir/tree/368c436ae2ad34b3ca64d11801aee6 >> 9e478555f7 >> >> The release files, including signatures, digests, etc. can be found at: >> >> https://repository.apache.org/content/repositories/orgapachebahir-1001 >> >> The source distribution is also available at: >> >> https://dist.apache.org/repos/dist/dev/bahir/2.0.0-rc1/ >> >> The vote is open for at least 72 hours and passes if a majority of at >> least 3 +1 PMC votes are cast. >> >> [ ] +1 Release this package as Apache Bahir 2.0.0-preview >> [ ] -1 Do not release this package because ... >> >> -- >> Luciano Resende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ >> > > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: Importing source code from Apache Spark
Another alternative, which is what we do internally here, is to have a shim layer in o.a.s namespace : with everything else in our own namespace. The shim will act not just as a means to private api, but also as an abstraction (in theory replaced with different version, impl, etc). Keeping rest of o.a.b code 'clean' ... This of course assumes a reasonable shim can be built. Definitely option two compared to clean separation Regards Mridul On Wednesday, June 1, 2016, Marcelo Vanzin wrote: > On Wed, Jun 1, 2016 at 10:44 AM, Mridul Muralidharan > wrote: > > That would also depend on whether it is possible to move out of o.a.s > > namespace - given the private[spark], etc restriction that scala > > imposes. > > I think Steve did allude to this in his mail. > > I think that should be a (reasonably) short-term goal; that would help > with making extensions compatible with multiple Spark releases, > something that would be harder if they depend on private-ish APIs. >
Re: Importing source code from Apache Spark
That would also depend on whether it is possible to move out of o.a.s namespace - given the private[spark], etc restriction that scala imposes. I think Steve did allude to this in his mail. Assuming that is not an issue (or can be resolved by making appropriate spi visibility changes in apache spark), then I would definitely prefer namespace isolation and move to org.apache.bahir Regards, Mridul On Wed, Jun 1, 2016 at 10:41 AM, Luciano Resende wrote: > Sorry for the misuse of the word "artifacts", I meant to be source, sample > source, and md for docs all under one extension umbrella. > > > > Now, a point Steve brought up on the other thread is related to extensions, > are we going to continue to use the org.apache.spark package or should we > use something different for the extensions we are importing from Apache > Spark ? > > Thoughts ? > > > On Wed, Jun 1, 2016 at 2:21 AM, Steve Loughran wrote: > >> (first post, hope the apache@org email gets in) >> >> two opts spring to mind >> >> -pure source, making a note of origin repo & commit >> -snapshot spark repo, purge most and then move to folders you want >> >> Now, what kind of code layout do we want, so as to encourage a contrib/ >> tree? >> >> >> >> On 1 June 2016 at 07:27, Mridul Muralidharan wrote: >> >> > I agree with importing just the source >> > >> > Regards >> > Mridul >> > >> > On Tuesday, May 31, 2016, Mattmann, Chris A (3980) < >> > chris.a.mattm...@jpl.nasa.gov> wrote: >> > >> > > I think source is fine by me for the first import - is there >> > > a specific reason to have all the artifacts? >> > > >> > > ++ >> > > Chris Mattmann, Ph.D. >> > > Chief Architect >> > > Instrument Software and Science Data Systems Section (398) >> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> > > Office: 168-519, Mailstop: 168-527 >> > > Email: chris.a.mattm...@nasa.gov >> > > WWW: http://sunset.usc.edu/~mattmann/ >> > > ++ >> > > Director, Information Retrieval and Data Science Group (IRDS) >> > > Adjunct Associate Professor, Computer Science Department >> > > University of Southern California, Los Angeles, CA 90089 USA >> > > WWW: http://irds.usc.edu/ >> > > ++ >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > On 5/31/16, 5:42 PM, "Luciano Resende" > > > > wrote: >> > > >> > > >I was thinking about how to import the initial extensions from spark >> and >> > > >had some initial thoughts : >> > > > >> > > >- Import history as much as possible >> > > >- Create a folder structure where all artifacts for a given extension >> > > would >> > > >be in that folder, including source, example, doc, etc >> > > > >> > > >Thoughts ? >> > > > >> > > >Any suggestions for the folder structure ? >> > > > >> > > >-- >> > > >Luciano Resende >> > > >http://twitter.com/lresende1975 >> > > >http://lresende.blogspot.com/ >> > > >> > >> > > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
Re: Importing source code from Apache Spark
I agree with importing just the source Regards Mridul On Tuesday, May 31, 2016, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > I think source is fine by me for the first import - is there > a specific reason to have all the artifacts? > > ++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Director, Information Retrieval and Data Science Group (IRDS) > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > WWW: http://irds.usc.edu/ > ++ > > > > > > > > > > > On 5/31/16, 5:42 PM, "Luciano Resende" > wrote: > > >I was thinking about how to import the initial extensions from spark and > >had some initial thoughts : > > > >- Import history as much as possible > >- Create a folder structure where all artifacts for a given extension > would > >be in that folder, including source, example, doc, etc > > > >Thoughts ? > > > >Any suggestions for the folder structure ? > > > >-- > >Luciano Resende > >http://twitter.com/lresende1975 > >http://lresende.blogspot.com/ >
