[
https://issues.apache.org/jira/browse/APEXMALHAR-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2540.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Serialization exception with throttle example
[
https://issues.apache.org/jira/browse/APEXCORE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh closed APEXCORE-782.
Resolution: Invalid
Can be done without changing the EventInfo.
> Adding analysis to EventInfo
>
[
https://issues.apache.org/jira/browse/APEXCORE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reopened APEXCORE-782:
--
> Adding analysis to EventInfo
>
>
> Key: APEXCORE-782
>
[
https://issues.apache.org/jira/browse/APEXCORE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-781:
Assignee: Chaitanya
> Autometric values of an operator is showing wrongly in App master
> --
[
https://issues.apache.org/jira/browse/APEXCORE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXCORE-743.
--
Resolution: Fixed
Fix Version/s: 3.7.0
> Killed container is shown as running
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-770:
Assignee: Sandesh
> Application getting killed with Null Pointer Exception
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2506:
Description:
Kafka input operator has a separate thread to read from Kafka. Even if the
Kafka
[
https://issues.apache.org/jira/browse/APEXMALHAR-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090913#comment-16090913
]
Sandesh commented on APEXMALHAR-2521:
-
[~ramapv]
Committed offset can be accesse
[
https://issues.apache.org/jira/browse/APEXCORE-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090370#comment-16090370
]
Sandesh commented on APEXCORE-763:
--
[~sanjaypujare] regardless, it should work for dt.a
[
https://issues.apache.org/jira/browse/APEXCORE-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-763:
-
Description:
For one of my applications, I was encountering blocked operator exception.
To avoid this,
[
https://issues.apache.org/jira/browse/APEXCORE-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-763:
-
Description:
For one of my applications, I was encountering blocked operator exception.
To avoid this,
[
https://issues.apache.org/jira/browse/APEXCORE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-761:
Assignee: Sandesh
> Add a utility class/methods to read the system properties
> -
Sandesh created APEXCORE-761:
Summary: Add a utility class/methods to read the system properties
Key: APEXCORE-761
URL: https://issues.apache.org/jira/browse/APEXCORE-761
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXMALHAR-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2518.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Kafka input operator stops reading tuples whe
[
https://issues.apache.org/jira/browse/APEXMALHAR-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2523:
---
Assignee: Venkata Rama Puppala (was: Sandesh)
> In Kafka input operator, use committed(
[
https://issues.apache.org/jira/browse/APEXMALHAR-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2520:
---
Assignee: Venkata Rama Puppala (was: Sandesh)
> Ability to set Kafka Offset Reset Strat
[
https://issues.apache.org/jira/browse/APEXMALHAR-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2521:
---
Assignee: Sandesh
> Expose kafka's committed offset and latest offset in Kafka input ope
[
https://issues.apache.org/jira/browse/APEXMALHAR-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2522:
---
Assignee: Sandesh
> Add support for specifying begin and end offsets for each partitions
[
https://issues.apache.org/jira/browse/APEXMALHAR-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2523:
---
Assignee: Sandesh
> In Kafka input operator, use committed() call instead of depending o
[
https://issues.apache.org/jira/browse/APEXMALHAR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2524:
---
Assignee: Pramod Immaneni
> In kafka input operator commit errors are not handled correc
[
https://issues.apache.org/jira/browse/APEXMALHAR-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2520:
---
Assignee: Sandesh
> Ability to set Kafka Offset Reset Strategy
> --
[
https://issues.apache.org/jira/browse/APEXMALHAR-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2404.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Avro file input operator should call beginWin
[
https://issues.apache.org/jira/browse/APEXMALHAR-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2506:
---
Assignee: Sandesh
> Kafka Input operator - needs better handling of failure of Kafka rea
[
https://issues.apache.org/jira/browse/APEXCORE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-743:
Assignee: Sandesh
> Killed container is shown as running
>
>
Sandesh created APEXMALHAR-2506:
---
Summary: Kafka Input operator - needs better handling of failure
of Kafka reader thread
Key: APEXMALHAR-2506
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2506
Sandesh created APEXCORE-743:
Summary: Killed container is shown as running
Key: APEXCORE-743
URL: https://issues.apache.org/jira/browse/APEXCORE-743
Project: Apache Apex Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/APEXMALHAR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2493.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> KafkaSinglePortExactlyOnceOutputOperator goin
[
https://issues.apache.org/jira/browse/APEXCORE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-631:
Assignee: (was: Sandesh)
> Improving BufferServer tests
>
>
>
[
https://issues.apache.org/jira/browse/APEXCORE-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-633:
Assignee: (was: Sandesh)
> Add unit tests for DataList
> ---
>
>
[
https://issues.apache.org/jira/browse/APEXCORE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-632:
Assignee: (was: Sandesh)
> Fix the existing unit test and move them to JUnit from testNg
> --
[
https://issues.apache.org/jira/browse/APEXCORE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-640:
Assignee: (was: Sandesh)
> BufferServer - purge crashes when the window purged is the last av
[
https://issues.apache.org/jira/browse/APEXCORE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-498:
Assignee: (was: Sandesh)
> Named Checkpoints - Checkpoint the DAG with a name/tag and start t
[
https://issues.apache.org/jira/browse/APEXCORE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-259:
Assignee: (was: Sandesh)
> Use BlockingQueue to pass data to the buffer server
>
[
https://issues.apache.org/jira/browse/APEXCORE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-612:
Assignee: (was: Sandesh)
> Add a logging for out of sequence endWindow tuple
> --
[
https://issues.apache.org/jira/browse/APEXCORE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-258:
Assignee: (was: Sandesh)
> Make buffer server optional and enabled by default
> -
[
https://issues.apache.org/jira/browse/APEXCORE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-613:
Assignee: (was: Sandesh)
> Fix/Remove the LogicalNode's javadoc.
> --
[
https://issues.apache.org/jira/browse/APEXCORE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-588:
Assignee: (was: Sandesh)
> Remove the usage of deprecated Yarn apis (example: AMCommand)
> --
[
https://issues.apache.org/jira/browse/APEXCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-482:
Assignee: (was: Sandesh)
> Default Unifiers should be ThreadLocal with downstream operators
>
[
https://issues.apache.org/jira/browse/APEXCORE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-630:
Assignee: (was: Sandesh)
> Remove FastDataList & related components from BufferServer & Engin
[
https://issues.apache.org/jira/browse/APEXCORE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-584:
Assignee: (was: Sandesh)
> User specified blacklist of nodes for resource allocation
> --
Sandesh created APEXCORE-697:
Summary: Use MiniYARNCluster for unit tests
Key: APEXCORE-697
URL: https://issues.apache.org/jira/browse/APEXCORE-697
Project: Apache Apex Core
Issue Type: Improveme
[
https://issues.apache.org/jira/browse/APEXCORE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-615:
-
Description:
In case of out of sequence tuple, killing the containers will not solve the
problem as con
[
https://issues.apache.org/jira/browse/APEXCORE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-615:
Assignee: (was: Sandesh)
> Out of sequence tuple exception - kill the whole app
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXCORE-663.
--
Resolution: Fixed
Fix Version/s: 3.6.0
> Application restart not working.
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946286#comment-15946286
]
Sandesh commented on APEXCORE-503:
--
[~bhupesh]
Yes, that is the idea. This mechanism sh
[
https://issues.apache.org/jira/browse/APEXCORE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-681:
-
Summary: Enhance the PubSubWebSocketServlet to support more flexible
internal message handlers (was: En
Sandesh created APEXCORE-681:
Summary: Enhance the PubSubWebSocketServlet to more flexible
internal message handlers
Key: APEXCORE-681
URL: https://issues.apache.org/jira/browse/APEXCORE-681
Project: Apac
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2419:
Fix Version/s: 3.7.0
> KafkaSinglePortExactlyOnceOutputOperator fails on recovery
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-676:
-
Description:
Apex CLI shows description for default properties, this feature was added
recently as a pa
[
https://issues.apache.org/jira/browse/APEXCORE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-676:
-
Description:
Apex CLI shows description for default properties, it was fixed recently.
https://issues.ap
Sandesh created APEXCORE-676:
Summary: Show description for DefaultProperties only when user
requests it
Key: APEXCORE-676
URL: https://issues.apache.org/jira/browse/APEXCORE-676
Project: Apache Apex Core
[
https://issues.apache.org/jira/browse/APEXCORE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXCORE-671.
--
Resolution: Fixed
Fix Version/s: 3.6.0
> DTConfiguration utility class ValueEntry access level
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXCORE-592.
--
Resolution: Fixed
Fix Version/s: 3.6.0
> Returning description field in defaultProperties durin
Sandesh created APEXMALHAR-2445:
---
Summary: KafkaExactlyOnce skip writing to wal after recovery if
window id < LargestCompletedWindowId
Key: APEXMALHAR-2445
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2445
[
https://issues.apache.org/jira/browse/APEXMALHAR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2438:
---
Assignee: Avneet Oberoi
> Add Azure Blob Store as a source and Sink
> --
[
https://issues.apache.org/jira/browse/APEXMALHAR-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903661#comment-15903661
]
Sandesh commented on APEXMALHAR-2386:
-
[~avneet15], Welcome to the Apex community
[
https://issues.apache.org/jira/browse/APEXMALHAR-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2386:
---
Assignee: Avneet Oberoi
> KafkaOutput Operator: Expose the must have Kafka Properties as
[
https://issues.apache.org/jira/browse/APEXCORE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-663:
Assignee: Sandesh
> Application restart not working.
>
>
>
Sandesh created APEXMALHAR-2436:
---
Summary: Make fileSystemWal unit tests to use MiniDFSCluster
Key: APEXMALHAR-2436
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2436
Project: Apache Apex Malhar
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2419.
-
Resolution: Done
> KafkaSinglePortExactlyOnceOutputOperator fails on recovery
> -
[
https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2422:
Affects Version/s: 3.7.0
> WindowDataManager not recovering as expected on HDFS
> -
[
https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2422:
Affects Version/s: 3.5.0
3.6.0
> WindowDataManager not recovering as exp
[
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892727#comment-15892727
]
Sandesh commented on APEXCORE-426:
--
Yes, the time required is HEART_BEAT_TIMEOUT
> Su
[
https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2422:
Description:
In WindowDataManager getLargestWindow during recovery is not reflecting the
saved
[
https://issues.apache.org/jira/browse/APEXCORE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891488#comment-15891488
]
Sandesh commented on APEXCORE-426:
--
Adding an answer to the question asked by [~PramodS
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2419:
Description:
The KafkaSinglePortExactlyOnceOutputOperator fails on recovery with the
message:
[
https://issues.apache.org/jira/browse/APEXCORE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXCORE-648.
--
Resolution: Fixed
Fix Version/s: 3.6.0
> Unnecessary byte array copy in DefaultStatefulStreamCo
[
https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2422:
Description:
In WindowDataManager getLargestWindow during recovery is not reflecting the
saved
Sandesh created APEXMALHAR-2422:
---
Summary: WindowDataManager not recovering as expected on HDFS
Key: APEXMALHAR-2422
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2422
Project: Apache Apex Malhar
[
https://issues.apache.org/jira/browse/APEXCORE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-650:
-
Description: ResetWindowTuple raises the complexity of the engine and
development, without much benefit.
Sandesh created APEXCORE-650:
Summary: Remove ResetWindowTuple
Key: APEXCORE-650
URL: https://issues.apache.org/jira/browse/APEXCORE-650
Project: Apache Apex Core
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXMALHAR-2419:
Comment: was deleted
(was: Fix is here, until it is merged.
https://github.com/sandeshh/apex-ma
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878951#comment-15878951
]
Sandesh edited comment on APEXMALHAR-2419 at 2/22/17 6:46 PM:
-
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878951#comment-15878951
]
Sandesh commented on APEXMALHAR-2419:
-
Largest completed window is moving only af
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876656#comment-15876656
]
Sandesh commented on APEXMALHAR-2419:
-
Fix is here, until it is merged.
https://g
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXMALHAR-2419:
---
Assignee: Sandesh
> KafkaSinglePortExactlyOnceOutputOperator fails on recovery
> ---
[
https://issues.apache.org/jira/browse/APEXMALHAR-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876641#comment-15876641
]
Sandesh commented on APEXMALHAR-2419:
-
largestCompletedWindow will be -1, if the
[
https://issues.apache.org/jira/browse/APEXMALHAR-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh closed APEXMALHAR-2410.
---
> KafkaSinglePortExactlyOnceOutputOperator fails if an operator crashes in the
> very first window
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh resolved APEXMALHAR-2410.
-
Resolution: Duplicate
Duplicate of APEXMALHAR-2419
> KafkaSinglePortExactlyOnceOutputOperato
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867108#comment-15867108
]
Sandesh commented on APEXCORE-592:
--
Ok, I am fine with keeping this simple. Why limit i
Sandesh created APEXCORE-647:
Summary: Positive reference count exception during Purge
Key: APEXCORE-647
URL: https://issues.apache.org/jira/browse/APEXCORE-647
Project: Apache Apex Core
Issue Ty
[
https://issues.apache.org/jira/browse/APEXCORE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863044#comment-15863044
]
Sandesh commented on APEXCORE-437:
--
[~dtram] Can you please create this jira in Malhar?
[
https://issues.apache.org/jira/browse/APEXCORE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861984#comment-15861984
]
Sandesh commented on APEXCORE-635:
--
[~brightchen]
What is the overhead of garbage coll
Sandesh created APEXMALHAR-2404:
---
Summary: Avro file input operator should call beginWindow of
AbstractFileInputOperator
Key: APEXMALHAR-2404
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2404
P
[
https://issues.apache.org/jira/browse/APEXCORE-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-633:
-
Component/s: Buffer Server
> Add unit tests for DataList
> ---
>
>
[
https://issues.apache.org/jira/browse/APEXCORE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-632:
-
Component/s: Buffer Server
> Fix the existing unit test and move them to JUnit from testNg
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-613:
-
Component/s: Buffer Server
> Fix/Remove the LogicalNode's javadoc.
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-631:
-
Component/s: Buffer Server
> Improving BufferServer tests
>
>
>
[
https://issues.apache.org/jira/browse/APEXCORE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-438:
Assignee: Sandesh (was: Vlad Rozov)
> ConcurrentModificationException in LogicalNode
> -
[
https://issues.apache.org/jira/browse/APEXCORE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-158:
Assignee: Sandesh (was: Vlad Rozov)
> buffer server tests intermittently fail
>
Sandesh created APEXCORE-643:
Summary: BufferServer - Concurrent Modification Exception during
Subscriber Teardown
Key: APEXCORE-643
URL: https://issues.apache.org/jira/browse/APEXCORE-643
Project: Apache
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855014#comment-15855014
]
Sandesh edited comment on APEXCORE-592 at 2/7/17 12:15 AM:
---
Ha
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855014#comment-15855014
]
Sandesh edited comment on APEXCORE-592 at 2/7/17 12:14 AM:
---
Ha
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855014#comment-15855014
]
Sandesh commented on APEXCORE-592:
--
Have you looked at get-jar-operator-properties & ge
[
https://issues.apache.org/jira/browse/APEXCORE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-592:
Assignee: Ajay Gupta
> Returning description field in defaultProperties during apex cli call
> g
[
https://issues.apache.org/jira/browse/APEXCORE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-640:
-
Summary: BufferServer - purge crashes when the window purged is the last
available (was: BufferServer p
[
https://issues.apache.org/jira/browse/APEXCORE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh reassigned APEXCORE-640:
Assignee: Sandesh
> BufferServer purge crashes when the window purged is the last available
> ---
[
https://issues.apache.org/jira/browse/APEXCORE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-640:
-
Description:
While working on the unit test of BufferServer saw this behavior,
purge on the last windo
[
https://issues.apache.org/jira/browse/APEXCORE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandesh updated APEXCORE-640:
-
Summary: BufferServer purge crashes when the window purged is the last
available (was: BufferServer pur
Sandesh created APEXCORE-640:
Summary: BufferServer purge crashes for when the window purge is
the last available
Key: APEXCORE-640
URL: https://issues.apache.org/jira/browse/APEXCORE-640
Project: Apache
1 - 100 of 249 matches
Mail list logo
