[jira] [Created] (APEXMALHAR-2550) NycTaxiDataReader throws exception when encountering lines with unrecognized format in the NYC taxi example

David Yan created APEXMALHAR-2550: - Summary: NycTaxiDataReader throws exception when encountering lines with unrecognized format in the NYC taxi example Key: APEXMALHAR-2550 URL: https://issues.apache.org/jira/bro

[jira] [Created] (APEXMALHAR-2547) Add ride data processing example to Apex Library

David Yan created APEXMALHAR-2547: - Summary: Add ride data processing example to Apex Library Key: APEXMALHAR-2547 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2547 Project: Apache Apex Malhar

[jira] [Created] (APEXMALHAR-2530) Refactor AbstractAppDataSnapshotServer so that subclasses don't need schemas

David Yan created APEXMALHAR-2530: - Summary: Refactor AbstractAppDataSnapshotServer so that subclasses don't need schemas Key: APEXMALHAR-2530 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2530

[jira] [Created] (APEXMALHAR-2529) Allow subclass of AbstractFileInputOperator to control when to advance streaming window

David Yan created APEXMALHAR-2529: - Summary: Allow subclass of AbstractFileInputOperator to control when to advance streaming window Key: APEXMALHAR-2529 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2529

[jira] [Updated] (APEXCORE-768) Upgrade Kryo

