Hello Bahir community,
The Apache Flink community is currently discussing how to handle incoming
(streaming) connector contributions [1].
The Flink community wants to limit the maintained connectors to the most
popular ones, but we don't want to reject valuable code contributions
without offering
I can see benefits from this —provided we get some help from the Flink
people in maintaining and testing the stuff.
On 11 August 2016 at 10:54, Robert Metzger wrote:
> Hello Bahir community,
>
> The Apache Flink community is currently discussing how to handle incoming
> (streaming) connector con
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416952#comment-15416952
]
Prashant Sharma commented on BAHIR-51:
--
QoS is set on message, when it is published. Th
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416966#comment-15416966
]
Sebastian Woehrl commented on BAHIR-51:
---
QoS can also be set when subscribing to a top
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416979#comment-15416979
]
Prashant Sharma commented on BAHIR-51:
--
Thank you !, It was my oversight.
> Add additi
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416981#comment-15416981
]
Prashant Sharma commented on BAHIR-51:
--
I was preparing a PR for MqttStreamSource with
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/bahir/pull/22
[BAHIR-51] MqttStreamSource supports a few important MqttConnectOptions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/bahir BAHIR
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416990#comment-15416990
]
ASF GitHub Bot commented on BAHIR-51:
-
GitHub user ScrapCodes opened a pull request:
On Thu, Aug 11, 2016 at 2:04 AM, Steve Loughran wrote:
> I can see benefits from this —provided we get some help from the Flink
> people in maintaining and testing the stuff.
>
+1, Let me know when you guys are ready and I can create a bahir-flink git
repository.
--
Luciano Resende
http://twi
@Steve: The plan is that Flink committers also help out here with
reviewing, releasing and other community activities (but I suspect the
activity will be much lower, otherwise, we would not be discussing removing
some of the connectors from Flink)
@Luciano: So the idea is to have separate reposito
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417334#comment-15417334
]
ASF GitHub Bot commented on BAHIR-51:
-
Github user swoehrl-mw commented on the issue:
Github user swoehrl-mw commented on the issue:
https://github.com/apache/bahir/pull/22
Change looks good to me. It adds all the important mqtt options and uses
sensible defaults.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
On Thu, Aug 11, 2016 at 5:42 AM, Robert Metzger wrote:
>
>
> @Luciano: So the idea is to have separate repositories for each project
> contributing connectors?
> I'm wondering if it makes sense to keep the code in the same repository to
> have some synergies (like the release scripts, CI, documen
On Sat, Aug 6, 2016 at 3: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/apa
Having Flink connectors in the same repo seems to make more sense at the
moment.
Certain artifacts can be shared between the two types of connectors.
Flink seems to have more frequent releases recently. But Bahir doesn't have
to follow each Flink patch release.
Just my two cents.
On Thu, Aug 11
Thank you for your responses.
@Luciano: I don't have a strong preference for one of the two options, but
I would like to understand the implications of the two before we start
setting up the infrastructure.
Regarding the release cycle: For the Flink connectors, I would actually try
to make the rel
Github user ScrapCodes commented on the issue:
https://github.com/apache/bahir/pull/22
Thanks @swoehrl-mw, @lresende Please take a look !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
[
https://issues.apache.org/jira/browse/BAHIR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418377#comment-15418377
]
ASF GitHub Bot commented on BAHIR-51:
-
Github user ScrapCodes commented on the issue:
18 matches
Mail list logo
