Re: [VOTE] Apache Bahir 2.3.3 (RC1)
+1 (binding) Regards JB On 19/05/2019 18:15, Luciano Resende wrote: > Dear community member, > > Please vote to approve the release of Apache Bahir 2.3.3 (RC1) based on > Apache Spark 2.3.3. > > Tag: v2.3.3-rc1 (e29034cad9bec11da1b81324b1f67118772861d2) > > https://github.com/apache/bahir/tree/v2.3.3-rc1 > > Release files: > > https://repository.apache.org/content/repositories/orgapachebahir-1029 > > Source distribution: > > https://dist.apache.org/repos/dist/dev/bahir/bahir-spark/2.3.3-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.3.3 > [ ] -1 Do not release this package because ... > > > Thanks for your vote! > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[jira] [Commented] (BAHIR-183) Using HDFS for saving message for mqtt source
[ https://issues.apache.org/jira/browse/BAHIR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843911#comment-16843911 ] ASF GitHub Bot commented on BAHIR-183: -- Brahim13brahim commented on issue #84: [BAHIR-183] [WIP] HDFS based MQTT client persistence URL: https://github.com/apache/bahir/pull/84#issuecomment-493959752 yes This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Using HDFS for saving message for mqtt source > - > > Key: BAHIR-183 > URL: https://issues.apache.org/jira/browse/BAHIR-183 > Project: Bahir > Issue Type: Improvement > Components: Spark Structured Streaming Connectors >Affects Versions: Spark-2.2.0 >Reporter: Wang Yanlin >Assignee: Wang Yanlin >Priority: Major > Fix For: Spark-2.4.0 > > > Currently in spark-sql-streaming-mqtt, the received mqtt message is saved in > a local file by driver, this will have the risks of losing data for cluster > mode when application master failover occurs. So saving in-coming mqtt > messages using a director in checkpoint will solve this problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Apache Bahir release for the Flink runtime
Ok, if everybody agrees, we can go with 1.8.0 and try to keep it synchronized. As for remaining items, any must-have items before we try a release candidate? On Mon, May 20, 2019 at 12:30 AM Joao Boto wrote: > > if we re going to try to be syncronized with flink version and this could be > important because of Blink (Alibaba fork) integration to Flink > > i think that the next release should be 1.8.0 > > El lun., 20 may. 2019 a las 0:21, Luciano Resende () > escribió: >> >> What should we call the next release then? Just 1.1? 1.5? 2.0? >> >> On Mon, May 20, 2019 at 00:13 Joao Boto wrote: >>> >>> There are a new connectors and some actualizations on previous connectors >>> Because of that I think so. >>> >>> Relatively to synchronization to Flink version, could be interesting but we >>> have to do release more often >>> >>> >>> Joao Boto >>> >>> El dom., 19 may. 2019 a las 23:05, Luciano Resende () >>> escribió: It has been a while since the last Bahir release for the Apache Flink runtime, should we create one? Also, the last release was 1.0, what should we call it now (as Flink is around 1.8)? Any synchronization required/desired? -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/ >> >> -- >> Sent from my Mobile device -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