[ https://issues.apache.org/jira/browse/APEXCORE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-768: --- Description: Kryo version is pretty old and upgrade will also bring bug fixes. It will require majo

[jira] [Resolved] (APEXMALHAR-2354) Add support for heuristic watermarks in WindowedOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2354. --- Resolution: Fixed Fix Version/s: 3.7.0 > Add support for heuristic watermarks in W

[jira] [Resolved] (APEXCORE-616) Application fails to start Kerberised cluster

[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXCORE-616. Resolution: Fixed Fix Version/s: 3.6.0 > Application fails to start Kerberised cluster > --

[jira] [Created] (APEXCORE-618) ClassNotFoundException thrown when launching app on secure Hadoop

David Yan created APEXCORE-618: -- Summary: ClassNotFoundException thrown when launching app on secure Hadoop Key: APEXCORE-618 URL: https://issues.apache.org/jira/browse/APEXCORE-618 Project: Apache Apex

[jira] [Resolved] (APEXMALHAR-2359) Optimise fire trigger to avoid go through all data

[ https://issues.apache.org/jira/browse/APEXMALHAR-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2359. --- Resolution: Fixed Fix Version/s: 3.7.0 > Optimise fire trigger to avoid go through

[jira] [Resolved] (APEXMALHAR-2301) Implement another TimeBucketAssigner to work with any time

[ https://issues.apache.org/jira/browse/APEXMALHAR-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2301. --- Resolution: Fixed > Implement another TimeBucketAssigner to work with any time >

[jira] [Resolved] (APEXMALHAR-2358) Optimise GenericSerde to use specific serde to improve the performance

[ https://issues.apache.org/jira/browse/APEXMALHAR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2358. --- Resolution: Fixed Fix Version/s: 3.7.0 > Optimise GenericSerde to use specific ser

[jira] [Created] (APEXMALHAR-2385) Idempotency issues in ApexWindowedStreamImpl.java

David Yan created APEXMALHAR-2385: - Summary: Idempotency issues in ApexWindowedStreamImpl.java Key: APEXMALHAR-2385 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2385 Project: Apache Apex Malha

[jira] [Resolved] (APEXMALHAR-2343) Count Accumulation should only increase one for each tuple

[ https://issues.apache.org/jira/browse/APEXMALHAR-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2343. --- Resolution: Fixed Fix Version/s: 3.7.0 > Count Accumulation should only increase o

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729693#comment-15729693 ] David Yan commented on APEXCORE-558: This sounds good to me > Do not use yellow col

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729663#comment-15729663 ] David Yan commented on APEXCORE-558: [~sanjaypujare] I can assure you that there are

[jira] [Commented] (APEXCORE-559) Support quit which should behave the same as "exit"

[ https://issues.apache.org/jira/browse/APEXCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726779#comment-15726779 ] David Yan commented on APEXCORE-559: I don't think this feature is warranted at all.

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726769#comment-15726769 ] David Yan commented on APEXCORE-558: I still think we should not have any color at a

[jira] [Commented] (APEXCORE-558) Do not use yellow color to display command strings in help output

[ https://issues.apache.org/jira/browse/APEXCORE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716923#comment-15716923 ] David Yan commented on APEXCORE-558: We probably should not have any color at all si

[jira] [Created] (APEXCORE-585) Latency should be calculated only after the first window has been complete

David Yan created APEXCORE-585: -- Summary: Latency should be calculated only after the first window has been complete Key: APEXCORE-585 URL: https://issues.apache.org/jira/browse/APEXCORE-585 Project: Apa

[jira] [Commented] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716077#comment-15716077 ] David Yan commented on APEXCORE-581: Yes, I think that makes sense. [~vrozov] though

[jira] [Commented] (APEXMALHAR-2361) Optimise SpillableWindowedKeyedStorage remove(Window) to improve the performance

[ https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710326#comment-15710326 ] David Yan commented on APEXMALHAR-2361: --- I think removing it is better since yo

[jira] [Updated] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-581: --- Description: The behavior should be as follow: - The control tuples should only be sent to downstre

[jira] [Commented] (APEXMALHAR-2361) Optimise SpillableWindowedKeyedStorage remove(Window) to improve the performance

[ https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710301#comment-15710301 ] David Yan commented on APEXMALHAR-2361: --- In that case, for DISCARDING, let's re

[jira] [Moved] (APEXMALHAR-2362) SpillableSetMulitmapImpl.removedSets keeps growing

[ https://issues.apache.org/jira/browse/APEXMALHAR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan moved APEXCORE-582 to APEXMALHAR-2362: Workflow: Default workflow, editable Closed status (was: jira)

[jira] [Created] (APEXCORE-582) SpillableSetMulitmapImpl.removedSets keeps growing

David Yan created APEXCORE-582: -- Summary: SpillableSetMulitmapImpl.removedSets keeps growing Key: APEXCORE-582 URL: https://issues.apache.org/jira/browse/APEXCORE-582 Project: Apache Apex Core I

[jira] [Commented] (APEXMALHAR-2361) Optimise SpillableWindowedKeyedStorage remove(Window) to improve the performance

[ https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710094#comment-15710094 ] David Yan commented on APEXMALHAR-2361: --- It makes sense. This potentially skips

[jira] [Updated] (APEXCORE-581) Delivery of Custom Control Tuples

[ https://issues.apache.org/jira/browse/APEXCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-581: --- Description: The behavior should be as follow: - The control tuples should only be sent to downstr

[jira] [Updated] (APEXCORE-580) Interface for processing and emitting control tuples

[ https://issues.apache.org/jira/browse/APEXCORE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-580: --- Description: DefaultOutputPort needs to have a emitControl method so that operator code can call to

[jira] [Updated] (APEXCORE-580) Interface for processing and emitting control tuples

[ https://issues.apache.org/jira/browse/APEXCORE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-580: --- Summary: Interface for processing and emitting control tuples (was: Add methods for processing and

[jira] [Updated] (APEXCORE-580) Add methods for processing and emitting control tuples

[ https://issues.apache.org/jira/browse/APEXCORE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-580: --- Description: DefaultOutputPort needs to have a emitControl method so that operator code can call to

[jira] [Created] (APEXCORE-581) Delivery of Custom Control Tuples

David Yan created APEXCORE-581: -- Summary: Delivery of Custom Control Tuples Key: APEXCORE-581 URL: https://issues.apache.org/jira/browse/APEXCORE-581 Project: Apache Apex Core Issue Type: Sub-ta

[jira] [Created] (APEXCORE-580) Add methods for processing and emitting control tuples

David Yan created APEXCORE-580: -- Summary: Add methods for processing and emitting control tuples Key: APEXCORE-580 URL: https://issues.apache.org/jira/browse/APEXCORE-580 Project: Apache Apex Core

[jira] [Created] (APEXCORE-579) Custom control tuple support

David Yan created APEXCORE-579: -- Summary: Custom control tuple support Key: APEXCORE-579 URL: https://issues.apache.org/jira/browse/APEXCORE-579 Project: Apache Apex Core Issue Type: New Feature

[jira] [Commented] (APEXCORE-498) Named Checkpoints - Checkpoint the DAG with a name/tag and start the app from that point

[ https://issues.apache.org/jira/browse/APEXCORE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688960#comment-15688960 ] David Yan commented on APEXCORE-498: In addition to this, there are many components

[jira] [Created] (APEXMALHAR-2345) Purge the time buckets from managed state for all time buckets that fall beyond the lateness horizon

David Yan created APEXMALHAR-2345: - Summary: Purge the time buckets from managed state for all time buckets that fall beyond the lateness horizon Key: APEXMALHAR-2345 URL: https://issues.apache.org/jira/browse/APE

[jira] [Commented] (APEXCORE-573) Need to return activation window id for physical operators in StramWebServices

[ https://issues.apache.org/jira/browse/APEXCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668321#comment-15668321 ] David Yan commented on APEXCORE-573: I think it would be better for StramWebServices

[jira] [Commented] (APEXCORE-573) Need to return activation window id for physical operators in StramWebServices

[ https://issues.apache.org/jira/browse/APEXCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667944#comment-15667944 ] David Yan commented on APEXCORE-573: The way to do this is to return the value of th

[jira] [Resolved] (APEXMALHAR-2334) Managed State benchmark: blocked committed window

[ https://issues.apache.org/jira/browse/APEXMALHAR-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2334. --- Resolution: Fixed Fix Version/s: 3.6.0 > Managed State benchmark: blocked committe

[jira] [Resolved] (APEXMALHAR-2333) StateTracker#run throws NoSuchElementException

[ https://issues.apache.org/jira/browse/APEXMALHAR-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2333. --- Resolution: Fixed Fix Version/s: 3.6.0 > StateTracker#run throws NoSuchElementExce

[jira] [Commented] (APEXMALHAR-2335) Problems on StateTracker

[ https://issues.apache.org/jira/browse/APEXMALHAR-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665763#comment-15665763 ] David Yan commented on APEXMALHAR-2335: --- [~brightchen] please have a more descr

[jira] [Resolved] (APEXMALHAR-2338) Couple of links in fsInputOperator.md have a stray # which prevents proper display

[ https://issues.apache.org/jira/browse/APEXMALHAR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2338. --- Resolution: Fixed Assignee: Munagala V. Ramanath Fix Version/s: 3.6.0 > C

[jira] [Updated] (APEXMALHAR-2328) ClassCastException while running TopWikipediaSessions

[ https://issues.apache.org/jira/browse/APEXMALHAR-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2328: -- Assignee: Siyuan Hua > ClassCastException while running TopWikipediaSessions >

[jira] [Resolved] (APEXMALHAR-2329) ManagedState benchmark should not use constant bucket

[ https://issues.apache.org/jira/browse/APEXMALHAR-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2329. --- Resolution: Fixed Fix Version/s: 3.6.0 > ManagedState benchmark should not use con

[jira] [Commented] (APEXMALHAR-2328) ClassCastException while running TopWikipediaSessions

[ https://issues.apache.org/jira/browse/APEXMALHAR-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645753#comment-15645753 ] David Yan commented on APEXMALHAR-2328: --- [~hsy541] can you take a look at this?

[jira] [Resolved] (APEXMALHAR-2327) BucketsFileSystem.writeBucketData() call Slice.toByteArray() cause allocate unnecessary memory

[ https://issues.apache.org/jira/browse/APEXMALHAR-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2327. --- Resolution: Fixed Fix Version/s: 3.6.0 > BucketsFileSystem.writeBucketData() call

[jira] [Resolved] (APEXMALHAR-2320) FSWindowDataManager.toSlice() can cause lots of garbage collection

[ https://issues.apache.org/jira/browse/APEXMALHAR-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2320. --- Resolution: Fixed Fix Version/s: 3.6.0 > FSWindowDataManager.toSlice() can cause l

[jira] [Commented] (APEXMALHAR-2327) BucketsFileSystem.writeBucketData() call Slice.toByteArray() cause allocate unnecessary memory

[ https://issues.apache.org/jira/browse/APEXMALHAR-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634420#comment-15634420 ] David Yan commented on APEXMALHAR-2327: --- Or maybe just add append(Slice key, Sl

[jira] [Commented] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633806#comment-15633806 ] David Yan commented on APEXCORE-561: The finish time is supplied by Yarn's Container

[jira] [Comment Edited] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630848#comment-15630848 ] David Yan edited comment on APEXCORE-570 at 11/2/16 11:11 PM:

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630848#comment-15630848 ] David Yan commented on APEXCORE-570: [~PramodSSImmaneni] Maybe we can't block it but

[jira] [Commented] (APEXCORE-570) Prevent upstream operators from getting too far ahead when downstream operators are slow

[ https://issues.apache.org/jira/browse/APEXCORE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630694#comment-15630694 ] David Yan commented on APEXCORE-570: If the spooling capacity limit is reached, woul

[jira] [Resolved] (APEXMALHAR-2244) Optimize WindowedStorage and Spillable data structures for time series

[ https://issues.apache.org/jira/browse/APEXMALHAR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2244. --- Resolution: Fixed > Optimize WindowedStorage and Spillable data structures for time serie

[jira] [Resolved] (APEXMALHAR-2317) Change SpillableBenchmarkApp to adapt the change on Spillable Data Structure

[ https://issues.apache.org/jira/browse/APEXMALHAR-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2317. --- Resolution: Fixed Fix Version/s: 3.6.0 > Change SpillableBenchmarkApp to adapt the

[jira] [Updated] (APEXMALHAR-2271) Special SpillableSetMultimap> handling in ManagedState in SpillableSessionWindowedStorage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2271: -- Assignee: Siyuan Hua (was: David Yan) > Special SpillableSetMultimap> handling in > Manag

[jira] [Resolved] (APEXCORE-562) RecordingsAgent: returns records for offset beyond number of tuples

[ https://issues.apache.org/jira/browse/APEXCORE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXCORE-562. Resolution: Fixed > RecordingsAgent: returns records for offset beyond number of tuples >

[jira] [Updated] (APEXCORE-562) RecordingsAgent: returns records for offset beyond number of tuples

[ https://issues.apache.org/jira/browse/APEXCORE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-562: --- Fix Version/s: 3.5.0 > RecordingsAgent: returns records for offset beyond number of tuples > ---

[jira] [Resolved] (APEXMALHAR-2307) Session windows are not deleted properly after merge or extend in InMemorySessionWindowedStorage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2307. --- Resolution: Fixed Fix Version/s: 3.6.0 > Session windows are not deleted properly

[jira] [Resolved] (APEXMALHAR-2305) Change implementation of session window to reflect what is described in streaming 102 blog

[ https://issues.apache.org/jira/browse/APEXMALHAR-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2305. --- Resolution: Fixed Fix Version/s: 3.6.0 > Change implementation of session window t

[jira] [Updated] (APEXMALHAR-2307) Session windows are not deleted properly after merge or extend in InMemorySessionWindowedStorage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2307: -- Description: The code does not remove any windows from the keyToWindows map. It should over

[jira] [Created] (APEXMALHAR-2307) Session windows are not deleted properly after merge or extend in InMemorySessionWindowedStorage

David Yan created APEXMALHAR-2307: - Summary: Session windows are not deleted properly after merge or extend in InMemorySessionWindowedStorage Key: APEXMALHAR-2307 URL: https://issues.apache.org/jira/browse/APEXMAL

[jira] [Created] (APEXMALHAR-2305) Change implementation of session window to reflect what is described in streaming 102 blog

David Yan created APEXMALHAR-2305: - Summary: Change implementation of session window to reflect what is described in streaming 102 blog Key: APEXMALHAR-2305 URL: https://issues.apache.org/jira/browse/APEXMALHAR-23

[jira] [Commented] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586503#comment-15586503 ] David Yan commented on APEXCORE-561: This is a good feature to have to diagnostics.

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583417#comment-15583417 ] David Yan commented on APEXMALHAR-2272: --- I think we should change the title of

[jira] [Resolved] (APEXCORE-552) Support application tags when launching application

[ https://issues.apache.org/jira/browse/APEXCORE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXCORE-552. Resolution: Fixed Fix Version/s: 3.5.0 > Support application tags when launching applicatio

[jira] [Commented] (APEXCORE-514) Apache Apex website update

[ https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563884#comment-15563884 ] David Yan commented on APEXCORE-514: The summary looks good to me. > Apache Apex we

[jira] [Commented] (APEXCORE-514) Apache Apex website update

[ https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563106#comment-15563106 ] David Yan commented on APEXCORE-514: 1. Troubleshooting is one word (I also commente

[jira] [Resolved] (APEXCORE-546) Web site: Add use case section to powered by page

[ https://issues.apache.org/jira/browse/APEXCORE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXCORE-546. Resolution: Fixed > Web site: Add use case section to powered by page > --

[jira] [Updated] (APEXCORE-546) Web site: Add use case section to powered by page

[ https://issues.apache.org/jira/browse/APEXCORE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-546: --- Assignee: Thomas Weise > Web site: Add use case section to powered by page > ---

[jira] [Updated] (APEXCORE-379) Latency is stuck when an operator is stuck (before the 1000 window threshold)

[ https://issues.apache.org/jira/browse/APEXCORE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-379: --- Description: When the operator suddenly gets stuck, the latency value will also gets stuck, until i

[jira] [Created] (APEXMALHAR-2282) Document Windowed Operator and Accumulation

David Yan created APEXMALHAR-2282: - Summary: Document Windowed Operator and Accumulation Key: APEXMALHAR-2282 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2282 Project: Apache Apex Malhar

[jira] [Commented] (APEXCORE-552) Support application tags when launching application

[ https://issues.apache.org/jira/browse/APEXCORE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553735#comment-15553735 ] David Yan commented on APEXCORE-552: YARN has a limitation on the length of a tag an

[jira] [Created] (APEXCORE-552) Support application tags when launching application

David Yan created APEXCORE-552: -- Summary: Support application tags when launching application Key: APEXCORE-552 URL: https://issues.apache.org/jira/browse/APEXCORE-552 Project: Apache Apex Core

[jira] [Commented] (APEXMALHAR-2276) ManagedState: value of a key does not get over-written in the same time bucket

[ https://issues.apache.org/jira/browse/APEXMALHAR-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550470#comment-15550470 ] David Yan commented on APEXMALHAR-2276: --- Agreed with [~thw] here. The windowed

[jira] [Resolved] (APEXMALHAR-2280) Add InterfaceStability annotations to all windowed operator related packages

[ https://issues.apache.org/jira/browse/APEXMALHAR-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2280. --- Resolution: Fixed Assignee: David Yan Fix Version/s: 3.6.0 > Add Interfac

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550100#comment-15550100 ] David Yan commented on APEXCORE-548: I actually think we should make that logic part

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550044#comment-15550044 ] David Yan commented on APEXCORE-548: Yes, but it's not that simple. First of all, ge

[jira] [Commented] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550007#comment-15550007 ] David Yan commented on APEXCORE-548: The problem is that ApexCli is using the AppFac

[jira] [Created] (APEXMALHAR-2280) Add InterfaceStability annotations to all windowed operator related packages

David Yan created APEXMALHAR-2280: - Summary: Add InterfaceStability annotations to all windowed operator related packages Key: APEXMALHAR-2280 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2280

[jira] [Updated] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

[ https://issues.apache.org/jira/browse/APEXCORE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXCORE-548: --- Description: ApexCli is incorrectly using the fully qualified class name of the Application class in

[jira] [Created] (APEXCORE-548) ApexCLI does not correctly detect running applications with the same name at launch time

David Yan created APEXCORE-548: -- Summary: ApexCLI does not correctly detect running applications with the same name at launch time Key: APEXCORE-548 URL: https://issues.apache.org/jira/browse/APEXCORE-548

[jira] [Assigned] (APEXCORE-536) Upgrade Hadoop dependency

[ https://issues.apache.org/jira/browse/APEXCORE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan reassigned APEXCORE-536: -- Assignee: David Yan > Upgrade Hadoop dependency > - > >

[jira] [Resolved] (APEXMALHAR-2273) Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is true

[ https://issues.apache.org/jira/browse/APEXMALHAR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2273. --- Resolution: Fixed > Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is

[jira] [Updated] (APEXMALHAR-2273) Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is true

[ https://issues.apache.org/jira/browse/APEXMALHAR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2273: -- Fix Version/s: 3.6.0 > Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is

[jira] [Moved] (APEXCORE-544) Latency values are out of whack immediately after app is launched

[ https://issues.apache.org/jira/browse/APEXCORE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan moved APEXMALHAR-2277 to APEXCORE-544: Workflow: jira (was: Default workflow, editable Closed status)

[jira] [Created] (APEXMALHAR-2277) Latency values are out of whack immediately after app is launched

David Yan created APEXMALHAR-2277: - Summary: Latency values are out of whack immediately after app is launched Key: APEXMALHAR-2277 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2277 Project:

[jira] [Resolved] (APEXMALHAR-2276) ManagedState: value of a key does not get over-written in the same time bucket

[ https://issues.apache.org/jira/browse/APEXMALHAR-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan resolved APEXMALHAR-2276. --- Resolution: Fixed > ManagedState: value of a key does not get over-written in the same ti

[jira] [Updated] (APEXMALHAR-2276) ManagedState: value of a key does not get over-written in the same time bucket

[ https://issues.apache.org/jira/browse/APEXMALHAR-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2276: -- Fix Version/s: 3.6.0 > ManagedState: value of a key does not get over-written in the same t

[jira] [Updated] (APEXMALHAR-2273) Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is true

[ https://issues.apache.org/jira/browse/APEXMALHAR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2273: -- Description: Retraction trigger is fired incorrectly if the retraction value is the same as

[jira] [Updated] (APEXMALHAR-2273) Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is true

[ https://issues.apache.org/jira/browse/APEXMALHAR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2273: -- Summary: Retraction trigger is fired incorrectly when fireOnlyUpdatedPanes is true (was: R

[jira] [Commented] (APEXMALHAR-2276) ManagedTimeUnifiedStateImpl doesn't support time events properly

[ https://issues.apache.org/jira/browse/APEXMALHAR-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536550#comment-15536550 ] David Yan commented on APEXMALHAR-2276: --- [~csingh] Any thoughts? > ManagedTime

[jira] [Updated] (APEXMALHAR-2273) Retraction trigger is fired if the retraction value is the same as the current value and when fireOnlyUpdatedPanes is true

[ https://issues.apache.org/jira/browse/APEXMALHAR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2273: -- Summary: Retraction trigger is fired if the retraction value is the same as the current val

[jira] [Created] (APEXMALHAR-2273) Retraction trigger is fired if the retraction value is the same as the current value and when fireOnlyUpdatedPanes is false

David Yan created APEXMALHAR-2273: - Summary: Retraction trigger is fired if the retraction value is the same as the current value and when fireOnlyUpdatedPanes is false Key: APEXMALHAR-2273 URL: https://issues.apa

[jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected

[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530908#comment-15530908 ] David Yan commented on APEXMALHAR-2272: --- Please fix the spelling in "sequencial

[jira] [Updated] (APEXMALHAR-2267) Remove the word "Byte" in the spillable data structures because it's implied

[ https://issues.apache.org/jira/browse/APEXMALHAR-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2267: -- Description: Spillable means part of the data is on disk and they need to be serialized, an

[jira] [Updated] (APEXMALHAR-2267) Remove the word "Byte" in the spillable data structures because it's implied

[ https://issues.apache.org/jira/browse/APEXMALHAR-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2267: -- Description: Spillable means part of the data is on disk and they need to be serialized, an

[jira] [Updated] (APEXMALHAR-2267) Remove the word "Byte" in the spillable data structures because it's implied

[ https://issues.apache.org/jira/browse/APEXMALHAR-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2267: -- Summary: Remove the word "Byte" in the spillable data structures because it's implied (was

[jira] [Updated] (APEXMALHAR-2271) Special SpillableSetMultimap> handling in ManagedState in SpillableSessionWindowedStorage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated APEXMALHAR-2271: -- Description: The problem with this data structure is that the key is not time based. This p

[jira] [Created] (APEXMALHAR-2271) Special SpillableSetMultimap> handling in ManagedState in SpillableSessionWindowedStorage

David Yan created APEXMALHAR-2271: - Summary: Special SpillableSetMultimap> handling in ManagedState in SpillableSessionWindowedStorage Key: APEXMALHAR-2271 URL: https://issues.apache.org/jira/browse/APEXMALHAR-227

[jira] [Created] (APEXMALHAR-2267) Add documentation about the required properties of the keys in spillable data structures

David Yan created APEXMALHAR-2267: - Summary: Add documentation about the required properties of the keys in spillable data structures Key: APEXMALHAR-2267 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2267

[jira] [Closed] (APEXMALHAR-2231) Implement a Spillable map that takes two keys

[ https://issues.apache.org/jira/browse/APEXMALHAR-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan closed APEXMALHAR-2231. - Assignee: (was: David Yan) > Implement a Spillable map that takes two keys >

  1   2   >