[jira] [Updated] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

2016-08-17 Thread Chaitanya (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya updated APEXCORE-494: --- Fix Version/s: 3.5.0 > Window id of downstream operator is not moving after dynamic partition of >

[jira] [Resolved] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

2016-08-17 Thread Chaitanya (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya resolved APEXCORE-494. Resolution: Fixed > Window id of downstream operator is not moving after dynamic partition of >

[GitHub] apex-core pull request #362: APEXCORE-494 Fixed the dynamic partition issue ...

2016-08-17 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/362 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

2016-08-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425930#comment-15425930 ] ASF GitHub Bot commented on APEXCORE-494: - Github user asfgit closed the pull request at:

[jira] [Commented] (APEXCORE-510) Enforce DefaultOutputPort.emit() or Sink.put() thread affinity

2016-08-17 Thread Sanjay M Pujare (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425917#comment-15425917 ] Sanjay M Pujare commented on APEXCORE-510: -- One way to do this as follows: - In

[jira] [Updated] (APEXMALHAR-2142) High-level API window support

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2142: - Labels: roadmap (was: ) > High-level API window support >

[jira] [Created] (APEXCORE-510) Enforce DefaultOutputPort.emit() or Sink.put() thread affinity

2016-08-17 Thread Vlad Rozov (JIRA)
Vlad Rozov created APEXCORE-510: --- Summary: Enforce DefaultOutputPort.emit() or Sink.put() thread affinity Key: APEXCORE-510 URL: https://issues.apache.org/jira/browse/APEXCORE-510 Project: Apache Apex

[jira] [Updated] (APEXCORE-509) OperatorContext.JVM_OPTIONS should preserve order

2016-08-17 Thread Vlad Rozov (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-509: Labels: newbie (was: ) > OperatorContext.JVM_OPTIONS should preserve order >

Re: Malhar Newbie / Beginner tasks

2016-08-17 Thread Thomas Weise
Hi Brendan, Welcome to the community! I took this as opportunity to put the ticket link onto our community page and also added a few more tickets that I thought would be good fit: https://issues.apache.org/jira/issues/?jql=project%20in%20(APEXCORE%2C%20APEXMALHAR)%20and%20labels%20%3D%20newbie

[jira] [Updated] (APEXCORE-508) Document difference between JVM_OPTIONS and CONTAINER_JVM_OPTIONS

2016-08-17 Thread Vlad Rozov (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-508: Labels: documentation (was: ) > Document difference between JVM_OPTIONS and

[jira] [Created] (APEXCORE-508) Document difference between JVM_OPTIONS and CONTAINER_JVM_OPTIONS

2016-08-17 Thread Vlad Rozov (JIRA)
Vlad Rozov created APEXCORE-508: --- Summary: Document difference between JVM_OPTIONS and CONTAINER_JVM_OPTIONS Key: APEXCORE-508 URL: https://issues.apache.org/jira/browse/APEXCORE-508 Project: Apache

[GitHub] apex-site pull request #47: Add candidate JIRA list link to contributing sec...

2016-08-17 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/apex-site/pull/47 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (APEXCORE-448) Make operator name available in OperatorContext

2016-08-17 Thread Vlad Rozov (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-448. - Resolution: Fixed Fix Version/s: 3.5.0 > Make operator name available in OperatorContext

[jira] [Resolved] (APEXMALHAR-2149) Add unittests for FunctionOperator

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2149. -- Resolution: Fixed > Add unittests for FunctionOperator >

[jira] [Updated] (APEXMALHAR-2162) Enable unit tests of 0.9.0 Kafka Output operator

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2162: - Labels: newbie (was: ) > Enable unit tests of 0.9.0 Kafka Output operator >

[jira] [Updated] (APEXMALHAR-2159) Add Enum Support in CSV Parser

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2159: - Labels: newbie (was: ) > Add Enum Support in CSV Parser >

[jira] [Updated] (APEXMALHAR-2178) Unnecessary byte array copy in KryoSerializableStreamCodec

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2178: - Labels: newbie (was: ) > Unnecessary byte array copy in KryoSerializableStreamCodec

[jira] [Updated] (APEXMALHAR-2175) POJOUtils is considering java reserved words as fields in the expression

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2175: - Labels: newbie (was: ) > POJOUtils is considering java reserved words as fields in

[jira] [Updated] (APEXMALHAR-2173) add a constraint validation for subject in JMSBase

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2173: - Labels: newbie (was: ) > add a constraint validation for subject in JMSBase >

[jira] [Updated] (APEXMALHAR-2183) Add user document for CsvFormatter operator

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2183: - Labels: newbie (was: ) > Add user document for CsvFormatter operator >

[jira] [Updated] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2134: - Labels: newbie (was: ) > Catch NullPointerException if some Kafka partition has no

[jira] [Updated] (APEXMALHAR-2134) Catch NullPointerException if some Kafka partition has no leader broker

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2134: - Assignee: (was: Siyuan Hua) > Catch NullPointerException if some Kafka partition

Re: Malhar 3.5.0 release

2016-08-17 Thread Thomas Weise
Friendly reminder.. There are still a few unresolved tickets for 3.5: https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.5.0%20AND%20project%20%3D%20APEXMALHAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC Please remove the fix version unless you expect to

[jira] [Updated] (APEXMALHAR-2154) Update kafka 0.9 input operator to use new CheckpointNotificationListener

2016-08-17 Thread Siyuan Hua (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2154: --- Fix Version/s: (was: 3.5.0) > Update kafka 0.9 input operator to use new

[jira] [Updated] (APEXMALHAR-2154) Update kafka 0.9 input operator to use new CheckpointNotificationListener

2016-08-17 Thread Siyuan Hua (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2154: --- Assignee: Chaitanya (was: Siyuan Hua) > Update kafka 0.9 input operator to use new

[jira] [Resolved] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2 client

2016-08-17 Thread Thomas Weise (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2135. -- Resolution: Fixed > Upgrade Kafka 0.8 input operator to support 0.8.2 client >

[jira] [Commented] (APEXMALHAR-2182) benchmark for spillable data structure and storage

2016-08-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424947#comment-15424947 ] ASF GitHub Bot commented on APEXMALHAR-2182: Github user brightchen closed the pull

[jira] [Commented] (APEXMALHAR-2182) benchmark for spillable data structure and storage

2016-08-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424948#comment-15424948 ] ASF GitHub Bot commented on APEXMALHAR-2182: GitHub user brightchen reopened a pull

[GitHub] apex-malhar pull request #370: APEXMALHAR-2182 #resolve #comment benchmark f...

2016-08-17 Thread brightchen
GitHub user brightchen reopened a pull request: https://github.com/apache/apex-malhar/pull/370 APEXMALHAR-2182 #resolve #comment benchmark for spillable data struct… …ure and storage You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

2016-08-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424013#comment-15424013 ] ASF GitHub Bot commented on APEXMALHAR-2100: GitHub user chaithu14 reopened a pull

[GitHub] apex-malhar pull request #330: APEXMALHAR-2100 Implementation of Inner Join ...

2016-08-17 Thread chaithu14
GitHub user chaithu14 reopened a pull request: https://github.com/apache/apex-malhar/pull/330 APEXMALHAR-2100 Implementation of Inner Join operator You can merge this pull request into a Git repository by running: $ git pull https://github.com/chaithu14/incubator-apex-malhar

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

2016-08-17 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424008#comment-15424008 ] ASF GitHub Bot commented on APEXMALHAR-2100: Github user chaithu14 closed the pull

[GitHub] apex-malhar pull request #330: APEXMALHAR-2100 Implementation of Inner Join ...

2016-08-17 Thread chaithu14
Github user chaithu14 closed the pull request at: https://github.com/apache/apex-malhar/pull/330 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the