[jira] [Assigned] (FLINK-4084) Add configDir parameter to CliFrontend and flink shell script
[
https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Sella reassigned FLINK-4084:
---
Assignee: (was: Andrea Sella)
> Add configDir parameter to CliFrontend and flink shell script
> -
>
> Key: FLINK-4084
> URL: https://issues.apache.org/jira/browse/FLINK-4084
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment there is no other way than the environment variable
> FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if
> it is started via the flink shell script. In order to improve the user
> exprience, I would propose to introduce a {{--configDir}} parameter which the
> user can use to specify a configuration directory more easily.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (FLINK-6023) Fix Scala snippet into Process Function (Low-level Operations) Doc
[ https://issues.apache.org/jira/browse/FLINK-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Sella reassigned FLINK-6023: --- Assignee: (was: Andrea Sella) > Fix Scala snippet into Process Function (Low-level Operations) Doc > -- > > Key: FLINK-6023 > URL: https://issues.apache.org/jira/browse/FLINK-6023 > Project: Flink > Issue Type: Bug > Components: Documentation >Reporter: Mauro Cortellazzi >Priority: Trivial > Fix For: 1.3.0, 1.2.1 > > > The current `/docs/dev/stream/process_function.md` has some errors in the > Scala snippet -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FLINK-6023) Fix Scala snippet into Process Function (Low-level Operations) Doc
[ https://issues.apache.org/jira/browse/FLINK-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Sella reassigned FLINK-6023: --- Assignee: Andrea Sella > Fix Scala snippet into Process Function (Low-level Operations) Doc > -- > > Key: FLINK-6023 > URL: https://issues.apache.org/jira/browse/FLINK-6023 > Project: Flink > Issue Type: Bug > Components: Documentation >Reporter: Mauro Cortellazzi >Assignee: Andrea Sella >Priority: Trivial > Fix For: 1.3.0, 1.2.1 > > > The current `/docs/dev/stream/process_function.md` has some errors in the > Scala snippet -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FLINK-5885) Java code snippet instead of scala in documentation
[ https://issues.apache.org/jira/browse/FLINK-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Sella reassigned FLINK-5885: --- Assignee: Andrea Sella > Java code snippet instead of scala in documentation > --- > > Key: FLINK-5885 > URL: https://issues.apache.org/jira/browse/FLINK-5885 > Project: Flink > Issue Type: Bug > Components: Cassandra Connector, Documentation >Affects Versions: 1.2.0, 1.3.0 >Reporter: Evgeny Vanslov >Assignee: Andrea Sella >Priority: Trivial > > There is java code snippet instead of scala snippet in code examples on page > https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/connectors/cassandra.html#example -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FLINK-5877) Fix Scala snippet in Async I/O API doc
Andrea Sella created FLINK-5877: --- Summary: Fix Scala snippet in Async I/O API doc Key: FLINK-5877 URL: https://issues.apache.org/jira/browse/FLINK-5877 Project: Flink Issue Type: Improvement Components: Documentation Reporter: Andrea Sella Assignee: Andrea Sella Priority: Minor The current `docs/dev/stream/asyncio.md` has an error in the Scala snippet, it doesn't use the Scala AsyncFunction and the brackets are inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FLINK-4177) CassandraConnectorTest.testCassandraCommitter causing unstable builds
[
https://issues.apache.org/jira/browse/FLINK-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367574#comment-15367574
]
Andrea Sella commented on FLINK-4177:
-
Increasing the timeout should be enough, we can do it adding
`write_request_timeout_in_ms: ` in the
`test/resources/cassandra.yaml`
> CassandraConnectorTest.testCassandraCommitter causing unstable builds
> -
>
> Key: FLINK-4177
> URL: https://issues.apache.org/jira/browse/FLINK-4177
> Project: Flink
> Issue Type: Bug
> Components: Cassandra Connector, Streaming Connectors
>Affects Versions: 1.1.0
>Reporter: Robert Metzger
> Labels: test-stability
>
> This build: https://api.travis-ci.org/jobs/143272982/log.txt?deansi=true
> failed with
> {code}
> 07/08/2016 09:59:12 Job execution switched to status FINISHED.
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 146.646 sec
> <<< FAILURE! - in
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorTest
> testCassandraCommitter(org.apache.flink.streaming.connectors.cassandra.CassandraConnectorTest)
> Time elapsed: 9.057 sec <<< ERROR!
> com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout
> during write query at consistency LOCAL_SERIAL (1 replica were required but
> only 0 acknowledged the write)
> at
> com.datastax.driver.core.exceptions.WriteTimeoutException.copy(WriteTimeoutException.java:73)
> at
> com.datastax.driver.core.exceptions.WriteTimeoutException.copy(WriteTimeoutException.java:26)
> at
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
> at
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
> at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:63)
> at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:39)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraCommitter.open(CassandraCommitter.java:103)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraConnectorTest.testCassandraCommitter(CassandraConnectorTest.java:284)
> Caused by: com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_SERIAL (1 replica
> were required but only 0 acknowledged the write)
> at
> com.datastax.driver.core.exceptions.WriteTimeoutException.copy(WriteTimeoutException.java:100)
> at
> com.datastax.driver.core.Responses$Error.asException(Responses.java:122)
> at
> com.datastax.driver.core.RequestHandler$SpeculativeExecution.onSet(RequestHandler.java:477)
> at
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:1005)
> at
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:928)
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> at
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:618)
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:329)
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:250)
> at
> io.netty.util.concurrent.Sing
[jira] [Created] (FLINK-4119) Null checks in close() for Cassandra Input/Output Formats, checking arguments via Flink Preconditions
Andrea Sella created FLINK-4119: --- Summary: Null checks in close() for Cassandra Input/Output Formats, checking arguments via Flink Preconditions Key: FLINK-4119 URL: https://issues.apache.org/jira/browse/FLINK-4119 Project: Flink Issue Type: Improvement Components: Batch Connectors and Input/Output Formats, Cassandra Connector Reporter: Andrea Sella Assignee: Andrea Sella Priority: Minor Fix For: 1.1.0 Add null checks for session and cluster to align the behaviour with Cassandra Streaming Connector, refactor check arguments using Flink Preconditions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-4084) Add configDir parameter to CliFrontend and flink shell script
[
https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344328#comment-15344328
]
Andrea Sella commented on FLINK-4084:
-
Hi [~mxm], thanks for follow me in this issue.
If FLINK_CONF_DIR was already set, should it be restored after the starting of
CliFrontend?
> Add configDir parameter to CliFrontend and flink shell script
> -
>
> Key: FLINK-4084
> URL: https://issues.apache.org/jira/browse/FLINK-4084
> Project: Flink
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Assignee: Andrea Sella
>Priority: Minor
>
> At the moment there is no other way than the environment variable
> FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if
> it is started via the flink shell script. In order to improve the user
> exprience, I would propose to introduce a {{--configDir}} parameter which the
> user can use to specify a configuration directory more easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FLINK-4097) Cassandra Sink throws NPE on closing if server is not available
[
https://issues.apache.org/jira/browse/FLINK-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Sella reassigned FLINK-4097:
---
Assignee: Andrea Sella
> Cassandra Sink throws NPE on closing if server is not available
> ---
>
> Key: FLINK-4097
> URL: https://issues.apache.org/jira/browse/FLINK-4097
> Project: Flink
> Issue Type: Bug
> Components: Cassandra Connector, Streaming Connectors
>Affects Versions: 1.1.0
>Reporter: Robert Metzger
>Assignee: Andrea Sella
>
> {code}
> 11:41:41,515 ERROR
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase - Error
> while closing session.
> java.lang.NullPointerException
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.close(CassandraSinkBase.java:84)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.closeFunction(FunctionUtils.java:45)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.dispose(AbstractUdfStreamOperator.java:107)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.disposeAllOperators(StreamTask.java:370)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:304)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> {code}
> 11:41:43,896 ERROR org.apache.flink.runtime.taskmanager.Task
>- Task execution failed.
> com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s)
> tried for query failed (tried: /127.0.0.1:9042
> (com.datastax.driver.core.exceptions.TransportException: [/127.0.0.1] Cannot
> connect))
> at
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:231)
> at
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)
> at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1414)
> at com.datastax.driver.core.Cluster.init(Cluster.java:162)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:333)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:308)
> at com.datastax.driver.core.Cluster.connect(Cluster.java:250)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.open(CassandraSinkBase.java:67)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraPojoSink.open(CassandraPojoSink.java:48)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:38)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:91)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:340)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:225)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4097) Cassandra Sink throws NPE on closing if server is not available
[
https://issues.apache.org/jira/browse/FLINK-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342073#comment-15342073
]
Andrea Sella commented on FLINK-4097:
-
In the close() of Sink's lifecycle session should be initialized. So, I think
it is a bit hackish to add a null-check to avoid an unexpected behaviour, I
rather prefer a try-catch.
> Cassandra Sink throws NPE on closing if server is not available
> ---
>
> Key: FLINK-4097
> URL: https://issues.apache.org/jira/browse/FLINK-4097
> Project: Flink
> Issue Type: Bug
> Components: Cassandra Connector, Streaming Connectors
>Affects Versions: 1.1.0
>Reporter: Robert Metzger
>
> {code}
> 11:41:41,515 ERROR
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase - Error
> while closing session.
> java.lang.NullPointerException
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.close(CassandraSinkBase.java:84)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.closeFunction(FunctionUtils.java:45)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.dispose(AbstractUdfStreamOperator.java:107)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.disposeAllOperators(StreamTask.java:370)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:304)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> {code}
> 11:41:43,896 ERROR org.apache.flink.runtime.taskmanager.Task
>- Task execution failed.
> com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s)
> tried for query failed (tried: /127.0.0.1:9042
> (com.datastax.driver.core.exceptions.TransportException: [/127.0.0.1] Cannot
> connect))
> at
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:231)
> at
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)
> at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1414)
> at com.datastax.driver.core.Cluster.init(Cluster.java:162)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:333)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:308)
> at com.datastax.driver.core.Cluster.connect(Cluster.java:250)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.open(CassandraSinkBase.java:67)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraPojoSink.open(CassandraPojoSink.java:48)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:38)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:91)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:340)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:225)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4097) Cassandra Sink throws NPE on closing if server is not available
[
https://issues.apache.org/jira/browse/FLINK-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342042#comment-15342042
]
Andrea Sella commented on FLINK-4097:
-
I am not a huge fan of null-checking in these cases, but it makes sense to
"standardize" the close() as the other connectors. I'll assign the issue to me
and I will add the null-check to session and cluster for CassandraSinkBase.
Should I add the null-check to CassandraTupleWriteAheadSink as well?
> Cassandra Sink throws NPE on closing if server is not available
> ---
>
> Key: FLINK-4097
> URL: https://issues.apache.org/jira/browse/FLINK-4097
> Project: Flink
> Issue Type: Bug
> Components: Cassandra Connector, Streaming Connectors
>Affects Versions: 1.1.0
>Reporter: Robert Metzger
>
> {code}
> 11:41:41,515 ERROR
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase - Error
> while closing session.
> java.lang.NullPointerException
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.close(CassandraSinkBase.java:84)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.closeFunction(FunctionUtils.java:45)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.dispose(AbstractUdfStreamOperator.java:107)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.disposeAllOperators(StreamTask.java:370)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:304)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> {code}
> 11:41:43,896 ERROR org.apache.flink.runtime.taskmanager.Task
>- Task execution failed.
> com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s)
> tried for query failed (tried: /127.0.0.1:9042
> (com.datastax.driver.core.exceptions.TransportException: [/127.0.0.1] Cannot
> connect))
> at
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:231)
> at
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)
> at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1414)
> at com.datastax.driver.core.Cluster.init(Cluster.java:162)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:333)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:308)
> at com.datastax.driver.core.Cluster.connect(Cluster.java:250)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.open(CassandraSinkBase.java:67)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraPojoSink.open(CassandraPojoSink.java:48)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:38)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:91)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:340)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:225)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4097) Cassandra Sink throws NPE on closing if server is not available
[
https://issues.apache.org/jira/browse/FLINK-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342001#comment-15342001
]
Andrea Sella commented on FLINK-4097:
-
I think it is correct to log the NullPointerException. The line throws the
exception is `session.close()`, where session is null due to
NoHostAvailableException, is wrapped inside a try-catch statement to notify
this behaviour.
> Cassandra Sink throws NPE on closing if server is not available
> ---
>
> Key: FLINK-4097
> URL: https://issues.apache.org/jira/browse/FLINK-4097
> Project: Flink
> Issue Type: Bug
> Components: Cassandra Connector, Streaming Connectors
>Affects Versions: 1.1.0
>Reporter: Robert Metzger
>
> {code}
> 11:41:41,515 ERROR
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase - Error
> while closing session.
> java.lang.NullPointerException
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.close(CassandraSinkBase.java:84)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.closeFunction(FunctionUtils.java:45)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.dispose(AbstractUdfStreamOperator.java:107)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.disposeAllOperators(StreamTask.java:370)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:304)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> {code}
> 11:41:43,896 ERROR org.apache.flink.runtime.taskmanager.Task
>- Task execution failed.
> com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s)
> tried for query failed (tried: /127.0.0.1:9042
> (com.datastax.driver.core.exceptions.TransportException: [/127.0.0.1] Cannot
> connect))
> at
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:231)
> at
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)
> at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1414)
> at com.datastax.driver.core.Cluster.init(Cluster.java:162)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:333)
> at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:308)
> at com.datastax.driver.core.Cluster.connect(Cluster.java:250)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraSinkBase.open(CassandraSinkBase.java:67)
> at
> org.apache.flink.streaming.connectors.cassandra.CassandraPojoSink.open(CassandraPojoSink.java:48)
> at
> org.apache.flink.api.common.functions.util.FunctionUtils.openFunction(FunctionUtils.java:38)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.open(AbstractUdfStreamOperator.java:91)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:340)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:225)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:588)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4084) Add configDir parameter to CliFrontend and flink shell script
[
https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341739#comment-15341739
]
Andrea Sella commented on FLINK-4084:
-
Ok, thank you.
> Add configDir parameter to CliFrontend and flink shell script
> -
>
> Key: FLINK-4084
> URL: https://issues.apache.org/jira/browse/FLINK-4084
> Project: Flink
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Assignee: Andrea Sella
>Priority: Minor
>
> At the moment there is no other way than the environment variable
> FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if
> it is started via the flink shell script. In order to improve the user
> exprience, I would propose to introduce a {{--configDir}} parameter which the
> user can use to specify a configuration directory more easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4084) Add configDir parameter to CliFrontend and flink shell script
[
https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341705#comment-15341705
]
Andrea Sella commented on FLINK-4084:
-
Is enough retrieve the new property and set the value as FLINK_CONF_DIR?[1]
[1]https://github.com/alkagin/flink/commit/ddd161f56655f0d79fc809f0ed0a34b8722a6c5b
> Add configDir parameter to CliFrontend and flink shell script
> -
>
> Key: FLINK-4084
> URL: https://issues.apache.org/jira/browse/FLINK-4084
> Project: Flink
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Assignee: Andrea Sella
>Priority: Minor
>
> At the moment there is no other way than the environment variable
> FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if
> it is started via the flink shell script. In order to improve the user
> exprience, I would propose to introduce a {{--configDir}} parameter which the
> user can use to specify a configuration directory more easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-4084) Add configDir parameter to CliFrontend and flink shell script
[
https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339627#comment-15339627
]
Andrea Sella commented on FLINK-4084:
-
If no one is already working on it, I am available to do it.
> Add configDir parameter to CliFrontend and flink shell script
> -
>
> Key: FLINK-4084
> URL: https://issues.apache.org/jira/browse/FLINK-4084
> Project: Flink
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Priority: Minor
>
> At the moment there is no other way than the environment variable
> FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if
> it is started via the flink shell script. In order to improve the user
> exprience, I would propose to introduce a {{--configDir}} parameter which the
> user can use to specify a configuration directory more easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLINK-3774) Flink configuration is not correctly forwarded to PlanExecutor in ScalaShellRemoteEnvironment
[
https://issues.apache.org/jira/browse/FLINK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Sella updated FLINK-3774:
Assignee: Till Rohrmann (was: Andrea Sella)
> Flink configuration is not correctly forwarded to PlanExecutor in
> ScalaShellRemoteEnvironment
> -
>
> Key: FLINK-3774
> URL: https://issues.apache.org/jira/browse/FLINK-3774
> Project: Flink
> Issue Type: Bug
> Components: Scala Shell
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Minor
> Fix For: 1.1.0
>
>
> Currently, the {{ScalaShellRemoteEnvironment}} does not correctly forwards
> the Flink configuration to the {{PlanExecutor}}. Therefore, it is not
> possible to use the Scala shell in combination with an HA cluster which needs
> the configuration parameters set in the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FLINK-3774) Flink configuration is not correctly forwarded to PlanExecutor in ScalaShellRemoteEnvironment
[
https://issues.apache.org/jira/browse/FLINK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Sella reassigned FLINK-3774:
---
Assignee: Andrea Sella
> Flink configuration is not correctly forwarded to PlanExecutor in
> ScalaShellRemoteEnvironment
> -
>
> Key: FLINK-3774
> URL: https://issues.apache.org/jira/browse/FLINK-3774
> Project: Flink
> Issue Type: Bug
> Components: Scala Shell
>Affects Versions: 1.1.0
>Reporter: Till Rohrmann
>Assignee: Andrea Sella
>Priority: Minor
> Fix For: 1.1.0
>
>
> Currently, the {{ScalaShellRemoteEnvironment}} does not correctly forwards
> the Flink configuration to the {{PlanExecutor}}. Therefore, it is not
> possible to use the Scala shell in combination with an HA cluster which needs
> the configuration parameters set in the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140677#comment-15140677 ] Andrea Sella edited comment on FLINK-3311 at 2/10/16 11:49 AM: --- Hi [~rmetzger], Meanwhile [~Zentol] is doing research to achieve an exactly-once implementation, I am glad to submit my connector via PR. Do I have to include OutputFormat/InputFormat to PR? Or do I have to open another Jira Issue related to batch connector? Thx was (Author: alkagin): Hi [~rmetzger], Meanwhile [~Zentol] is doing reasearch to achieve an exactly-once implementation, I am glad to submit my connector via PR. Do I have to include OutputFormat/InputFormat to PR? Or do I have to open another Jira Issue related to batch connector? Thx > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Andrea Sella > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140677#comment-15140677 ] Andrea Sella commented on FLINK-3311: - Hi [~rmetzger], Meanwhile [~Zentol] is doing reasearch to achieve an exactly-once implementation, I am glad to submit my connector via PR. Do I have to include OutputFormat/InputFormat to PR? Or do I have to open another Jira Issue related to batch connector? Thx > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Andrea Sella > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136967#comment-15136967 ] Andrea Sella commented on FLINK-3311: - I agree with [~Zentol]. I can create a new module, which it has flink-batch-connectors as parent, with CassandraOutputFormat and CassandraInputFormat. Is a good approach? > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Andrea Sella > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136816#comment-15136816 ] Andrea Sella edited comment on FLINK-3311 at 2/8/16 11:09 AM: -- Hi, Should I move the flink-connector-cassandra from flink-streaming-connectors to flink-contrib due to the presence of Batch and Stream mode? Thanks, Andrea was (Author: alkagin): Hi, Should move flink-connector-cassandra from flink-streaming-connectors to flink-contrib due to the presence of Batch and Stream mode? Thanks, Andrea > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Andrea Sella > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136816#comment-15136816 ] Andrea Sella commented on FLINK-3311: - Hi, Should move flink-connector-cassandra from flink-streaming-connectors to flink-contrib due to the presence of Batch and Stream mode? Thanks, Andrea > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Andrea Sella > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3332) Provide an exactly-once Cassandra connector
[ https://issues.apache.org/jira/browse/FLINK-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132110#comment-15132110 ] Andrea Sella commented on FLINK-3332: - Hi guys, Do you have something about "exactly once" implementation to study? Other connectors are implemented with this specification? Thanks, Andrea > Provide an exactly-once Cassandra connector > --- > > Key: FLINK-3332 > URL: https://issues.apache.org/jira/browse/FLINK-3332 > Project: Flink > Issue Type: Improvement > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Chesnay Schepler > > With FLINK-3311, we are adding a Cassandra connector to Flink. > It would be good to also provide an "exactly-once" C* connector. > I would like to first discuss how we are going to implement this in Flink. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132074#comment-15132074 ] Andrea Sella commented on FLINK-3311: - Sound good to me, too. > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Chesnay Schepler > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130379#comment-15130379 ] Andrea Sella edited comment on FLINK-3311 at 2/3/16 4:40 PM: - Yes, I can share it. How kind of interface I need to implement to make cassandra sink "exactly once"? Source: https://github.com/radicalbit/flink/tree/cassandra-connector EDIT: source github was (Author: alkagin): Yes, I can share it. How kind of interface I need to implement to make cassandra sink "exactly once"? > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Chesnay Schepler > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130379#comment-15130379 ] Andrea Sella commented on FLINK-3311: - Yes, I can share it. How kind of interface I need to implement to make cassandra sink "exactly once"? > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Chesnay Schepler > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-3311) Add a connector for streaming data into Cassandra
[ https://issues.apache.org/jira/browse/FLINK-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128123#comment-15128123 ] Andrea Sella commented on FLINK-3311: - Hi, I am already working on to cassandra-connector into a private branch and I am using the java drivers. After some internal tests I will glad to submit my solution to the community, I need just a couple of days to finish it. Andrea > Add a connector for streaming data into Cassandra > - > > Key: FLINK-3311 > URL: https://issues.apache.org/jira/browse/FLINK-3311 > Project: Flink > Issue Type: New Feature > Components: Streaming Connectors >Reporter: Robert Metzger >Assignee: Chesnay Schepler > > We had users in the past asking for a Flink+Cassandra integration. > It seems that there is a well-developed java client for connecting into > Cassandra: https://github.com/datastax/java-driver (ASL 2.0) > There are also tutorials out there on how to start a local cassandra instance > (for the tests): > http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html > For the data types, I think we should support TupleX types, and map standard > java types to the respective cassandra types. > In addition, it seems that there is a object mapper from datastax to store > POJOs in Cassandra (there are annotations for defining the primary key and > types) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
