[jira] [Commented] (BAHIR-228) Flink SQL supports kudu sink
[
https://issues.apache.org/jira/browse/BAHIR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166625#comment-17166625
]
João Boto commented on BAHIR-228:
-
closing this as its already merged
> Flink SQL supports kudu sink
>
>
> Key: BAHIR-228
> URL: https://issues.apache.org/jira/browse/BAHIR-228
> Project: Bahir
> Issue Type: New Feature
> Components: Flink Streaming Connectors
>Reporter: dalongliu
>Assignee: dalongliu
>Priority: Major
> Fix For: Flink-Next
>
>
> currently, for Flink-1.10.0, we can use the catalog to store our stream table
> sink for kudu, it should exist a kudu table sink so we can register it to
> catalog, and use kudu as a table in SQL environment.
> we can use kudu table sink like this:
> {code:java}
> KuduOptions options = KuduOptions.builder()
> .setKuduMaster(kuduMaster)
> .setTableName(kuduTable)
> .build();
> KuduWriterOptions writerOptions = KuduWriterOptions.builder()
> .setWriteMode(KuduWriterMode.UPSERT)
> .setFlushMode(FlushMode.AUTO_FLUSH_BACKGROUND)
> .build();
> KuduTableSink tableSink = KuduTableSink.builder()
> .setOptions(options)
> .setWriterOptions(writerOptions)
> .setTableSchema(schema)
> .build();
> tEnv.registerTableSink("kudu", tableSink);
> tEnv.sqlUpdate("insert into kudu select * from source");
> {code}
> I have used kudu table sink to sync data in company's production environment,
> the writing speed at 5w/s in upsert mode
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (BAHIR-228) Flink SQL supports kudu sink
[
https://issues.apache.org/jira/browse/BAHIR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Boto resolved BAHIR-228.
-
Fix Version/s: Flink-Next
Resolution: Done
> Flink SQL supports kudu sink
>
>
> Key: BAHIR-228
> URL: https://issues.apache.org/jira/browse/BAHIR-228
> Project: Bahir
> Issue Type: New Feature
> Components: Flink Streaming Connectors
>Reporter: dalongliu
>Assignee: dalongliu
>Priority: Major
> Fix For: Flink-Next
>
>
> currently, for Flink-1.10.0, we can use the catalog to store our stream table
> sink for kudu, it should exist a kudu table sink so we can register it to
> catalog, and use kudu as a table in SQL environment.
> we can use kudu table sink like this:
> {code:java}
> KuduOptions options = KuduOptions.builder()
> .setKuduMaster(kuduMaster)
> .setTableName(kuduTable)
> .build();
> KuduWriterOptions writerOptions = KuduWriterOptions.builder()
> .setWriteMode(KuduWriterMode.UPSERT)
> .setFlushMode(FlushMode.AUTO_FLUSH_BACKGROUND)
> .build();
> KuduTableSink tableSink = KuduTableSink.builder()
> .setOptions(options)
> .setWriterOptions(writerOptions)
> .setTableSchema(schema)
> .build();
> tEnv.registerTableSink("kudu", tableSink);
> tEnv.sqlUpdate("insert into kudu select * from source");
> {code}
> I have used kudu table sink to sync data in company's production environment,
> the writing speed at 5w/s in upsert mode
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (BAHIR-228) Flink SQL supports kudu sink
[
https://issues.apache.org/jira/browse/BAHIR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Boto reassigned BAHIR-228:
---
Assignee: dalongliu
> Flink SQL supports kudu sink
>
>
> Key: BAHIR-228
> URL: https://issues.apache.org/jira/browse/BAHIR-228
> Project: Bahir
> Issue Type: New Feature
> Components: Flink Streaming Connectors
>Reporter: dalongliu
>Assignee: dalongliu
>Priority: Major
>
> currently, for Flink-1.10.0, we can use the catalog to store our stream table
> sink for kudu, it should exist a kudu table sink so we can register it to
> catalog, and use kudu as a table in SQL environment.
> we can use kudu table sink like this:
> {code:java}
> KuduOptions options = KuduOptions.builder()
> .setKuduMaster(kuduMaster)
> .setTableName(kuduTable)
> .build();
> KuduWriterOptions writerOptions = KuduWriterOptions.builder()
> .setWriteMode(KuduWriterMode.UPSERT)
> .setFlushMode(FlushMode.AUTO_FLUSH_BACKGROUND)
> .build();
> KuduTableSink tableSink = KuduTableSink.builder()
> .setOptions(options)
> .setWriterOptions(writerOptions)
> .setTableSchema(schema)
> .build();
> tEnv.registerTableSink("kudu", tableSink);
> tEnv.sqlUpdate("insert into kudu select * from source");
> {code}
> I have used kudu table sink to sync data in company's production environment,
> the writing speed at 5w/s in upsert mode
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende updated BAHIR-225: -- Fix Version/s: (was: Not Applicable) Flink-Next > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Assignee: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Flink-Next > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende reassigned BAHIR-225: - Assignee: sam lin > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Assignee: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Not Applicable > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende resolved BAHIR-225. --- Resolution: Fixed > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Assignee: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Flink-Next > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende reopened BAHIR-225: --- > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Not Applicable > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] João Boto closed BAHIR-225. --- Resolution: Fixed > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Not Applicable > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BAHIR-225) flink-connector-redis Jedis connect to Redis cluster throws NumberFormatException For input string 112@112
[ https://issues.apache.org/jira/browse/BAHIR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166529#comment-17166529 ] João Boto commented on BAHIR-225: - jedis was updated to 2.9 here > flink-connector-redis Jedis connect to Redis cluster throws > NumberFormatException For input string 112@112 > -- > > Key: BAHIR-225 > URL: https://issues.apache.org/jira/browse/BAHIR-225 > Project: Bahir > Issue Type: Bug > Components: Flink Streaming Connectors >Affects Versions: Flink-1.0 > Environment: mac and Linux, Java8, Flink 1.10 >Reporter: sam lin >Priority: Blocker > Labels: build, jedis, maven > Fix For: Not Applicable > > Original Estimate: 24h > Remaining Estimate: 24h > > There is a bug in Jedis connecting to Redis cluster when using > flink-redis-connector. The maven 1.1.0~1.1.5 > [jar]([https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis]) > all are using Jedis 2.8. After I upgrade Jedis to 2.9, this error is gone. > Please build and push a new version maven Jar with Jedis 2.9 will fix this > issue. > Context: [http://www.programmersought.com/article/589114613/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BAHIR-240) replace docker tests by testcontainer
[ https://issues.apache.org/jira/browse/BAHIR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166508#comment-17166508 ] ASF subversion and git services commented on BAHIR-240: --- Commit 86cce3910bd97fdacd77332c8cfb5db9eb0ebd7b in bahir-flink's branch refs/heads/master from Joao Boto [ https://gitbox.apache.org/repos/asf?p=bahir-flink.git;h=86cce39 ] BAHIR-240: replace docker test by testcontainer (#89) > replace docker tests by testcontainer > - > > Key: BAHIR-240 > URL: https://issues.apache.org/jira/browse/BAHIR-240 > Project: Bahir > Issue Type: Improvement > Components: Flink Streaming Connectors >Reporter: João Boto >Assignee: João Boto >Priority: Major > Fix For: Flink-Next > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (BAHIR-240) replace docker tests by testcontainer
[ https://issues.apache.org/jira/browse/BAHIR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] João Boto resolved BAHIR-240. - Fix Version/s: Flink-Next Resolution: Fixed > replace docker tests by testcontainer > - > > Key: BAHIR-240 > URL: https://issues.apache.org/jira/browse/BAHIR-240 > Project: Bahir > Issue Type: Improvement > Components: Flink Streaming Connectors >Reporter: João Boto >Assignee: João Boto >Priority: Major > Fix For: Flink-Next > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
