[jira] [Updated] (SPARK-22956) Union Stream Failover Cause `IllegalStateException`

2018-09-15 Thread Xiao Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/SPARK-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiao Li updated SPARK-22956:

Fix Version/s: (was: 2.4.0)

> Union Stream Failover Cause `IllegalStateException`
> ---
>
> Key: SPARK-22956
> URL: https://issues.apache.org/jira/browse/SPARK-22956
> Project: Spark
>  Issue Type: Bug
>  Components: Structured Streaming
>Affects Versions: 2.1.0
>Reporter: Li Yuanjian
>Assignee: Li Yuanjian
>Priority: Major
> Fix For: 2.3.0
>
>
> When we union 2 streams from kafka or other sources, while one of them have 
> no continues data coming and in the same time task restart, this will cause 
> an `IllegalStateException`. This mainly cause because the code in 
> [MicroBatchExecution|https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/MicroBatchExecution.scala#L190]
>   , while one stream has no continues data, its comittedOffset same with 
> availableOffset during `populateStartOffsets`, and `currentPartitionOffsets` 
> not properly handled in KafkaSource. Also, maybe we should also consider this 
> scenario in other Source.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Updated] (SPARK-22956) Union Stream Failover Cause `IllegalStateException`

2018-02-22 Thread Xiao Li (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiao Li updated SPARK-22956:

Fix Version/s: (was: 2.3.1)
   2.3.0

> Union Stream Failover Cause `IllegalStateException`
> ---
>
> Key: SPARK-22956
> URL: https://issues.apache.org/jira/browse/SPARK-22956
> Project: Spark
>  Issue Type: Bug
>  Components: Structured Streaming
>Affects Versions: 2.1.0
>Reporter: Li Yuanjian
>Assignee: Li Yuanjian
>Priority: Major
> Fix For: 2.3.0, 2.4.0
>
>
> When we union 2 streams from kafka or other sources, while one of them have 
> no continues data coming and in the same time task restart, this will cause 
> an `IllegalStateException`. This mainly cause because the code in 
> [MicroBatchExecution|https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/MicroBatchExecution.scala#L190]
>   , while one stream has no continues data, its comittedOffset same with 
> availableOffset during `populateStartOffsets`, and `currentPartitionOffsets` 
> not properly handled in KafkaSource. Also, maybe we should also consider this 
> scenario in other Source.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Updated] (SPARK-22956) Union Stream Failover Cause `IllegalStateException`

2018-01-15 Thread Shixiong Zhu (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shixiong Zhu updated SPARK-22956:
-
Fix Version/s: (was: 2.3.0)
   2.4.0
   2.3.1

> Union Stream Failover Cause `IllegalStateException`
> ---
>
> Key: SPARK-22956
> URL: https://issues.apache.org/jira/browse/SPARK-22956
> Project: Spark
>  Issue Type: Bug
>  Components: Structured Streaming
>Affects Versions: 2.1.0
>Reporter: Li Yuanjian
>Assignee: Li Yuanjian
>Priority: Major
> Fix For: 2.3.1, 2.4.0
>
>
> When we union 2 streams from kafka or other sources, while one of them have 
> no continues data coming and in the same time task restart, this will cause 
> an `IllegalStateException`. This mainly cause because the code in 
> [MicroBatchExecution|https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/MicroBatchExecution.scala#L190]
>   , while one stream has no continues data, its comittedOffset same with 
> availableOffset during `populateStartOffsets`, and `currentPartitionOffsets` 
> not properly handled in KafkaSource. Also, maybe we should also consider this 
> scenario in other Source.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org