[jira] [Created] (APEXMALHAR-2363) Kafka input operator needs a force exit in case it can't recover from application offsets

Siyuan Hua created APEXMALHAR-2363: -- Summary: Kafka input operator needs a force exit in case it can't recover from application offsets Key: APEXMALHAR-2363 URL: https://issues.apache.org/jira/browse/APEXM

Re: [VOTE] Apache Apex Malhar Release 3.6.0 (RC1)

+1 Verified checksums Verified compilation Verified build and test Verified pi demo On Wed, Nov 30, 2016 at 9:50 AM, Tushar Gosavi wrote: > +1 > > Verified checksums > Verified compilation > > - Tushar. > > > On Wed, Nov 30, 2016 at 7:43 PM, Thomas Weise wrote: > > Can folks please verify the

Re: Malhar release 3.6

gt;> Hi Thomas, > > > >> > > > >>I am working on APEXMALHAR-2284 and will open a PR in couple of > > days. > > > >> > > > >> Regards, > > > >> Chaitanya > > > >> > > > >> On Sun, Nov 6, 2016 at 10:51 PM, Thomas Weise

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15682657#comment-15682657 ] Siyuan Hua commented on APEXMALHAR-2301: Ok, there are couple things

Re: [DISCUSSION] Custom Control Tuples

I will vote for approach 1. First of all that one sounds easier to do to me. And I think idempotency is important. It may run at the cost of higher latency but I think it is ok And in addition, when in the future if users do need realtime control tuple processing, we can always add the option on

Re: Malhar release 3.6

+1 Thanks！ Sent from my iPhone > On Oct 26, 2016, at 13:11, Thomas Weise wrote: > > Hi, > > I'm proposing another release of Malhar in November. There are 49 issues > marked for the release, including important bug fixes, new documentation, > SQL support and the work for windowed operator sta

