Upgrade Apache Bigtop to Apex Core 3.5.0

Dear Community, Now that Apex core 3.5.0 is released, is it good time to upgrade Apache Bigtop for Apex to 3.5.0? -Chinmay.

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1 for including Apex 3.5 in Bigtop. - Tushar. On Thu, Jan 19, 2017 at 2:23 PM, Chinmay Kolhatkar wrote: > Dear Community, > > Now that Apex core 3.5.0 is released, is it good time to upgrade Apache > Bigtop for Apex to 3.5.0? > > -Chinmay.

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1, Also suggest you to start a thread for that in Big top community... Thanks, A _ Sent with difficulty, I mean handheld ;) On 19 Jan 2017 2:28 pm, "Tushar Gosavi" wrote: > +1 for including Apex 3.5 in Bigtop. > > - Tushar. > > >

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

Yes. Will be doing that next. - Chinmay. On 19 Jan 2017 6:20 p.m., "Aniruddha Thombare" wrote: > +1, Also suggest you to start a thread for that in Big top community... > > Thanks, > > A > > > _ > Sent with difficulty, I mean

[jira] [Commented] (APEXCORE-612) Add a logging for out of sequence endWindow tuple

[ https://issues.apache.org/jira/browse/APEXCORE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830742#comment-15830742 ] Sandesh commented on APEXCORE-612: -- I was modifying buffer server and there was a bug, which created

[jira] [Commented] (APEXCORE-612) Add a logging for out of sequence endWindow tuple

[ https://issues.apache.org/jira/browse/APEXCORE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830735#comment-15830735 ] gaurav gupta commented on APEXCORE-612: --- Can you please add more details to this? Are you saying

[jira] [Commented] (APEXMALHAR-2001) Fix all the checkstyle violations in kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830653#comment-15830653 ] ASF GitHub Bot commented on APEXMALHAR-2001: GitHub user oliverwnk opened a pull request:

[GitHub] apex-malhar pull request #540: APEXMALHAR-2001 Fixed checkstyle violations i...

GitHub user oliverwnk opened a pull request: https://github.com/apache/apex-malhar/pull/540 APEXMALHAR-2001 Fixed checkstyle violations in Kafka @sandeshh @tweise please review and merge as appropriate You can merge this pull request into a Git repository by running: $ git

[GitHub] apex-site pull request #67: Apexcore-553 tracking download button click even...

GitHub user mx4web opened a pull request: https://github.com/apache/apex-site/pull/67 Apexcore-553 tracking download button click event @PramodSSImmaneni Please review You can merge this pull request into a Git repository by running: $ git pull

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1 assuming not a lot of work is involved. What does it take to add a mention of Apex in http://bigtop.apache.org/ ? On 1/19/17, 8:12 AM, "Pramod Immaneni" wrote: +1 On Thu, Jan 19, 2017 at 12:53 AM, Chinmay Kolhatkar wrote:

Re: [DISCUSS] Stram events log levels

Strong +1 for the reasons cited by Ajay and Hitesh. Do we really need to modify the EventInfo class? Wouldn’t the BeanUtils.describe(event) automatically populate the EventLogLevel into “data” (a Map) as a property? All the downstream code including the REST API will then just

[jira] [Assigned] (APEXMALHAR-2221) Fix checkstyle violations in benchmark module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Winke reassigned APEXMALHAR-2221: Assignee: Oliver Winke > Fix checkstyle violations in benchmark module >

[jira] [Assigned] (APEXMALHAR-2001) Fix all the checkstyle violations in kafka module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Winke reassigned APEXMALHAR-2001: Assignee: Oliver Winke > Fix all the checkstyle violations in kafka module >

Re: APEXCORE-294 Clean application shutdown

Hi Thomas, I agree with you on the current behavior. The effect of shutdown can be achieve with kill. I was more worried about backward compatibility issue while relaunching the shutdown app, hence kept the default as same as before (cli and rest api default). If we don't want to retain the

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

Sanjay, Its not a lot of work. Just a version change, but primarily follwing apache process for bigtop. Powered by Page of bigtop is here: https://cwiki.apache.org/confluence/display/BIGTOP/Powered+By+Bigtop Looking at the existing content, I would like to know what we can add there. All, Thanks

[jira] [Commented] (APEXCORE-608) Streaming Containers use stale RPC proxy after connection is closed

[ https://issues.apache.org/jira/browse/APEXCORE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831181#comment-15831181 ] ASF GitHub Bot commented on APEXCORE-608: - GitHub user vrozov opened a pull request:

Re: [DISCUSS] Stram events log levels

+1 for this feature. The event priority is not statically defained by its type, it also depends on on context in which event is generated. for example STOP_CONTAINER event could be because of - jvm issue/out of memory - This could be at much higher level - All operators in containers have

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1 On Fri, Jan 20, 2017 at 9:25 AM, Chinmay Kolhatkar wrote: > Sanjay, > Its not a lot of work. Just a version change, but primarily follwing apache > process for bigtop. > Powered by Page of bigtop is here: >

Re: [DISCUSS] Stram events log levels

+1 it will enhance the user experience and the approach suggested by Ajay doesn't seems to add significant overhead. Also I feel that in future it can be enhanced further and UI can also filter the event logs based on these log levels. On Jan 19, 2017 10:57 PM, "AJAY GUPTA"

[jira] [Created] (APEXCORE-615) Out of sequence tuple exception - kill the whole app

Sandesh created APEXCORE-615: Summary: Out of sequence tuple exception - kill the whole app Key: APEXCORE-615 URL: https://issues.apache.org/jira/browse/APEXCORE-615 Project: Apache Apex Core

Re: APEXCORE-294 Clean application shutdown

Hi Thomas, As discussed I will remote the old behaviour of shutdown. - Tushar. On Fri, Jan 20, 2017 at 10:03 AM, Tushar Gosavi wrote: > Hi Thomas, > > I agree with you on the current behavior. The effect of shutdown can > be achieve with kill. I was more worried about

[jira] [Assigned] (APEXCORE-612) Add a logging for out of sequence endWindow tuple

[ https://issues.apache.org/jira/browse/APEXCORE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandesh reassigned APEXCORE-612: Assignee: Sandesh > Add a logging for out of sequence endWindow tuple >

[jira] [Created] (APEXCORE-612) Add a logging for out of sequence endWindow tuple

Sandesh created APEXCORE-612: Summary: Add a logging for out of sequence endWindow tuple Key: APEXCORE-612 URL: https://issues.apache.org/jira/browse/APEXCORE-612 Project: Apache Apex Core Issue

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1 On Thu, Jan 19, 2017 at 12:53 AM, Chinmay Kolhatkar wrote: > Dear Community, > > Now that Apex core 3.5.0 is released, is it good time to upgrade Apache > Bigtop for Apex to 3.5.0? > > -Chinmay. >

[jira] [Created] (APEXCORE-614) Upgrade beanutils version to 1.9.2

Pramod Immaneni created APEXCORE-614: Summary: Upgrade beanutils version to 1.9.2 Key: APEXCORE-614 URL: https://issues.apache.org/jira/browse/APEXCORE-614 Project: Apache Apex Core

[DISCUSS] Stram events log levels

Hi Apex community, Currently, events logged by stram such as StartContainer, StartOperator, StopContainer, StopOperator, etc dont have any associated priority level. We can provide log levels for such Stram events. Log levels can be INFO, WARN, ERROR Eg: 1. Start Container, Start Operator are

Re: APEXCORE-294 Clean application shutdown

Tushar, I would like to see the use case for "hard shutdown" vs kill. The current shutdown behavior isn't useful, confusing and sometimes does not even end the app (based on feedback received in the past from users). I would prefer we don't retain it without clear understanding of use case and

[jira] [Commented] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830240#comment-15830240 ] Pramod Immaneni commented on APEXCORE-614: -- https://github.com/apache/apex-core/pull/394 >

[jira] [Updated] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-614: - Issue Type: Improvement (was: Bug) > Upgrade beanutils version to 1.9.2 >

[jira] [Resolved] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXCORE-614. -- Resolution: Fixed Fix Version/s: 3.5.0 > Upgrade beanutils version to 1.9.2 >

[jira] [Created] (APEXCORE-613) Fix/Remove the LogicalNode's javadoc.

Sandesh created APEXCORE-613: Summary: Fix/Remove the LogicalNode's javadoc. Key: APEXCORE-613 URL: https://issues.apache.org/jira/browse/APEXCORE-613 Project: Apache Apex Core Issue Type: Bug

[jira] [Closed] (APEXCORE-614) Upgrade beanutils version to 1.9.2

[ https://issues.apache.org/jira/browse/APEXCORE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXCORE-614. - > Upgrade beanutils version to 1.9.2 > -- > > Key:

Re: [DISCUSS] Stram events log levels

Current event log mechanism : The events recorded are currently recorded in datatorrent/apps/{appid}/events/folder in files named part{id}.txt . eg : datatorrent/apps/application_1483801541352_0003/events/part0.txt We can access these events via REST Api which returns the list of events as