+1 (binding)
Verified checksums
Verified LICENSE, NOTICE and README.md.
Build with:
mvn clean apache-rat:check verify -Dlicense.skip=false -Pall-modules
install -DskipTests
Thank you,
Vlad
On 11/30/16 22:56, Bhupesh Chawda wrote:
+1
- Verified signatures
- Build and test successful
Yes, Ram explained to me that in practice this would be a useful feature for
Apex devops who typically have no control over Hadoop/Yarn cluster.
On 11/30/16, 9:22 PM, "Mohit Jotwani" wrote:
This is a practical scenario where developers would be required to exclude
certain nodes as they
+1
- Verified signatures
- Build and test successful
- LICENSE, NOTICE, README, CHANGELOG.md exist
~ Bhupesh
On Thu, Dec 1, 2016 at 11:24 AM, David Yan wrote:
> +1 (binding)
>
> Verified existance of LICENSE, NOTICE, README.md and CHANGELOG.md files
> Built with this command:
>
> mvn cl
+1 (binding)
Verified existance of LICENSE, NOTICE, README.md and CHANGELOG.md files
Built with this command:
mvn clean apache-rat:check verify -Dlicense.skip=false -Pall-modules
install
with no errors.
Verified pi demo
On Wed, Nov 30, 2016 at 11:37 AM, Siyuan Hua wrote:
> +1
>
> Verified
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhupesh Chawda resolved APEXMALHAR-2022.
Resolution: Fixed
Fix Version/s: 3.7.0
> S3 Output Module for file copy
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710953#comment-15710953
]
ASF GitHub Bot commented on APEXMALHAR-2022:
Github user asfgit closed th
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/483
---
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
This is a practical scenario where developers would be required to exclude
certain nodes as they might be required for some mission critical
applications. It would be good to have this feature.
I understand that Stram should not get into resourcing and still rely on
Yarn, however, as the App Maste
I would like to work on https://issues.apache.org/jira/browse/APEXCORE-580.
~ Bhupesh
On Thu, Dec 1, 2016 at 5:42 AM, Sandesh Hegde
wrote:
> I am interested in working on the following subtask
>
> https://issues.apache.org/jira/browse/APEXCORE-581
>
> Thanks
>
>
> On Wed, Nov 30, 2016 at 2:07 P
[
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710305#comment-15710305
]
bright chen commented on APEXMALHAR-2361:
-
Probably we can handle DISCARDING
[
https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710303#comment-15710303
]
bright chen commented on APEXMALHAR-2361:
-
Probably we can handle DISCARDING
[
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
[
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
I am interested in working on the following subtask
https://issues.apache.org/jira/browse/APEXCORE-581
Thanks
On Wed, Nov 30, 2016 at 2:07 PM David Yan wrote:
> I have created an umbrella ticket for control tuple support:
>
> https://issues.apache.org/jira/browse/APEXCORE-579
>
> Currently it
[
https://issues.apache.org/jira/browse/APEXMALHAR-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710290#comment-15710290
]
bright chen commented on APEXMALHAR-2361:
-
When AccumulationMode is DISCARDIN
[
https://issues.apache.org/jira/browse/APEXMALHAR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710167#comment-15710167
]
ASF GitHub Bot commented on APEXMALHAR-2362:
GitHub user davidyan74 opene
GitHub user davidyan74 opened a pull request:
https://github.com/apache/apex-malhar/pull/519
APEXMALHAR-2362 #resolve clearing the removedSets at endWindow in
SpillableSetMultimapImpl
@brightchen please review and merge
You can merge this pull request into a Git repository by runni
[
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)
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
[
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710031#comment-15710031
]
bright chen commented on APEXMALHAR-2339:
-
SpillableWindowedKeyedStorage.remo
bright chen created APEXMALHAR-2361:
---
Summary: Optimise SpillableWindowedKeyedStorage remove(Window) to
improve the performance
Key: APEXMALHAR-2361
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2361
[
https://issues.apache.org/jira/browse/APEXMALHAR-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709958#comment-15709958
]
ASF GitHub Bot commented on APEXMALHAR-2359:
GitHub user brightchen opene
GitHub user brightchen opened a pull request:
https://github.com/apache/apex-malhar/pull/518
APEXMALHAR-2359 #resolve #comment Optimise fire trigger to avoid go tâ¦
â¦hrough all data
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
I have created an umbrella ticket for control tuple support:
https://issues.apache.org/jira/browse/APEXCORE-579
Currently it has two subtasks. Please have a look at them and see whether
I'm missing anything or if you have anything to add. You are welcome to add
more subtasks or comment on the exi
[
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
[
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
[
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
[
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
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
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
Apex has automatic blacklisting of the troublesome nodes, please take a
look at the following attributes,
MAX_CONSECUTIVE_CONTAINER_FAILURES_FOR_BLACKLIST
https://www.datatorrent.com/docs/apidocs/com/datatorrent/api/Context.DAGContext.html#MAX_CONSECUTIVE_CONTAINER_FAILURES_FOR_BLACKLIST
BLACKLIS
Not sure if this is what Milind had in mind but we often run into
situations where the dev group
working with Apex has no control over cluster configuration -- to make any
changes to the cluster they need to
go through an elaborate process that can take many days.
Meanwhile, if they notice that a
+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
I agree, Randomly rebooting node is Yarn issue. Even anti-affinity between
apps should be Yarn in long run. We could contribute the above jira.
Thks
Amol
On Wed, Nov 30, 2016 at 10:58 AM, Sanjay Pujare
wrote:
> To me both use cases appear to be generic resource management use cases.
> For exam
To me both use cases appear to be generic resource management use cases. For
example, a randomly rebooting node is not good for any purpose esp. long
running apps so it is a bit of a stretch to imagine that these nodes will be
acceptable for some batch jobs in Yarn. So such a node should be mark
But then, what's the solution to the 2 problem scenarios that Milind
describes ?
Ram
On Wed, Nov 30, 2016 at 10:34 AM, Sanjay Pujare
wrote:
> I think “exclude nodes” and such is really the job of the resource manager
> i.e. Yarn. So I am not sure taking over some of these tasks in Apex would
>
I think “exclude nodes” and such is really the job of the resource manager i.e.
Yarn. So I am not sure taking over some of these tasks in Apex would be very
useful.
I agree with Amol that apps should be node neutral. Resource management in Yarn
together with fault tolerance in Apex should minim
+1
Verified checksums
Verified compilation
- Tushar.
On Wed, Nov 30, 2016 at 7:43 PM, Thomas Weise wrote:
> Can folks please verify the release.
>
> Thanks
>
> --
> sent from mobile
> On Nov 26, 2016 6:32 PM, "Thomas Weise" wrote:
>
>> Dear Community,
>>
>> Please vote on the following Apache
Can folks please verify the release.
Thanks
--
sent from mobile
On Nov 26, 2016 6:32 PM, "Thomas Weise" wrote:
> Dear Community,
>
> Please vote on the following Apache Apex Malhar 3.6.0 release candidate.
>
> This is a source release with binary artifacts published to Maven.
>
> This release i
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708479#comment-15708479
]
ASF GitHub Bot commented on APEXMALHAR-2022:
Github user chaithu14 closed
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708481#comment-15708481
]
ASF GitHub Bot commented on APEXMALHAR-2022:
GitHub user chaithu14 reopen
GitHub user chaithu14 reopened a pull request:
https://github.com/apache/apex-malhar/pull/483
APEXMALHAR-2022 Developed S3 Output Module
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chaithu14/incubator-apex-malhar
APEXMALHAR-
Github user chaithu14 closed the pull request at:
https://github.com/apache/apex-malhar/pull/483
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708392#comment-15708392
]
ASF GitHub Bot commented on APEXMALHAR-2022:
Github user chaithu14 closed
GitHub user chaithu14 reopened a pull request:
https://github.com/apache/apex-malhar/pull/483
APEXMALHAR-2022 Developed S3 Output Module
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chaithu14/incubator-apex-malhar
APEXMALHAR-
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708393#comment-15708393
]
ASF GitHub Bot commented on APEXMALHAR-2022:
GitHub user chaithu14 reopen
Github user chaithu14 closed the pull request at:
https://github.com/apache/apex-malhar/pull/483
---
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
49 matches
Mail list logo
