[jira] [Commented] (BAHIR-155) Add expire to redis sink

2019-09-27 Thread Jira
[ https://issues.apache.org/jira/browse/BAHIR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939522#comment-16939522 ] Gustavo Momenté commented on BAHIR-155: --- Anyone working on this?  > Add expire to r

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
Any update on this? Are snapshot published anywhere? I'm interested in using Apache Bahir right now, but can't figure where snapshots are published. On 2019/05/20 07:41:24, Luciano Resende wrote: > Ok, if everybody agrees, we can go with 1.8.0 and try to keep it synchronized.> > > As for remainin

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Luciano Resende
I just started publishing a snapshot based on latest master. It will be available shortly from : https://repository.apache.org/content/groups/snapshots/ On Fri, Sep 27, 2019 at 8:51 AM Gustavo Momenté wrote: > > Any update on this? Are snapshot published anywhere? I'm interested in > using Apac

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
Thanks a lot, that will be really helpful. Do think it would be possible to also publish older versions for flink 1.8.x? On Fri, Sep 27, 2019, 13:03 Luciano Resende wrote: > I just started publishing a snapshot based on latest master. > > It will be available shortly from : > https://repository

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Luciano Resende
I don't think it's easy to get multiple snapshots for same artifact name/version. Are you having compatibility issues ? Or Do you have issues building these locally with the required updates? On Fri, Sep 27, 2019 at 9:22 AM Gustavo Momenté wrote: > > Thanks a lot, that will be really helpful. Do

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
> > I don't think it's easy to get multiple snapshots for same artifact > name/version. I agree with you, I think right now the best solution for my use case (I can't upgrade to Flink 1.9.0 yet) is to release the old versions in an internal maven repository. I'm not having issues build locally,