Re: [VOTE] Move Apex to the Apache Attic

+1 Thank you, Vlad > On Aug 13, 2019, at 19:22, Atri Sharma wrote: > > +1 > > On Wed, 14 Aug 2019 at 07:32, Thomas Weise wrote: > >> Hi, >> >> There has been discussion > 6 months ago [1] on whether it is time to move >> Apex to Attic or not. At the time few participants expressed

[jira] [Resolved] (APEXCORE-819) Use Random.nextdouble instead of Math.Random

[ https://issues.apache.org/jira/browse/APEXCORE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-819. - Resolution: Not A Bug > Use Random.nextdouble instead of Math.Ran

Re: Contribution and committer guidelines

> On Jan 29, 2019, at 20:04, Justin Mclean wrote: > > Hi, > >> Badly written code, missing and failing unit tests make it harder for >> everyone to contribute. > > IMO having code that can be easily improved makes it easier for people to > contribute. Possibly you are interested in

Re: Contribution and committer guidelines

Sanjay, I never threaten to -1 https://github.com/apache/apex-core/pull/607 . The -1 would apply to the proposal to drop SSL support and your suggestion to check on user@apex. The discussion regarding SSL including backward compatibility needs to

Re: Contribution and committer guidelines

n 28, 2019 at 1:36 PM Pramod Immaneni > wrote: > >> On Mon, Jan 28, 2019 at 12:45 PM Vlad Rozov wrote: >> >>> IMO, the performance criteria is quite vague and it needs to be taken on >> a >>> case by case basis. Fixing not critical bug or adding minor fu

Re: Contribution and committer guidelines

re the -1 is overridden. -1 needs an > explanation that fits with what we come up with on this thread. > > Amol > > > On Mon, Jan 28, 2019 at 12:45 PM Vlad Rozov wrote: > >> IMO, the performance criteria is quite vague and it needs to be taken on a >> case by case basis. Fix

Re: Contribution and committer guidelines

o-reviewer > from my peer reviewers in the PR. I can dig into the archives and find > those if needed. > > Thanks > > On Mon, Jan 28, 2019 at 8:43 AM Vlad Rozov wrote: > >> Is there an example from prior PRs where it was not accepted/merged due to >> a disagreement

Re: Contribution and committer guidelines

Is there an example from prior PRs where it was not accepted/merged due to a disagreement between a contributor and a committer on the amount of refactoring or code quality? Thank you, Vlad > On Jan 27, 2019, at 06:56, Chinmay Kolhatkar > wrote: > > +1. > > On Sat, 26 Jan 2019, 11:56 pm

Re: support Hadoop 3.X

Hi Aaron, I’d recommend to start with upgrading Hadoop dependency to 3.x, recompiling and running unit test. Also, before you put significant effort into Hadoop 3.x upgrade, let’s discuss and vote on dev@apex. Once everyone agrees and vote passes, please open JIRA for tracking the changes.

Re: Salesforce operator

; > Thanks > > On Wed, Jan 9, 2019 at 4:08 PM Vlad Rozov wrote: > >> Pramod, >> >> Did you consider using CometD library directly? epm-connector is a thin >> layer on top of CometD and skipping it will allow you at least to resolve >> dependency on

Re: [DISCUSS] Time for attic?

n. Hopefully it's not too late for that. > > Sanjay > > On Wed, Jan 9, 2019 at 2:01 PM Vlad Rozov wrote: > >> Hi Sanjay, long time, no see. >> >> This is my attempt to mobilize the community and see if we can revive some >> activity on the project. Not

Re: [DISCUSS] Time for attic?

he ASF owns the Apex > trademark. > > -Taylor > >> On Jan 9, 2019, at 5:01 PM, Vlad Rozov wrote: >> >> Hi Sanjay, long time, no see. >> >> This is my attempt to mobilize the community and see if we can revive some >> activity on the project. Note th

Salesforce operator

Pramod, Did you consider using CometD library directly? epm-connector is a thin layer on top of CometD and skipping it will allow you at least to resolve dependency on a snapshot version. Thank you, Vlad > On Jan 9, 2019, at 14:52, Thomas Weise wrote: > > Thanks for the actionable input.

Re: [DISCUSS] Time for attic?

t; drive to move the project to the attic. May I know why you chose the last > option instead of one of the others? It will be good to know your answer > before discussing the details of people staying away or being discouraged. > > Sanjay > > > > On Wed, Jan 9, 2019 at 10

Re: [DISCUSS] Time for attic?

gt; Amol > > > On Wed, Jan 9, 2019 at 9:22 AM Vlad Rozov wrote: > >> Remember that to vote -1 it is necessary to provide justification, so I’d >> like to see the justifications and the plan from those who do not want to >> move Apex to the attic. I am also

Re: [DISCUSS] Time for attic?

ting a move to attic. That should be a > consequence of status of the project; inline with ASF policies. > > Thomas > > > On Wed, Jan 9, 2019 at 9:22 AM Vlad Rozov wrote: > >> Remember that to vote -1 it is necessary to provide justification, so I’d >> like to see the just

Re: [DISCUSS] Time for attic?

feel it is a dead end, you don’t have to continue to be involved with the > project and that’s your prerogative. Let others who want to continue, take > it forward, why try to force your will on to everyone. > > Thanks > > On Wed, Jan 9, 2019 at 8:43 AM Vlad Rozov wrote:

Re: [DISCUSS] Time for attic?

Without concrete details of what will be committed (support for k8s, hadoop 3.x, kafka 2.x, etc) and what requirements in code submission needs to be relaxed (well written java code, consistent code style, successful build with passing unit tests in CI, providing unit test, etc) the statements

Re: [DISCUSS] Time for attic?

hough that >>> would be largely regrettable. Jan end sounds reasonable for the >> submission >>> although it’s outcome should not determine the future of the project. >>> >>> Thanks >>> >>> On Mon, Jan 7, 2019 at 6:09 PM Vlad Rozov wrote: >&

Re: [DISCUSS] Time for attic?

re are concerns > that the policies are contributing to declining participation. > > Thanks > > On Tue, Jan 8, 2019 at 12:25 PM Vlad Rozov wrote: > >> This e-mail thread is to bring to the community the Apache board concerns >> and questions and in particular whether or n

Re: [DISCUSS] Time for attic?

It will be good to provide concrete examples when commits were not accepted due to the high bar and overall percentage of rejected commits compared to total number of commits that will support the statement. Actually few more folks were added to PMCs and there were absolutely no new

Re: [DISCUSS] Time for attic?

when > there is no consensus. Thomas has done a good job over the years preparing > the reports for board and participating in community governance discussions > but if he wishes to not continue to do that, I am sure others can take up > that responsibility. > > Thanks > &g

Re: [DISCUSS] Time for attic?

itter cannot or does not wish to >>> participate at any time, they can choose to remain inactive, there is no >>> obligation. If someone feels strongly that they rather not remain >> inactive >>> while being part of the project they can choose to resign, although that &g

Re: [DISCUSS] Time for attic?

ote: > > For what it is worth, I think that would be a shame... > > Sent from my iPhone > >> On Jan 7, 2019, at 12:00, Vlad Rozov wrote: >> >> Does anyone plan to contribute to the project in the near future? Otherwise, >> I plan to submit a vote to move the

Re: [DISCUSS] Time for attic?

or that I am trying to get clearance on before > submitting. Will likely need a maven server to host a dependency that's not > on central. > > Thanks > > On Mon, Jan 7, 2019 at 9:08 AM Vlad Rozov wrote: > >> Does anyone plan to contribute to the project in the near fu

[DISCUSS] Time for attic?

Does anyone plan to contribute to the project in the near future? Otherwise, I plan to submit a vote to move the project to Apache attic. Thank you, Vlad

Re: Branch 3.7.0 failing install related to Kryo version...perhaps

+1. Apex does not have as large community as other Apache project, but let's try to build it. Thank you, Vlad On 6/20/18 10:24, Pramod Immaneni wrote: Aaron, Your concerns are legitimate, the number of folks contributing in terms of code commits has reduced quite a bit. I do however still

Re: Branch 3.7.0 failing install related to Kryo version...perhaps

AFAIK, those RPC calls are expected to fail (test for RPC timeout). The test fails due to the change in Kryo flush behavior, please see my other response. Thank you, Vlad On 6/20/18 09:09, Pramod Immaneni wrote: There are hadoop IPC calls are failing possibly because of its reliance on kryo

Re: Kryo version and default serializer

Hi Aaron, Nice to see more contributors to the Apex! Welcome. I'd suggest that we stop this e-mail thread and continue discussion on the other dev@apex only e-mail thread. Usually users@apex is not a good choice to discuss dependency upgrades. Please be patient, majority of Apex and Apache

[jira] [Resolved] (APEXCORE-714) Reusable instance operator recovery

[ https://issues.apache.org/jira/browse/APEXCORE-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-714. - Resolution: Implemented Fix Version/s: 4.0.0 > Reusable instance operator recov

[jira] [Resolved] (APEXCORE-817) StramLocalCluster.testDynamicLoading test failing on travis

[ https://issues.apache.org/jira/browse/APEXCORE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-817. - Resolution: Fixed Fix Version/s: 4.0.0 > StramLocalCluster.testDynamicLoading t

[jira] [Resolved] (APEXCORE-810) Concurrent modification exception during connection cleanup in buffer server

[ https://issues.apache.org/jira/browse/APEXCORE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-810. - Resolution: Fixed Fix Version/s: 4.0.0 > Concurrent modification exception dur

Re: Proposal for UI component in stram

could provide something like MetricsStore functionality which was there in DataTorrent RTS. -- Thanks and Regards, Shubhrajyoti Mohapatra On Tue, Jun 12, 2018 at 2:49 AM Vlad Rozov wrote: IMO it will be hard to provide UI that meets everyone expectation. An external webUI can serve two go

Re: Proposal for UI component in stram

better visual output. Overall I am +1 on the idea. On Mon, Jun 11, 2018 at 8:59 AM Vlad Rozov wrote: Clarification: I am -0 on making UI part of the stram. I am +1 on providing reference webUI application outside of the stram. Thank you, Vlad On 6/9/18 07:05, Vlad Rozov wrote: -0: stram

Re: Proposal for UI component in stram

Clarification: I am -0 on making UI part of the stram. I am +1 on providing reference webUI application outside of the stram. Thank you, Vlad On 6/9/18 07:05, Vlad Rozov wrote: -0: stram provides REST API to query runtime information and IMO this is sufficient to build an external webUI

Apex core Travis CI build fails

Anyone to volunteer fixing Travis CI build? Tests in error:   StramLocalClusterTest.testDynamicLoading:296 » UnsupportedClassVersion POJO ha... Thank you, Vlad

Re: Proposal for UI component in stram

-0: stram provides REST API to query runtime information and IMO this is sufficient to build an external webUI application(s). Thank you, Vlad On 6/6/18 11:17, Ambarish Pande wrote: +1 For this feature. It would be really helpfull for users to visualize all this information and the DAG. +1

[jira] [Updated] (APEXCORE-810) Concurrent modification exception during connection cleanup in buffer server

[ https://issues.apache.org/jira/browse/APEXCORE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-810: Description: {noformat} ERROR com.datatorrent.bufferserver.server.Server: Buffer server Server

Re: [ANNOUNCE] New Apache Apex PMC Member: Chinmay Kolhatkar

Congrats Chinmay! Thank you, Vlad On 5/24/18 12:27, Ananth G wrote: Congratulations Chinmay Regards Ananth On 25 May 2018, at 4:19 am, amol kekre wrote: Congrats Chinmay Amol On Thu, May 24, 2018 at 10:34 AM, Hitesh Kapoor wrote:

Re: Your buildbot script apex.conf

at 9:18 AM, Vlad Rozov <vro...@apache.org> wrote: line 217 where and how that affects Apex in a practical way. Thank you, Vlad On 5/22/18 07:19, sebb wrote: On 22 May 2018 at 15:11, Vlad Rozov <vro...@apache.org> wrote: What build is affected by the change? See line 217 - i

Re: Your buildbot script apex.conf

line 217 where and how that affects Apex in a practical way. Thank you, Vlad On 5/22/18 07:19, sebb wrote: On 22 May 2018 at 15:11, Vlad Rozov <vro...@apache.org> wrote: What build is affected by the change? See line 217 - it looks like this applies to several core builds. Tha

Re: Your buildbot script apex.conf

What build is affected by the change? Thank you, Vlad On 5/22/18 03:01, sebb wrote: I happened to notice that the Apex buildbot conf file has a comment that the SingleBranchScheduler is not working. The same problem affected a builder that I was working on; it turns out that the Gitbox

Re: [DISCUSS] Maven version

ASF Jenkins has 3.3 and 3.5 available. Thank you, Vlad On 5/17/18 07:03, Thomas Weise wrote: What are the versions available in ASF Jenkins and with the common package managers? On Wed, May 16, 2018 at 3:20 PM, Vlad Rozov <vro...@apache.org> wrote: Note that the question is reg

Re: [DISCUSS] Maven version

org/jira/browse/MNG-5786 ? Regards, Ananth On Wed, May 16, 2018 at 5:13 AM, Vlad Rozov <vro...@apache.org> wrote: I think it is time to revisit minimum maven version required to build Apex. I suggest upgrading to 3.3.1 at minimum to get maven.multiModuleProjectDirectory property supported. Another o

Re: [DISCUSS] Maven version

Wed, May 16, 2018 at 5:13 AM, Vlad Rozov <vro...@apache.org> wrote: I think it is time to revisit minimum maven version required to build Apex. I suggest upgrading to 3.3.1 at minimum to get maven.multiModuleProjectDirectory property supported. Another option is to upgrade to 3.5.x. Thank you, Vlad

[DISCUSS] Maven version

I think it is time to revisit minimum maven version required to build Apex. I suggest upgrading to 3.3.1 at minimum to get maven.multiModuleProjectDirectory property supported. Another option is to upgrade to 3.5.x. Thank you, Vlad

[jira] [Created] (APEXCORE-815) Whitelist CVE-2016-6811

Vlad Rozov created APEXCORE-815: --- Summary: Whitelist CVE-2016-6811 Key: APEXCORE-815 URL: https://issues.apache.org/jira/browse/APEXCORE-815 Project: Apache Apex Core Issue Type: Task

[jira] [Updated] (APEXCORE-815) Whitelist CVE-2016-6811

[ https://issues.apache.org/jira/browse/APEXCORE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-815: Fix Version/s: 4.0.0 > Whitelist CVE-2016-6811 > --- > >

Re: [Feature Proposal] Add metrics dropwizards like gauges, meters, histogram etc to Apex Platform

+1 for the #1 proposal. Thank you, Vlad On 5/9/18 07:14, Thomas Weise wrote: +1 for the initiative Some thoughts: - it is probably good to retain a level of abstraction, to avoid direct dependency on dropwizard - support programmatic metric creation (not just annotations) - remove

Re: Apex-core build/release steps improvements proposal

+1 to all 3. Thank you, Vlad On 5/3/18 07:03, Thomas Weise wrote: +1 to all of this There are existing JIRAs that you can assign / add to: https://issues.apache.org/jira/browse/APEXCORE-727 Thanks! On Thu, May 3, 2018 at 4:26 AM, Chinmay Kolhatkar wrote: Hello

Re: project dependencies - important

For netlet we can either move it to apex-core (it will require package name change and major version update) or keep it in public github repository. Other libraries are available on maven central and I see that you already open a PR (+1). Thank you, Vlad On 5/2/18 19:38, Thomas Weise wrote:

[jira] [Resolved] (APEXCORE-808) Change min supported java version dependency to Java 8

[ https://issues.apache.org/jira/browse/APEXCORE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-808. - Resolution: Implemented > Change min supported java version dependency to Jav

[jira] [Assigned] (APEXCORE-808) Change min supported java version dependency to Java 8

[ https://issues.apache.org/jira/browse/APEXCORE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov reassigned APEXCORE-808: --- Assignee: Vlad Rozov > Change min supported java version dependency to Jav

Re: [VOTE] Apache Apex Core Release 3.7.0 (RC1)

+1 (binding). - verified release signature and hashes - "mvn clean apache-rat:check verify -Dlicense.skip=false install -Dmaven.repo.local=" runs clean on my machine - verified NOTICE, LICENSE, CHANGELOG.md and README.md - checked DEPENDENCIES - no unexpected binary/jar files I deleted .md5

Re: [VOTE] Apache Apex Core Release 3.7.0 (RC1)

Please fix the KEYS before proceeding with the vote. Thank you, Vlad On 4/14/18 11:48, Pramod Immaneni wrote: Dear Community, Please vote on the following Apache Apex Core 3.7.0 release candidate. This is a source release with binary artifacts published to Maven. List of all issues fixed:

Re: Core release 3.7.0

release.html Thanks On Mon, Apr 9, 2018 at 1:45 PM, Vlad Rozov <vro...@apache.org> wrote: What was the reason to create the branch? Usually there is no branch created, only tag. Thank you, Vlad On 4/9/18 08:32, Pramod Immaneni wrote: The branch release-3.7 has been created and maste

Re: Core release 3.7.0

ni < pra...@datatorrent.com> wrote: I can do it if no one is volunteering. Thanks On Jan 31, 2018, at 7:59 AM, Thomas Weise <t...@apache.org> wrote: We are still looking for a volunteer to run the release.. On Fri, Jan 19, 2018 at 8:32 AM, Vlad Rozov < vro...@apache.org> wr

Re: Core release 3.7.0

t 9:06 AM, Pramod Immaneni < pra...@datatorrent.com> wrote: I can do it if no one is volunteering. Thanks On Jan 31, 2018, at 7:59 AM, Thomas Weise <t...@apache.org> wrote: We are still looking for a volunteer to run the release.. On Fri, Jan 19, 2018 at 8:32 AM, Vlad Rozov < vr

[jira] [Resolved] (APEXCORE-806) Upgrade org.owasp:dependency-check-maven

[ https://issues.apache.org/jira/browse/APEXCORE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-806. - Resolution: Done Fix Version/s: 3.7.0 > Upgrade org.owasp:dependency-check-ma

[jira] [Updated] (APEXCORE-806) Upgrade org.owasp:dependency-check-maven

[ https://issues.apache.org/jira/browse/APEXCORE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-806: Issue Type: Dependency upgrade (was: Bug) > Upgrade org.owasp:dependency-check-ma

[jira] [Created] (APEXCORE-806) Upgrade org.owasp:dependency-check-maven

Vlad Rozov created APEXCORE-806: --- Summary: Upgrade org.owasp:dependency-check-maven Key: APEXCORE-806 URL: https://issues.apache.org/jira/browse/APEXCORE-806 Project: Apache Apex Core Issue

[jira] [Updated] (APEXMALHAR-2557) TimeBasedDedupOperator fails with NullPointer

[ https://issues.apache.org/jira/browse/APEXMALHAR-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXMALHAR-2557: --- Fix Version/s: 4.0.0 > TimeBasedDedupOperator fails with NullPoin

[jira] [Updated] (APEXMALHAR-2557) TimeBasedDedupOperator fails with NullPointer

[ https://issues.apache.org/jira/browse/APEXMALHAR-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXMALHAR-2557: --- Description: While using the TimeBasedDedupOperator for deduping, I see that operator

[jira] [Updated] (APEXMALHAR-2557) TimeBasedDedupOperator fails with NullPointer

[ https://issues.apache.org/jira/browse/APEXMALHAR-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXMALHAR-2557: --- Description: While using the TimeBasedDedupOperator for deduping, I see that operator

[jira] [Commented] (APEXCORE-805) There are dependency conflicts in apex-core/engine module

[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373018#comment-16373018 ] Vlad Rozov commented on APEXCORE-805: - [~PandaMonkey] Conflict with {{org.eclipse.jetty:jetty

[jira] [Commented] (APEXCORE-805) There are dependency conflicts in apex-core/engine module

[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370703#comment-16370703 ] Vlad Rozov commented on APEXCORE-805: - [~PandaMonkey] exclude {{test}} scope from your analysis

[jira] [Updated] (APEXCORE-805) There are dependency conflicts in apex-core/engine module

[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-805: Fix Version/s: (was: 3.6.1) > There are dependency conflicts in apex-core/engine mod

[jira] [Updated] (APEXCORE-805) There are dependency conflicts in apex-core/engine module

[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-805: Priority: Minor (was: Major) > There are dependency conflicts in apex-core/engine mod

Re: [Proposal] Extension of the Apex configuration to add dependent jar files in runtime.

the run-time configuration of Apex applications. It means the plugins cannot be a part of the system configuration of the platform. Thanks, Sergey On Mon, Feb 5, 2018 at 9:39 AM, Vlad Rozov <vro...@apache.org> wrote: Apex platform dependencies are already covered with the compile time

Re: [Proposal] Extension of the Apex configuration to add dependent jar files in runtime.

Immaneni <pra...@datatorrent.com> wrote: Yes generic in the Attribute class On Feb 3, 2018, at 10:00 AM, Vlad Rozov <vro...@apache.org> wrote: +1 assuming that support for merge/override will be generic for all attributes that support list/set of values and not limited to LIBRARY_JA

Re: [Proposal] Extension of the Apex configuration to add dependent jar files in runtime.

. On Fri, Feb 2, 2018 at 6:32 PM, Vlad Rozov <vro...@apache.org> wrote: IMO, support for Kubernetes, Docker images, Mesos and anything outside of Yarn deployments is a topic by itself and design for such support needs to be discussed. I do not want to propose any specific design, but

Re: [Proposal] Extension of the Apex configuration to add dependent jar files in runtime.

n, the current static approach in Apex code to hardcode a list of dependent jars will not work anymore. It will require to include a new solution to add/change jars in specific Apex builds/configurations. And I don't think the usage of the plugins will be good for that. Thanks, Sergey On T

Re: [Proposal] Extension of the Apex configuration to add dependent jar files in runtime.

There is a way to get the same end result by using plugins. It will be good to understand why plugin can't be used and can they be extended to provide the required functionality. Thank you, Vlad On 1/29/18 15:14, Sergey Golovko wrote: Hello All, In Apex there are two ways to deploy

[jira] [Resolved] (APEXCORE-803) Update archetype version number in setup guide

[ https://issues.apache.org/jira/browse/APEXCORE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-803. - Resolution: Fixed > Update archetype version number in setup gu

[jira] [Resolved] (APEXCORE-802) Upgrade Malhar version in archetype to 3.8.0

[ https://issues.apache.org/jira/browse/APEXCORE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-802. - Resolution: Fixed > Upgrade Malhar version in archetype to 3.

Re: [Proposal] Switch to Java 8

tart using some java 9 features in the code.. otherwise wouldn’t something built with java 8 automatically work with java 9. On Jan 19, 2018, at 1:29 PM, Vlad Rozov <vro...@apache.org> wrote: Yes, support for Java 9 does not mean that support for Java 8 is dropped. Thank you, Vlad

Re: [Proposal] Switch to Java 8

9, 2018, at 8:31 AM, Vlad Rozov <vro...@apache.org> wrote: +1. It will be good to start supporting Java 9. Thank you, Vlad On 1/18/18 11:01, Hitesh Kapoor wrote: +1. --Hitesh

Re: Core release 3.7.0

+1. Should be the last release to support Java 7. Thank you, Vlad On 1/18/18 18:45, Bhupesh Chawda wrote: +1 for release ~ Bhupesh On Jan 19, 2018 12:14 AM, "Ananth G" wrote: +1 for the release. Regards, Ananth On Fri, Jan 19, 2018 at 4:41 AM, Chinmay Kolhatkar

Re: [Proposal] Switch to Java 8

+1. It will be good to start supporting Java 9. Thank you, Vlad On 1/18/18 11:01, Hitesh Kapoor wrote: +1. --Hitesh On Fri, Jan 19, 2018 at 12:28 AM, Ananth G wrote: Hello All, I was wondering if we can consider making java 8 as the minimum supported idk version

[jira] [Resolved] (APEXCORE-795) Update NOTICE copyright year

[ https://issues.apache.org/jira/browse/APEXCORE-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-795. - Resolution: Done Fix Version/s: 3.7.0 > Update NOTICE copyright y

[jira] [Resolved] (APEXMALHAR-2517) Relocate classes to org.apache.apex packages

[ https://issues.apache.org/jira/browse/APEXMALHAR-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXMALHAR-2517. Resolution: Done Fix Version/s: 4.0.0 > Relocate classes to org.apache.a

Re: [Proposal] Simulate setting for application launch

an alternate solution, so -0.5. Thank you, Vlad On 12/22/17 11:50, Pramod Immaneni wrote: On Fri, Dec 22, 2017 at 8:19 AM, Vlad Rozov <vro...@apache.org> wrote: I don't see more complexity in implementing a plugin compared to implementing an application. Additionally, for the use case you m

Re: [Proposal] Simulate setting for application launch

with these so they can create the dag accordingly. One example is a websocket gateway address. If this is present applications create a websocket output operator else they end up create a console or some other output operator. On Thu, Dec 21, 2017 at 8:27 AM, Vlad Rozov <vro...@apache.org>

Re: [Proposal] Simulate setting for application launch

2017 at 2:28 PM, Vlad Rozov <vro...@apache.org> wrote: -0.5: populateDAG() may be called by the platform as many times as it needs (even in case it calls it only once now to launch an application). Passing different parameters to populateDAG() in simulate launch mode and actual launch may

Re: [Proposal] Simulate setting for application launch

-0.5: populateDAG() may be called by the platform as many times as it needs (even in case it calls it only once now to launch an application). Passing different parameters to populateDAG() in simulate launch mode and actual launch may lead to different DAG being constructed for those two

[jira] [Resolved] (APEXCORE-798) Exclude log4j.properties from engine-test.jar

[ https://issues.apache.org/jira/browse/APEXCORE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-798. - Resolution: Fixed Fix Version/s: 3.7.0 > Exclude log4j.properties from engine-test.

Re: checking dependencies for known vulnerabilities

Please see PR https://github.com/apache/apex-core/pull/585 comments and APEXCORE-790 for the further discussion and the resolution. There is still one open item - updating contributor/committer guidelines if someone wants to help with it. Thank you, Vlad On 11/2/17 16:55, Vlad Rozov wrote

[jira] [Updated] (APEXCORE-799) Fix documentation for release process instructions

[ https://issues.apache.org/jira/browse/APEXCORE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-799: Priority: Minor (was: Major) > Fix documentation for release process instructi

[jira] [Updated] (APEXCORE-797) Download page must not link to dist.apache.org

[ https://issues.apache.org/jira/browse/APEXCORE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-797: Priority: Minor (was: Major) > Download page must not link to dist.apache.

[jira] [Created] (APEXCORE-800) Disable the disk health checker service for StramMiniClusterTest

Vlad Rozov created APEXCORE-800: --- Summary: Disable the disk health checker service for StramMiniClusterTest Key: APEXCORE-800 URL: https://issues.apache.org/jira/browse/APEXCORE-800 Project: Apache

[jira] [Updated] (APEXCORE-798) Exclude log4j.properties from engine-test.jar

[ https://issues.apache.org/jira/browse/APEXCORE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-798: Description: log4j.properties is supposed to be excluded from the engine test jar based

[jira] [Created] (APEXCORE-798) Exclude log4j.properties from engine-test.jar

Vlad Rozov created APEXCORE-798: --- Summary: Exclude log4j.properties from engine-test.jar Key: APEXCORE-798 URL: https://issues.apache.org/jira/browse/APEXCORE-798 Project: Apache Apex Core

Re: [VOTE] Apache Apex Malhar 3.8.0 release candidate RC1

changes tonight. ( another 12 hours from now ). Regards, Ananth On 6 Nov 2017, at 3:44 am, Vlad Rozov <vro...@apache.org> wrote: Hi Ananth, There is new requirement [1], [2] for Apache releases to use .sha512 extension that is not yet reflected by Apex release guidelines. Can you

Re: [VOTE] Apache Apex Malhar 3.8.0 release candidate RC1

will include the above as well. Yes, it will be nice to update the release guidelines I would be able to push the above changes tonight. ( another 12 hours from now ). Regards, Ananth On 6 Nov 2017, at 3:44 am, Vlad Rozov <vro...@apache.org> wrote: Hi Ananth, There is new requirem

Re: [VOTE] Apache Apex Malhar 3.8.0 release candidate RC1

Hi Ananth, There is new requirement [1], [2] for Apache releases to use .sha512 extension that is not yet reflected by Apex release guidelines. Can you please update extension. Thank you, Vlad [1] http://www.apache.org/dev/release-distribution [2]

[jira] [Resolved] (APEXCORE-791) Gateway security settings need to be available in the DAG

[ https://issues.apache.org/jira/browse/APEXCORE-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-791. - Resolution: Fixed Fix Version/s: 3.7.0 > Gateway security settings need to be availa

[jira] [Updated] (APEXCORE-791) Gateway security settings need to be available in the DAG

[ https://issues.apache.org/jira/browse/APEXCORE-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-791: Priority: Minor (was: Major) > Gateway security settings need to be available in the

[jira] [Created] (APEXCORE-793) Revisit PubSubWebSocketClient and SharedPubSubWebSocketClient

Vlad Rozov created APEXCORE-793: --- Summary: Revisit PubSubWebSocketClient and SharedPubSubWebSocketClient Key: APEXCORE-793 URL: https://issues.apache.org/jira/browse/APEXCORE-793 Project: Apache Apex

Re: Malhar release 3.8.0

Sorry, I don't fully understand your point. Is the suggestion not to add maven plugin and only rely on manual sanity check or do extra manual sanity check on top of the plugin? Any reason not to go with the second approach? Thank you, Vlad On 11/3/17 08:36, Justin Mclean wrote: Hi, The

Re: checking dependencies for known vulnerabilities

ink.. at this point I am -1 on merging the change as is that would fail all PR builds when a matching CVE is discovered regardless of whether the PR was the cause of the CVE or not. On Wed, Nov 1, 2017 at 12:07 PM, Vlad Rozov <vro...@apache.org> wrote: On 11/1/17 11:39, Pramod Immaneni

  1   2   3   4   5   6   7   8   >