[jira] [Closed] (APEXMALHAR-2101) RuntimeException from Default Bucket which is under managed state.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXMALHAR-2101. Assignee: (was: Chaitanya) > RuntimeException from Default Bucket which is under

[jira] [Commented] (APEXMALHAR-2485) PojoUtils should support empty constructors for Pojos

[ https://issues.apache.org/jira/browse/APEXMALHAR-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982108#comment-15982108 ] Vlad Rozov commented on APEXMALHAR-2485: Time to call Constructor.newInstance() 5280 ms, new

[jira] [Created] (APEXMALHAR-2485) PojoUtils should support empty constructors for Pojos

Vlad Rozov created APEXMALHAR-2485: -- Summary: PojoUtils should support empty constructors for Pojos Key: APEXMALHAR-2485 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2485 Project: Apache

Re: Specialized operator recovery

+1 to support the feature. It will be important to properly name and document the feature. It is quite powerful and may lead to significant performance improvements, but also may cause incorrect results when not used correctly. Thank you, Vlad On 4/24/17 08:57, Pramod Immaneni wrote: In a

Re: Towards Apache Apex 3.6.0 release

Hi, APEXCORE-641 has been fixed and I marked it resolved. I have moved my PR which I believe may result in a minor improvement from the blocking path. Thanks On Mon, Apr 24, 2017 at 12:24 PM, Tushar Gosavi wrote: > Hi All, > > I am going to cut first RC in few days.

[jira] [Resolved] (APEXCORE-641) Subscribers/DataListeners may not be scheduled to execute even when they have data to process

[ https://issues.apache.org/jira/browse/APEXCORE-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-641. -- Resolution: Fixed > Subscribers/DataListeners may not be scheduled to execute even

[jira] [Comment Edited] (APEXCORE-712) Support distribution of custom SSL material to the Stram node while launch the app

[ https://issues.apache.org/jira/browse/APEXCORE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980261#comment-15980261 ] Sanjay M Pujare edited comment on APEXCORE-712 at 4/24/17 7:23 PM: ---

Re: Towards Apache Apex 3.6.0 release

Hi All, I am going to cut first RC in few days. There are two JIRA pending APEXCORE-700 and APEXCORE-641. APEXCORE-700 is close to merge. @Vlad, Can we move APEXCORE-641 out of 3.6? List of 3.6 issues. https://issues.apache.org/jira/browse/APEXCORE/fixforversion

[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient to 4.3.6 version

[ https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-656: --- Summary: Upgrade org.apache.httpcomponents.httpclient to 4.3.6 version (was: Upgrade

[jira] [Updated] (APEXCORE-634) Unifier attributes are not set for modules in DAG

[ https://issues.apache.org/jira/browse/APEXCORE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-634: --- Summary: Unifier attributes are not set for modules in DAG (was: Apex Platform unable to

[jira] [Updated] (APEXCORE-594) Plugin support in Apex

[ https://issues.apache.org/jira/browse/APEXCORE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-594: --- Summary: Plugin support in Apex (was: Investigate adding new functionality to apex through

[jira] [Updated] (APEXCORE-710) Plugin manager does not report exceptions from plugins

[ https://issues.apache.org/jira/browse/APEXCORE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-710: --- Issue Type: Bug (was: Sub-task) Parent: (was: APEXCORE-594) > Plugin manager

[jira] [Updated] (APEXCORE-577) Plugin support to inspect DAG before launch.

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-577: --- Summary: Plugin support to inspect DAG before launch. (was: Visitor API for DAG) > Plugin

[jira] [Resolved] (APEXCORE-577) Plugin support to inspect DAG before launch.

[ https://issues.apache.org/jira/browse/APEXCORE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi resolved APEXCORE-577. Resolution: Fixed Fix Version/s: 3.6.0 > Plugin support to inspect DAG before

Re: Specialized operator recovery

Sanjay, This shouldn't be default as it will give wrong computation results for regular operators. This is only for operators that fall into the category that I described. Thanks On Mon, Apr 24, 2017 at 10:56 AM, Sanjay Pujare wrote: > +1. > > If we didn't have to

[jira] [Resolved] (APEXCORE-699) Investigate versioning for plugins

[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi resolved APEXCORE-699. Resolution: Won't Fix The solution suggested by [~vrozov] looks good. We have provided an

[jira] [Updated] (APEXCORE-660) Documentation for Control tuple support changes

[ https://issues.apache.org/jira/browse/APEXCORE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-660: --- Component/s: Documentation > Documentation for Control tuple support changes >

Re: Specialized operator recovery

+1 for this feature to explicitly identify operators for specialized operator recovery as in Pramod’s email. Don’t think that this can be made default. From my understanding, by default, this can guarantee ATLEAST_ONCE and not EXACTLY_ONCE in the downstream of failed container as the stream is

[jira] [Created] (APEXMALHAR-2484) BlockWriter for writing the part files into the specified directory

Chaitanya created APEXMALHAR-2484: - Summary: BlockWriter for writing the part files into the specified directory Key: APEXMALHAR-2484 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2484

[jira] [Commented] (APEXMALHAR-2483) Error in High Level API test

[ https://issues.apache.org/jira/browse/APEXMALHAR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981482#comment-15981482 ] Thomas Weise commented on APEXMALHAR-2483: -- {code} Running

[jira] [Created] (APEXMALHAR-2483) Error in High Level API test

Thomas Weise created APEXMALHAR-2483: Summary: Error in High Level API test Key: APEXMALHAR-2483 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2483 Project: Apache Apex Malhar

[GitHub] apex-malhar pull request #595: Apexmalhar 2458 Move kafka related examples f...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/595 --- 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

Re: Checkstyle policies with auto generated code

+1 for option 3. Thank you, Vlad On 4/23/17 16:25, Ananth G wrote: Hello All, Apologies if it is a repost as the earlier email did not seem to go through. I have run into a dilemma and would like to know what our policy is to deal with the following situation. As part of the implementation

Checkstyle policies for auto generated code

Hello All, I have run into a dilemma and would like to know what our policy is to deal with the following situation. As part of the implementation for Kudu Input operator (https://issues.apache.org/jira/browse/APEXMALHAR-2472 ) , I will