Hi
For the initial release, I am planning to have static event log levels,
i.e., log levels without considering context in which event was generated.
I will add support for updating this log level so that in future, we can
update log levels considering the context of the event.
Ajay
On Fri, J
Tushar Gosavi created APEXCORE-622:
--
Summary: event files are overwritten when master restarts.
Key: APEXCORE-622
URL: https://issues.apache.org/jira/browse/APEXCORE-622
Project: Apache Apex Core
Hi,
StrAM raises events whenever Operator or Container restarts. In Apex Dag
whenever a container/operator, say operator "X", is killed/terminated all
downstream operators are redeployed. And during redeploy process they raise
stop/start events. These events are triggered by redeployment of operat
[
https://issues.apache.org/jira/browse/APEXCORE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Narkhede reassigned APEXCORE-621:
Assignee: Deepak Narkhede
> populate TIMEOUT_WINDOW_COUNT for thread local operat
[
https://issues.apache.org/jira/browse/APEXMALHAR-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837265#comment-15837265
]
Yogi Devendra commented on APEXMALHAR-2369:
---
[~chaithu] Could you please re
[
https://issues.apache.org/jira/browse/APEXCORE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tushar Gosavi updated APEXCORE-621:
---
Description:
A -> B -> C -> D
In above dag if we have set TIMEOUT_WINDOW_COUNT on 'C' and '
Tushar Gosavi created APEXCORE-621:
--
Summary: populate TIMEOUT_WINDOW_COUNT for thread local operators
from downstreams.
Key: APEXCORE-621
URL: https://issues.apache.org/jira/browse/APEXCORE-621
Proj
GitHub user oliverwnk opened a pull request:
https://github.com/apache/apex-malhar/pull/543
APEXCORE-2394 adding check if already been rotated
@PramodSSImmaneni
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oliverwnk/apex-malha
Oliver Winke created APEXMALHAR-2394:
Summary: AbstractFileOutputOperator.rotate(...) does not check if
file has already been rotated before computing next rotation
Key: APEXMALHAR-2394
URL: https://issues.apa
Jose Casillas created APEXCORE-620:
--
Summary: Support Fat Jar without POM, allowing Gradle and other
build systems
Key: APEXCORE-620
URL: https://issues.apache.org/jira/browse/APEXCORE-620
Project: A
Hi Sandesh,
For upgrading apex in bigtop we need to create a PR in bigtop. Later its in
there control when to release that as a part of apt or yum repo. It's we
who are integrating with them here.
Hence I think its in best interest to have a quick vote of confidence with
our community as well.
-
Prefer it to be made part of Apex core release. No need for another vote.
On Fri, Jan 20, 2017 at 1:53 PM Amol Kekre wrote:
> +1
>
> Thks
> Amol
>
>
> On Thu, Jan 19, 2017 at 8:55 PM, Priyanka Gugale >
> wrote:
>
> > +1
> >
> > On Fri, Jan 20, 2017 at 9:25 AM, Chinmay Kolhatkar <
> > chin...@da
GitHub user yogidevendra opened a pull request:
https://github.com/apache/apex-malhar/pull/542
APEXMALHAR-2369 S3 output-tuple-based
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yogidevendra/apex-malhar
APEXMALHAR-2369-s3-out
Hi All,
I have updated the design document as per review comments on pull
request (https://issues.apache.org/jira/secure/attachment/12849094/dag.docx).
Please provide your suggestion.
- Tushar.
On Fri, Sep 16, 2016 at 6:40 PM, Tushar Gosavi wrote:
> Hi All,
>
> I have opened a review pull requ
14 matches
Mail list logo
