Re: Java packages: legacy -> org.apache.apex

It is time to resurrect this thread and get going with the work. For the next release, I will sign up to do the package move in Malhar: https://issues.apache.org/jira/browse/APEXMALHAR-2517 In general this will be straightforward; most classes in Malhar are marked evolving and it is trivial for

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086773#comment-16086773 ] Vlad Rozov commented on APEXCORE-759: - Will unification also be supported for 1xNx1 case? Can it be

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086770#comment-16086770 ] Pramod Immaneni commented on APEXCORE-759: -- Will double check and see whether 1xN was already

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

I open ticket INFRA-14588 to enable it back. Thank you, Vlad On 7/13/17 19:13, Thomas Weise wrote: This is an excellent upgrade, but like everything else it should be discussed upfront. Does it in any way affect the JIRA integration? For the PR I just opened I don't see the PR link attached

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086745#comment-16086745 ] Vlad Rozov commented on APEXCORE-759: - [~thw] Do you know where unification is done in the case of

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086740#comment-16086740 ] Vlad Rozov commented on APEXCORE-759: - I guess the comment from the code is no longer in effect. It

Re: [jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

Will double check and see whether it was already implemented and we need to add the appropriate consistency checks or if 1xN configuration will have to be supported anew. Vlad to answer your question, yes it will be one thread for all. On Thu, Jul 13, 2017 at 6:47 PM Thomas Weise (JIRA)

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086716#comment-16086716 ] Thomas Weise commented on APEXCORE-759: --- There is no restriction for CONTAINER_LOCAL. THREAD_LOCAL

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086705#comment-16086705 ] Vlad Rozov commented on APEXCORE-759: - [~thw] Can be done on the application master. Throwing

[jira] [Commented] (APEXCORE-760) Webapp tracking URL does not include full qualified hostname

[ https://issues.apache.org/jira/browse/APEXCORE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086704#comment-16086704 ] Sanjay M Pujare commented on APEXCORE-760: -- Could this be a host configuration issue on the app

[jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086702#comment-16086702 ] Vlad Rozov commented on APEXCORE-759: - Will all N downstream partitions be in the same thread? I

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

Even in this case rebase is not a no-op. When a contributor rebases his own commit against upstream/master, a committer can push it directly to github without using github options. In this case committer will not be recorded, it is the same as before. Thank you, Vlad On 7/13/17 18:08,

[jira] [Updated] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-759: Summary: Operators connected using THREAD_LOCAL stream locality should enforce parallel partition

[jira] [Comment Edited] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086681#comment-16086681 ] Pramod Immaneni edited comment on APEXCORE-759 at 7/14/17 1:06 AM: --- We

[jira] [Commented] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086680#comment-16086680 ] Thomas Weise commented on APEXCORE-759: --- Please elaborate. How many partitions a partitioner

[jira] [Commented] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086681#comment-16086681 ] Pramod Immaneni commented on APEXCORE-759: -- We catch this when parallel partitioning and MxN

[jira] [Commented] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086678#comment-16086678 ] Vlad Rozov commented on APEXCORE-759: - IMO, it is a bug. DAG validation should be able to catch

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

My understanding is that rebase always changes commit, there is no no-op rebase. Thank you, Vlad On 7/13/17 17:39, Pramod Immaneni wrote: +1 for all of them. Would rebase and commit record committer even if the rebase is a no-op. On Thu, Jul 13, 2017 at 4:43 PM, Vlad Rozov

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

+1 for all of them. Would rebase and commit record committer even if the rebase is a no-op. On Thu, Jul 13, 2017 at 4:43 PM, Vlad Rozov wrote: > OK, I agree, sorry for not sending a notification prior to filing an INFRA > ticket. Should we now focus on how new

[jira] [Commented] (APEXCORE-760) Webapp tracking URL does not include full qualified hostname

[ https://issues.apache.org/jira/browse/APEXCORE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086648#comment-16086648 ] Thomas Weise commented on APEXCORE-760: --- HTTP ERROR 500 Problem accessing

[jira] [Created] (APEXCORE-760) Webapp tracking URL does not include full qualified hostname

Thomas Weise created APEXCORE-760: - Summary: Webapp tracking URL does not include full qualified hostname Key: APEXCORE-760 URL: https://issues.apache.org/jira/browse/APEXCORE-760 Project: Apache

[jira] [Commented] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086634#comment-16086634 ] Thomas Weise commented on APEXCORE-759: --- Are you sure this is a bug? If not, then please ask a

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

OK, I agree, sorry for not sending a notification prior to filing an INFRA ticket. Should we now focus on how new functionality affects contributors and committers? 1. I checked with INFRA team and they recommend (strongly) to use github for push (and pulls) even though push (and pull) to

[jira] [Commented] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086598#comment-16086598 ] Pramod Immaneni commented on APEXCORE-759: -- Looks like it is because of the mismatch in the

[jira] [Updated] (APEXCORE-759) THREAD_LOCAL exception not handled.

[ https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay Bangalore Srikanth updated APEXCORE-759: -- Summary: THREAD_LOCAL exception not handled. (was: THREAD_LOCAL

[jira] [Created] (APEXCORE-759) THREAD_LOCAL exception are not handled.

Vinay Bangalore Srikanth created APEXCORE-759: - Summary: THREAD_LOCAL exception are not handled. Key: APEXCORE-759 URL: https://issues.apache.org/jira/browse/APEXCORE-759 Project: Apache

[jira] [Resolved] (APEXCORE-754) Add plugin class jar with it's dependencies to the list of libraries deployed with an application

[ https://issues.apache.org/jira/browse/APEXCORE-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-754. - Resolution: Implemented Fix Version/s: 3.7.0 > Add plugin class jar with it's

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

I wasn't focussing on the minor disruption. It was unexpected and that's ok. What I was saying is that it would have been good to know that we are adding this functionality or looking into adding it before it happened. Thanks On Thu, Jul 13, 2017 at 3:34 PM, Vlad Rozov

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

As I mentioned, it was not clear that enabling gitbox will lead to operation disruption and change of an existing upstream. It sounded like an additional functionality when I learned about the opportunity to enable write access on github, so I wanted to check how it works before presenting it

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

The integration is a good feature addition. Would be good to have had a heads up or a quick discussion unless I missed one. Thanks On Thu, Jul 13, 2017 at 2:31 PM, Vlad Rozov wrote: > It was not clear that the project needs to be removed from >

[jira] [Commented] (APEXCORE-758) Unify Apex plugin configuration settings

[ https://issues.apache.org/jira/browse/APEXCORE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086431#comment-16086431 ] Pramod Immaneni commented on APEXCORE-758: -- There needs to be a configuration for a plugin as

[jira] [Resolved] (APEXMALHAR-2434) JMSTransactionableStore uses Session.createQueue() which fails

[ https://issues.apache.org/jira/browse/APEXMALHAR-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2434. - Resolution: Fixed Fix Version/s: 3.8.0 > JMSTransactionableStore uses

[jira] [Created] (APEXCORE-758) Unify Apex plugin configuration settings

Vlad Rozov created APEXCORE-758: --- Summary: Unify Apex plugin configuration settings Key: APEXCORE-758 URL: https://issues.apache.org/jira/browse/APEXCORE-758 Project: Apache Apex Core Issue

Re: anyone else seeing a 404

Looks like it was moved to gitbox in process of supporting two way sync with github. Some notice would have been nice. https://gitbox.apache.org/repos/asf/apex-core.git 2017-07-13 14:07 GMT-07:00 Sandesh Hegde : > +1 > > On Thu, Jul 13, 2017 at 2:00 PM Amol Kekre

Re: anyone else seeing a 404

+1 On Thu, Jul 13, 2017 at 2:00 PM Amol Kekre wrote: > me too > > Thks > Amol > > > E:a...@datatorrent.com | M: 510-449-2606 <(510)%20449-2606> | Twitter: > @*amolhkekre* > > www.datatorrent.com > > > On Thu, Jul 13, 2017 at 1:31 PM, Pramod Immaneni

Re: [jira] [Apache Infrastructure] Add Apache Apex to the Gitbox [INFRA-14544]

Does this mean the repo is no longer available on asf? When was this initiated? Thanks On Wed, Jul 12, 2017 at 8:22 PM, Vlad Rozov wrote: > Committers, > > See below. Now it is possible to merge PRs directly on github. Please make > sure *not* to use "create merge

Re: anyone else seeing a 404

me too Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com On Thu, Jul 13, 2017 at 1:31 PM, Pramod Immaneni wrote: > https://git-wip-us.apache.org/repos/asf?p=apex-core.git >

anyone else seeing a 404

https://git-wip-us.apache.org/repos/asf?p=apex-core.git

[jira] [Commented] (APEXCORE-602) Provide a "group-id" in the event object so that events are grouped together by a "root cause".

[ https://issues.apache.org/jira/browse/APEXCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085875#comment-16085875 ] Priyanka Gugale commented on APEXCORE-602: -- Testing covered: 1. Wrote unit tests 2. Simulated

[jira] [Updated] (APEXCORE-756) Fix ConcurrentModificationException in GroupingManager

[ https://issues.apache.org/jira/browse/APEXCORE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXCORE-756: - Summary: Fix ConcurrentModificationException in GroupingManager (was: Fix test failure