Re: Should Flume integration be behind a profile?

On Mon, Oct 2, 2017 at 12:34 AM, Nick Pentreath wrote: > I'd agree with #1 or #2. Deprecation now seems fine. > > Perhaps this should be raised on the user list also? > > And perhaps it makes sense to look at moving the Flume support into Apache > Bahir if there is

[jira] [Assigned] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Esteban Laver reassigned BAHIR-138: --- Assignee: Esteban Laver > Fix sql-cloudant deprecation messages >

[jira] [Commented] (BAHIR-123) Fix errors to support the latest version of Play JSON library for sql-cloudant

[ https://issues.apache.org/jira/browse/BAHIR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187795#comment-16187795 ] ASF GitHub Bot commented on BAHIR-123: -- Github user ckadner commented on the issue:

[jira] [Commented] (BAHIR-123) Fix errors to support the latest version of Play JSON library for sql-cloudant

[ https://issues.apache.org/jira/browse/BAHIR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187794#comment-16187794 ] ASF GitHub Bot commented on BAHIR-123: -- Github user ckadner commented on the issue:

[jira] [Updated] (BAHIR-130) Support Cloudant Lite Plan

[ https://issues.apache.org/jira/browse/BAHIR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-130: --- Fix Version/s: (was: Spark-2.2.0) Spark-2.2.1 > Support Cloudant Lite

[jira] [Updated] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-138: --- Description: Deprecation warnings in {{DefaultSource}}: {code} [INFO] ---

[jira] [Updated] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-138: --- Description: Deprecation warnings in {{DefaultSource}}: {code} [INFO] ---

[jira] [Updated] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-138: --- Affects Version/s: Spark-2.2.0 > Fix sql-cloudant deprecation messages >

[jira] [Updated] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-138: --- Component/s: Spark Structured Streaming Connectors > Fix sql-cloudant deprecation messages >

[jira] [Updated] (BAHIR-138) Fix sql-cloudant deprecation messages

[ https://issues.apache.org/jira/browse/BAHIR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kadner updated BAHIR-138: --- Labels: warnings (was: ) > Fix sql-cloudant deprecation messages >

Re: Should Flume integration be behind a profile?

CCing user@ Yeah good point about perhaps moving the examples into the module itself. Actually removing it would be a long way off, no matter what. On Mon, Oct 2, 2017 at 8:35 AM Nick Pentreath wrote: > I'd agree with #1 or #2. Deprecation now seems fine. > > Perhaps

Re: Should Flume integration be behind a profile?

I'd agree with #1 or #2. Deprecation now seems fine. Perhaps this should be raised on the user list also? And perhaps it makes sense to look at moving the Flume support into Apache Bahir if there is interest (I've cc'ed Bahir dev list here)? That way the current state of the connector could keep