[jira] [Updated] (APEXMALHAR-2203) Control tuple port and watermark support in high-level API (version 1)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2203: --- Summary: Control tuple port and watermark support in high-level API (version 1) (was

[jira] [Commented] (APEXMALHAR-2203) Control tuple port and watermark support in high-level API (version 1)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592494#comment-15592494 ] Siyuan Hua commented on APEXMALHAR-2203: Support _single_ control tuple

Make cli support high-level API and SQL

Given we already have first version of high-level API and SQL PR is getting close to be merged. And also we have ability to launch application grammatically. I think it's nice to have our cli support both high-level API and SQL directly so people can simply prototype what they need and/or try out A

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

Siyuan Hua created APEXMALHAR-2301: -- Summary: Implement another TimeBucketAssigner to work with any time Key: APEXMALHAR-2301 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2301 Project

[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573091#comment-15573091 ] Siyuan Hua commented on APEXMALHAR-2220: [~d9liang] The malhar-lib

[jira] [Commented] (APEXMALHAR-2283) Refactor kafka output operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569248#comment-15569248 ] Siyuan Hua commented on APEXMALHAR-2283: There are couple of solution

[jira] [Created] (APEXMALHAR-2283) Refactor kafka output operator

Siyuan Hua created APEXMALHAR-2283: -- Summary: Refactor kafka output operator Key: APEXMALHAR-2283 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2283 Project: Apache Apex Malhar

[jira] [Updated] (APEXMALHAR-2283) Refactor kafka output operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2283: --- Assignee: Siyuan Hua > Refactor kafka output opera

[jira] [Updated] (APEXMALHAR-2283) Refactor kafka output operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2283: --- Description: The abstract kafka output operator needs to be refactored 1. Needs to set

Many FileSplitterInputTest.testRecoveryOfPartialFile test failures

There are many com.datatorrent.lib.io.fs.FileSplitterInputTest. testRecoveryOfPartialFile test failures in Jenkins CI build.

[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=15546598#comment-15546598 ] Siyuan Hua commented on APEXMALHAR-2276: Time will be mapped to a

Re: [VOTE] Hadoop upgrade

+1 for 2.6.x On Mon, Oct 3, 2016 at 3:41 PM, Pramod Immaneni wrote: > +1 for 2.6.x > > On Mon, Oct 3, 2016 at 1:47 PM, David Yan wrote: > > > Hi all, > > > > Thomas created this ticket for upgrading our Hadoop dependency version a > > couple weeks ago: > > > > https://issues.apache.org/jira/bro

[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543057#comment-15543057 ] Siyuan Hua commented on APEXMALHAR-2220: Sorry, I

[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542972#comment-15542972 ] Siyuan Hua commented on APEXMALHAR-2220: Maybe call

[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=15536587#comment-15536587 ] Siyuan Hua commented on APEXMALHAR-2276: The problem is in the DefaultBu

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2276: --- Issue Type: Sub-task (was: Bug) Parent: APEXMALHAR-2130

[jira] [Created] (APEXMALHAR-2275) ManagedTimeUnifiedStateImpl doesn't support time events properly

Siyuan Hua created APEXMALHAR-2275: -- Summary: ManagedTimeUnifiedStateImpl doesn't support time events properly Key: APEXMALHAR-2275 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2275 Pr

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

Siyuan Hua created APEXMALHAR-2276: -- Summary: ManagedTimeUnifiedStateImpl doesn't support time events properly Key: APEXMALHAR-2276 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2276 Pr

[jira] [Resolved] (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 ] Siyuan Hua resolved APEXMALHAR-2267. Resolution: Fixed > Remove the word "Byte" in the spillable data struc

[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 ] Siyuan Hua updated APEXMALHAR-2267: --- Fix Version/s: 3.6.0 > Remove the word "Byte" in the spillable data struc

[jira] [Resolved] (APEXMALHAR-2130) Scalable windowed storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2130. Resolution: Fixed > Scalable windowed stor

[jira] [Reopened] (APEXMALHAR-2130) Scalable windowed storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua reopened APEXMALHAR-2130: > Scalable windowed storage > - > >

[jira] [Updated] (APEXMALHAR-2130) Scalable windowed storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2130: --- Fix Version/s: 3.6.0 > Scalable windowed stor

[jira] [Commented] (APEXMALHAR-2230) Intermittent test failure in Kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526808#comment-15526808 ] Siyuan Hua commented on APEXMALHAR-2230: Another test failure that coul

[jira] [Resolved] (APEXMALHAR-2248) Create SpillableSet and SpillableSetMultimap interfaces and implementation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2248. Resolution: Fixed > Create SpillableSet and SpillableSetMultimap interfaces

[jira] [Updated] (APEXMALHAR-2248) Create SpillableSet and SpillableSetMultimap interfaces and implementation

[ https://issues.apache.org/jira/browse/APEXMALHAR-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2248: --- Fix Version/s: 3.6.0 > Create SpillableSet and SpillableSetMultimap interfaces

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15513770#comment-15513770 ] Siyuan Hua commented on APEXMALHAR-2244: Each spillable DS implementa

[jira] [Updated] (APEXMALHAR-2253) Iterator for spillable data structure should throw ConcurrentModificationException during the iteration

[ https://issues.apache.org/jira/browse/APEXMALHAR-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2253: --- Assignee: David Yan > Iterator for spillable data structure should th

[jira] [Created] (APEXMALHAR-2253) Iterator for spillable data structure should throw ConcurrentModificationException during the iteration

Siyuan Hua created APEXMALHAR-2253: -- Summary: Iterator for spillable data structure should throw ConcurrentModificationException during the iteration Key: APEXMALHAR-2253 URL: https://issues.apache.org/jira

[jira] [Commented] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496632#comment-15496632 ] Siyuan Hua commented on APEXMALHAR-2241: Hey [~Venkatesh Kottapalli] W

[jira] [Created] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

Siyuan Hua created APEXMALHAR-2241: -- Summary: The metadata kafka consumer should also pickup the properties setting on the kafka input operator. Key: APEXMALHAR-2241 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (APEXMALHAR-2241) The metadata kafka consumer should also pickup the properties setting on the kafka input operator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2241: --- Assignee: Venkatesh Kottapalli > The metadata kafka consumer should also pickup

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

[ https://issues.apache.org/jira/browse/APEXCORE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493629#comment-15493629 ] Siyuan Hua commented on APEXCORE-536: - So can we add anything that is new after

[jira] [Commented] (APEXMALHAR-2230) Intermittent test failure in Kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491639#comment-15491639 ] Siyuan Hua commented on APEXMALHAR-2230: Good news is this time we ca

[jira] [Commented] (APEXMALHAR-2230) Intermittent test failure in Kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491628#comment-15491628 ] Siyuan Hua commented on APEXMALHAR-2230: The code looks impossibl

[jira] [Created] (APEXCORE-529) Support annotation to automate lifecycle callbacks like setup() teardown() etc

Siyuan Hua created APEXCORE-529: --- Summary: Support annotation to automate lifecycle callbacks like setup() teardown() etc Key: APEXCORE-529 URL: https://issues.apache.org/jira/browse/APEXCORE-529

Re: [ANNOUNCE] New Apache Apex PMC Member: Chandni Singh

Congrats Chandni! Regards, Siyuan On Mon, Sep 12, 2016 at 9:33 AM, Thomas Weise wrote: > The Apache Apex PMC is pleased to announce that Chandni Singh is now a PMC > member. We appreciate all her contributions to the project so far, and are > looking forward to more. > > Congrats Chandni! > Tho

[jira] [Commented] (APEXMALHAR-2230) Intermittent test failure in Kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474990#comment-15474990 ] Siyuan Hua commented on APEXMALHAR-2230: Not necessarily related to K

[jira] [Assigned] (APEXMALHAR-2230) Intermittent test failure in Kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua reassigned APEXMALHAR-2230: -- Assignee: Siyuan Hua > Intermittent test failure in Kafka mod

[jira] [Commented] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468074#comment-15468074 ] Siyuan Hua commented on APEXMALHAR-2220: [~d9liang] The function opera

[jira] [Updated] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2220: --- Assignee: Dongming Liang (was: Siyuan Hua) > Move the FunctionOperator to Mal

[jira] [Created] (APEXMALHAR-2220) Move the FunctionOperator to Malhar library

Siyuan Hua created APEXMALHAR-2220: -- Summary: Move the FunctionOperator to Malhar library Key: APEXMALHAR-2220 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2220 Project: Apache Apex Malhar

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2142: --- Attachment: Java-High-level-API-Siyuan.pdf Apache Beam AutoComplete

[jira] [Updated] (APEXMALHAR-1939) Stream API

[ https://issues.apache.org/jira/browse/APEXMALHAR-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-1939: --- Attachment: Java-High-level-API-Siyuan.pdf Apache Beam AutoComplete

[jira] [Created] (APEXMALHAR-2217) Remove some redundant code in WindowedStorage and WindowedKeyedStorage

Siyuan Hua created APEXMALHAR-2217: -- Summary: Remove some redundant code in WindowedStorage and WindowedKeyedStorage Key: APEXMALHAR-2217 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2217

Re: [VOTE] Apache Apex Malhar Release 3.5.0 (RC2)

+1 File integrity check Build and license check Pi-demo for 10min All above look good Thanks, Siyuan On Tue, Aug 30, 2016 at 11:37 PM, Thomas Weise wrote: > Dear Community, > > Please vote on the following Apache Apex Malhar 3.5.0 release candidate. > > RC2 fixes the copyright related issues wi

Re: [VOTE] Apache Apex Malhar Release 3.5.0 (RC1)

+1 Checked for - File integration - Source code verification - Check for compilation and license - Run pi demo for 10 min On Sun, Aug 28, 2016 at 9:59 PM, Thomas Weise wrote: > Dear Community, > > Please vote on the following Apache Apex Malhar 3.5.0 release candidate. > > This is a source rel

[jira] [Updated] (APEXMALHAR-2214) Use tuple internally so it can carry over the window semantics

[ https://issues.apache.org/jira/browse/APEXMALHAR-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2214: --- Assignee: Siyuan Hua > Use tuple internally so it can carry over the window semant

[jira] [Created] (APEXMALHAR-2214) Use tuple internally so it can carry over the window semantics

Siyuan Hua created APEXMALHAR-2214: -- Summary: Use tuple internally so it can carry over the window semantics Key: APEXMALHAR-2214 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2214 Project

[jira] [Created] (APEXMALHAR-2213) Refactor Stream API to make it easier to specify keys for keyed transformation

Siyuan Hua created APEXMALHAR-2213: -- Summary: Refactor Stream API to make it easier to specify keys for keyed transformation Key: APEXMALHAR-2213 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2213

[jira] [Created] (APEXMALHAR-2212) Tuple codec to make application build by High-level api more efficient

Siyuan Hua created APEXMALHAR-2212: -- Summary: Tuple codec to make application build by High-level api more efficient Key: APEXMALHAR-2212 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2212

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua closed APEXMALHAR-2134. -- Resolution: Fixed > Catch NullPointerException if some Kafka partition has no lea

[jira] [Created] (APEXMALHAR-2208) High-level API beam examples

Siyuan Hua created APEXMALHAR-2208: -- Summary: High-level API beam examples Key: APEXMALHAR-2208 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2208 Project: Apache Apex Malhar Issue

[jira] [Closed] (APEXMALHAR-2208) High-level API beam examples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua closed APEXMALHAR-2208. -- Resolution: Fixed > High-level API beam examp

[jira] [Updated] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2199: --- Affects Version/s: (was: 3.4.0) > 0.8 kafka input operator doesn't suppor

[jira] [Updated] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2199: --- Assignee: Siyuan Hua (was: Chaitanya) > 0.8 kafka input operator doesn't suppor

[jira] [Created] (APEXMALHAR-2203) Control tuple port and watermark support in high-level API

Siyuan Hua created APEXMALHAR-2203: -- Summary: Control tuple port and watermark support in high-level API Key: APEXMALHAR-2203 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2203 Project

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437102#comment-15437102 ] Siyuan Hua commented on APEXMALHAR-2154: I don't think so >

[jira] [Commented] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435402#comment-15435402 ] Siyuan Hua commented on APEXMALHAR-2199: 0.9 operator should not have

[jira] [Commented] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435399#comment-15435399 ] Siyuan Hua commented on APEXMALHAR-2199: [~chaithu] Can you please ta

[jira] [Updated] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2199: --- Affects Version/s: 3.5.0 3.4.0 > 0.8 kafka input operator does

[jira] [Created] (APEXMALHAR-2199) 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support)

Siyuan Hua created APEXMALHAR-2199: -- Summary: 0.8 kafka input operator doesn't support chroot zookeeper path (multitenant kafka support) Key: APEXMALHAR-2199 URL: https://issues.apache.org/jira/browse/APEXM

[jira] [Updated] (APEXMALHAR-2180) KafkaInput Operator partitions has to be unchanged in case of dynamic scaling of ONE_TO_MANY strategy.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2180: --- Fix Version/s: 3.5.0 > KafkaInput Operator partitions has to be unchanged in case

[jira] [Resolved] (APEXMALHAR-2180) KafkaInput Operator partitions has to be unchanged in case of dynamic scaling of ONE_TO_MANY strategy.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2180. Resolution: Fixed > KafkaInput Operator partitions has to be unchanged in case

[jira] [Resolved] (APEXMALHAR-2169) KafkaInputoperator: Remove the stuff related to Partition Based on throughput.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2169. Resolution: Fixed > KafkaInputoperator: Remove the stuff related to Partition Based

[jira] [Updated] (APEXMALHAR-2169) KafkaInputoperator: Remove the stuff related to Partition Based on throughput.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2169: --- Fix Version/s: 3.5.0 > KafkaInputoperator: Remove the stuff related to Partition Ba

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

[ 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: 3.5.0 > Update kafka 0.9 input operator to use

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2154. Resolution: Fixed > Update kafka 0.9 input operator to use

[jira] [Updated] (APEXMALHAR-2168) The setter method for double field is not generated correctly in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2168: --- Summary: The setter method for double field is not generated correctly in

[jira] [Updated] (APEXMALHAR-2168) The in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2168: --- Summary: The in JdbcPOJOInputOperator. (was: Bug Found in JdbcPOJOInputOperator

[jira] [Resolved] (APEXMALHAR-2168) Bug Found in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua resolved APEXMALHAR-2168. Resolution: Fixed > Bug Found in JdbcPOJOInputOpera

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

[ 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

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

[ 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

[jira] [Created] (APEXMALHAR-2186) Configurable start offset for kafka input operator (0.9)

Siyuan Hua created APEXMALHAR-2186: -- Summary: Configurable start offset for kafka input operator (0.9) Key: APEXMALHAR-2186 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2186 Project: Apache

[jira] [Updated] (APEXMALHAR-2186) Configurable start offset for kafka input operator (0.9)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2186: --- Issue Type: Improvement (was: Bug) > Configurable start offset for kafka input opera

[jira] [Updated] (APEXMALHAR-2168) Bug Found in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2168: --- Fix Version/s: 3.5.0 > Bug Found in JdbcPOJOInputOpera

[jira] [Updated] (APEXMALHAR-2028) Add System.err to ConsoleOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2028: --- Fix Version/s: 3.5.0 > Add System.err to ConsoleOutputOpera

[jira] [Commented] (APEXMALHAR-2028) Add System.err to ConsoleOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415943#comment-15415943 ] Siyuan Hua commented on APEXMALHAR-2028: For high-level API as well &

Re: [ANNOUNCE] New Apache Apex Committer: Devendra Tagare

Welcome, Devendra! On Wed, Aug 10, 2016 at 12:28 PM, Thomas Weise wrote: > The Project Management Committee (PMC) for Apache Apex has asked Devendra > Tagare to become a committer and we are pleased to announce that he has > accepted. > > Devendra has been contributing to Apex for several months

[jira] [Updated] (APEXMALHAR-2158) Duplication of data emitted when the Kafka Input Operator(0.8 version) redeploys

[ https://issues.apache.org/jira/browse/APEXMALHAR-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2158: --- Fix Version/s: 3.5.0 > Duplication of data emitted when the Kafka Input Operator(

[jira] [Commented] (APEXMALHAR-2169) KafkaInputOperator: Dynamic partition is not working in case of ONE_TO_MANY partition strategy

[ https://issues.apache.org/jira/browse/APEXMALHAR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411388#comment-15411388 ] Siyuan Hua commented on APEXMALHAR-2169: [~chaithu] Then I think

[jira] [Commented] (APEXMALHAR-2169) KafkaInputOperator: Dynamic partition is not working in case of ONE_TO_MANY partition strategy

[ https://issues.apache.org/jira/browse/APEXMALHAR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1546#comment-1546 ] Siyuan Hua commented on APEXMALHAR-2169: [~chaithu] I'm still not

[jira] [Commented] (APEXMALHAR-2171) In CacheStore maxCacheSize is not applied

[ https://issues.apache.org/jira/browse/APEXMALHAR-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397862#comment-15397862 ] Siyuan Hua commented on APEXMALHAR-2171: [~lushun...@gmail.com] Could

[jira] [Created] (APEXMALHAR-2171) In CacheStore maxCacheSize is not applied

Siyuan Hua created APEXMALHAR-2171: -- Summary: In CacheStore maxCacheSize is not applied Key: APEXMALHAR-2171 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2171 Project: Apache Apex Malhar

[jira] [Commented] (APEXMALHAR-2169) KafkaInputOperator: Dynamic partition is not working in case of ONE_TO_MANY partition strategy

[ https://issues.apache.org/jira/browse/APEXMALHAR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396353#comment-15396353 ] Siyuan Hua commented on APEXMALHAR-2169: [~chaithu] Can you elaborate

[jira] [Commented] (APEXMALHAR-2168) Bug Found in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394635#comment-15394635 ] Siyuan Hua commented on APEXMALHAR-2168: Hey [~shubhamp], [~lu

[jira] [Created] (APEXMALHAR-2165) Implement a useful default Partitioner and/or Unifier for Keyed Windowed Operator

Siyuan Hua created APEXMALHAR-2165: -- Summary: Implement a useful default Partitioner and/or Unifier for Keyed Windowed Operator Key: APEXMALHAR-2165 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2165

Re: Using DSL api to construct sql queries

But is it a duplication of integration with Calcite? On Thu, Jul 21, 2016 at 9:26 AM, Timothy Farkas < timothytiborfar...@gmail.com> wrote: > I see, cool :) > > On Thu, Jul 21, 2016 at 9:21 AM, Priyanka Gugale > wrote: > > > Hi Tim, > > > > We are not creating our own DSL, the jooq is just anoth

Re: Bleeding edge branch ?

Ok, whether branches or forks. I still think we should have at least some materialized version of malhar/core for the big influencer like java, hadoop or even kafka. Java 8, for example, is actually not new. We don't have to be aggressive to try out new features from those right now. But we can at

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

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2135: --- Fix Version/s: 3.5.0 > Upgrade Kafka 0.8 input operator to support 0.8.2 cli

The first cut of high-level API for windowed transform is ready, please review

The first cut of high-level API for windowed transform is ready, please review. https://github.com/apache/apex-malhar/pull/339 Thanks! Regards, Siyuan

[jira] [Commented] (APEXMALHAR-2155) Make high-level api support multiple ports

[ https://issues.apache.org/jira/browse/APEXMALHAR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379647#comment-15379647 ] Siyuan Hua commented on APEXMALHAR-2155: And watermark > Make hig

[jira] [Created] (APEXCORE-492) The exception from ExitCondition should not be swallowed

Siyuan Hua created APEXCORE-492: --- Summary: The exception from ExitCondition should not be swallowed Key: APEXCORE-492 URL: https://issues.apache.org/jira/browse/APEXCORE-492 Project: Apache Apex Core

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

Siyuan Hua created APEXMALHAR-2154: -- Summary: Update kafka 0.9 input operator to use new CheckpointNotificationListener Key: APEXMALHAR-2154 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2154

  1   2   >