[
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 ma
[
https://issues.apache.org/jira/browse/APEXMALHAR-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXMALHAR-2458.
--
Resolution: Done
Fix Version/s: 3.8.0
> Move kafka related examples from dat
[
https://issues.apache.org/jira/browse/APEXMALHAR-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982108#comment-15982108
]
Vlad Rozov commented on APEXMALHAR-2485:
Time to call Constructor.newInstance
[
https://issues.apache.org/jira/browse/APEXMALHAR-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov updated APEXMALHAR-2485:
---
Description:
Currently, PojoUtils only supports getters and setters. It should be possibl
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 Apex
+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 f
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. There are two JIRA pending
[
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 whe
[
https://issues.apache.org/jira/browse/APEXCORE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980261#comment-15980261
]
Sanjay M Pujare edited comment on APEXCORE-712 at 4/24/17 7:23 PM:
---
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
/12338818/?selectedTab=com.atlassi
[
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 org.a
[
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 se
[
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
[
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 do
[
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
[
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 launc
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 worry about backward compatib
[
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
[
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
> -
+1.
We should not change the default, as this needs explicit user involvement.
The downstream operator has accomodate this behavior.
Thks
Amol
E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre*
www.datatorrent.com
On Mon, Apr 24, 2017 at 10:56 AM, Sanjay Pujare
wrote:
> +1.
+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
+1.
If we didn't have to worry about backward compatibility I would even make
this new behavior as the default behavior (so may be in v4.0 of Apex ?)
On Mon, Apr 24, 2017 at 8:57 AM, Pramod Immaneni
wrote:
> In a failure scenario, when a container fails, it is redeployed along with
> all the op
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
Project
[
https://issues.apache.org/jira/browse/APEXMALHAR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981482#comment-15981482
]
Thomas Weise commented on APEXMALHAR-2483:
--
{code}
Running org.apache.apex.m
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
Iss
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 is
In a failure scenario, when a container fails, it is redeployed along with
all the operators in it. The operators downstream to these operators are
also redeployed within their containers. The operators are restored from
their checkpoint and connect to the appropriate point in the stream
according
+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
28 matches
Mail list logo
