[RESULT] [VOTE] Move Apex to the Apache Attic

This vote to move Apex to the Attic has concluded as following: 6 x +1 for moving to Apache Attic: Atri Sharma Vlad Rozov (binding) David Yan (binding) Ilya Ganelin (binding) Hitesh Shah (binding) Thomas Weise (binding) No other votes. According to [1], I will add the resolution to the next

Re: [VOTE] Move Apex to the Apache Attic

+1 > > > > > > On Fri, Aug 16, 2019, 1:50 PM Vlad Rozov wrote: > > > > > > > +1 > > > > > > > > Thank you, > > > > > > > > Vlad > > > > > > > > > On Aug 13, 2019, at 19:22, Atri Sharma

[VOTE] Move Apex to the Apache Attic

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 interest to possibly contribute and there were also at least two PMC members not in favor of the move. Since then the project was mostly inactive, no code

Re: support Hadoop 3.X

For the upgrade it is probably best when you change the version number in [1] and then work through the build issues. I would expect a number of dependency changes since the client classpath now has the Hadoop transitive dependencies shaded away [2]. Regarding the development process, see [3].

Board report draft January 2019

Open for feedback/comments until tomorrow (due for submission today): https://docs.google.com/document/d/1TKHKI_4htvoIHYu4S7q5HuaX-2eUuW-d5pQUtsWTrBs/edit?usp=sharing

Re: Salesforce operator

t are helpful. > > > > > > 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 > > >&g

Re: [DISCUSS] Time for attic?

Quite satisfying to see this spike of mailing list activity! Didn't expect we still had so many subscribers and "attic" seems to be a strong keyword :) Aaron, thanks for refreshing my memory! I'm also not aware of any other project supporting on the fly topology changes. It's a capability that

Re: [DISCUSS] Time for attic?

Thanks for the actionable input. I would suggest you try to contribute back. From my end I'm happy to support that as reviewer or in advisory capacity. If multiple folks maintaining private forks were to contribute back, the cost equation was more attractive (you benefit from other contributions

Re: [DISCUSS] Time for attic?

I think it would be constructive to find answers to relevant questions that came up: * Who is going to contribute to the project? * Is there code in private forks that can be contributed? * What is the estimated timeline for such contributions? * Are there any other opportunities to

Re: [DISCUSS] Time for attic?

According to [1] projects that have no active committers are good candidates for the attic. The last commit in Apex was in June 2018, which is a very long time ago. No activity other than this attic discussion on dev@ for 3 months and one lonely email on users@. Do those that are not ready to

Re: [DISCUSS] Time for attic?

A shame it would be and sad for those of us who have put a lot of effort into the project. But not surprising to have reached this point at all. We should face reality or not? The crux of the matter is that Apache projects are community first and not a parking lot for code bases. Apex code base

[jira] [Closed] (APEXCORE-321) Document voting rules

[ https://issues.apache.org/jira/browse/APEXCORE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXCORE-321. - Resolution: Won't Do Assignee: (was: Thomas Weise) > Document voting ru

[jira] [Commented] (APEXCORE-796) Docker based deployment

[ https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553687#comment-16553687 ] Thomas Weise commented on APEXCORE-796: --- Completely agree. There is no need to invest effort

[jira] [Commented] (APEXCORE-796) Docker based deployment

[ https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553680#comment-16553680 ] Thomas Weise commented on APEXCORE-796: --- The ability for Apex to be packaged as and run

[jira] [Commented] (APEXCORE-796) Docker based deployment

[ https://issues.apache.org/jira/browse/APEXCORE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551795#comment-16551795 ] Thomas Weise commented on APEXCORE-796: --- That's great! Perhaps send an email to the list

Re: Board report draft July 2018

The report has been submitted. On Wed, Jul 4, 2018 at 12:33 PM Thomas Weise wrote: > Hi, > > Here is the report draft, please add suggestions/comments before July 9th: > > > https://docs.google.com/document/d/10zzIzX6CnHzuN8CiujCm0pDLoXxHiapMc_dDKhujsE4/edit?usp=sharing > > Thanks, > Thomas > >

Board report draft July 2018

Hi, Here is the report draft, please add suggestions/comments before July 9th: https://docs.google.com/document/d/10zzIzX6CnHzuN8CiujCm0pDLoXxHiapMc_dDKhujsE4/edit?usp=sharing Thanks, Thomas

Re: [Feature Proposal] Move Apache Apex website to Jekyll

to ci.apache.org). I will > cut down the top level menu of "Ecosystem". Is there anything else that you > see as crowded ? Also could you please point out what are the > considerations for Apache Theme ? > > I have only seen two votes and hence I am in a dilemma whether I take this >

Re: [Feature Proposal] Move Apache Apex website to Jekyll

+1 for website revamp with Jekyll. Regarding the details: Documentation is a release artifact that needs to remain decoupled from other web site content. I would propose to keep the documentation build/release process out of this effort. The top level navigation looks a bit crowded. I would

Re: Proposal for UI component in stram

Looks like there is some disconnect in this thread, a few replies express concerns that the proposal IMO doesn't imply. There is already a REST API that backs all of the CLI functionality. Modern UIs run in the browser, and so what was proposed (unless I misunderstood) would be based on the same

Re: Proposal for UI component in stram

strong +1 for adding a UI to Apex. This is actually something that users expect and are accustomed to with similar projects. Thanks for taking the initiative. There are nuances to be discussed, but the overall plan LGTM. To your question, I think this should use the existing web port with a

[ANNOUNCE] New Apache Apex PMC Member: Chinmay Kolhatkar

The Apache Apex PMC is pleased to announce that Chinmay Kolhatkar is now a PMC member. Chinmay has contributed to Apex in many ways, including: - Various transform operators in Malhar - SQL translation based on Calcite - Apache Bigtop integration - Docker sandbox - Blogs and conference

Re: Hello Apex Devs!

Hi Shubhrajyoti, Welcome! To get started, I would recommend to take a look at http://apex.apache.org/community.html http://apex.apache.org/contributing.html Then, unless you already found something to work on, consider picking a starter JIRA

Re: Your buildbot script apex.conf

Earlier it wasn't possible to build on a new commit, it currently runs nightly whether needed or not. On Tue, May 22, 2018 at 9:18 AM, Vlad Rozov wrote: > line 217 where and how that affects Apex in a practical way. > > Thank you, > > Vlad > > > On 5/22/18 07:19, sebb wrote:

Re: [DISCUSS] Maven version

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 wrote: > Note that the question is regarding the lowest version and > functionality/plugins it supports. A developer may install any later >

[jira] [Commented] (APEXCORE-569) Fix javadoc errors uncovered by Java 8

[ https://issues.apache.org/jira/browse/APEXCORE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477487#comment-16477487 ] Thomas Weise commented on APEXCORE-569: --- The change above was to suppress the lint errors. Keeping

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

[ https://issues.apache.org/jira/browse/APEXCORE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-815. --- Resolution: Fixed > Whitelist CVE-2016-6

[jira] [Resolved] (APEXCORE-811) Move docker build sourcecode from private repository to apex-core repo

[ https://issues.apache.org/jira/browse/APEXCORE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-811. --- Resolution: Fixed Fix Version/s: 4.0.0 > Move docker build sourcecode from priv

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

o. This will > act as a pilot for building docker from apex-core repo as well. Let me know > if this is fine. > > Regards, > Chinmay. > > > On Tue, 8 May 2018, 8:30 pm Thomas Weise, <t...@apache.org> wrote: > > > The md5 related change needs to be reflected o

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

+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 deprecated counter and auto-metric code and migrate operators to use new API - which metric

REST server for Apex application management

Hi, I wanted to make you aware that there is a base implementation for a REST service to manage Apex applications here: https://github.com/atrato/atrato-server It is ASL and everyone is welcome to use it or contribute to it. If there is sufficient interest it can also be discussed to add it to

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

... On Tue, Apr 24, 2018 at 9:51 AM, Pramod Immaneni <pra...@datatorrent.com> wrote: > Yes Thomas will complete it in a day or two. > > Thanks > > On Tue, Apr 24, 2018 at 9:15 AM, Thomas Weise <t...@apache.org> wrote: > > > Hi Pramod, > > > > Are y

Re: Apex-core build/release steps improvements proposal

well. Perhaps we will address these questions as > part of https://issues.apache.org/jira/browse/APEXCORE-724 and > https://issues.apache.org/jira/browse/APEXCORE-796. > > Regards, > Ananth > > On Fri, May 4, 2018 at 10:31 AM, Vlad Rozov <vro...@apache.org> wrote: > &g

[jira] [Commented] (APEXCORE-813) Update docker build steps to use apex bin dist package

[ https://issues.apache.org/jira/browse/APEXCORE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467492#comment-16467492 ] Thomas Weise commented on APEXCORE-813: --- I would prefer the ability to create images from

[jira] [Resolved] (APEXCORE-727) Create and publish binary releases along with the source releases

[ https://issues.apache.org/jira/browse/APEXCORE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-727. --- Resolution: Implemented Fix Version/s: 4.0.0 > Create and publish binary relea

[jira] [Resolved] (APEXCORE-728) Include licenses for dependencies

[ https://issues.apache.org/jira/browse/APEXCORE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-728. --- Resolution: Implemented > Include licenses for dependenc

[jira] [Resolved] (APEXCORE-731) Modifications to the build to generate binary package

[ https://issues.apache.org/jira/browse/APEXCORE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-731. --- Resolution: Implemented > Modifications to the build to generate binary pack

Re: project dependencies - important

ay, May 3, 2018, 9:46:04 AM PDT, Thomas Weise <t...@apache.org> > wrote: > > Pramod, > > There are several Apex related blogs on the DT web site that are referenced > from http://apex.apache.org/docs.html (there are probably a few more, but > that should be easy to identi

[jira] [Commented] (APEXCORE-729) Include an example in the release

[ https://issues.apache.org/jira/browse/APEXCORE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463340#comment-16463340 ] Thomas Weise commented on APEXCORE-729: --- Yes, how to tackle examples can be taken up separately

Re: project dependencies - important

vailable 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: > > > >> That one is not needed and I think we can nuke the zmq operator also. > >&

Re: Apex-core build/release steps improvements proposal

+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 Community, > > I want to propose following improvements for apex-core

Re: project dependencies - important

https://github.com/apache/apex-malhar/pull/685 Dependencies available from elsewhere. On Wed, May 2, 2018 at 7:38 PM, Thomas Weise <t...@apache.org> wrote: > That one is not needed and I think we can nuke the zmq operator also. > > R has an example, so we might want to fin

Re: project dependencies - important

gt; > Thanks > > On Wed, May 2, 2018 at 7:05 PM, Thomas Weise <t...@apache.org> wrote: > > > Hi Pramod, > > > > Thanks for the headsup. > > > > Do you have the list of malhar dependencies that live in the DT server? > > > > I remember R and

Re: project dependencies - important

Hi Pramod, Thanks for the headsup. Do you have the list of malhar dependencies that live in the DT server? I remember R and zmq, anything else? Thanks, Thomas On Wed, May 2, 2018 at 6:53 PM, Pramod Immaneni wrote: > Hello Community, > > As you may know, DataTorrent

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

Hi Pramod, Are you going to complete the release? Thanks On Wed, Apr 18, 2018 at 9:31 PM, Pramod Immaneni <pra...@datatorrent.com> wrote: > The vote concludes and passes. > > binding +1 (3) > > Justin Mclean > Vlad Rozov > Thomas Weise > > Will comple

[jira] [Commented] (APEXCORE-809) Documentation does not build with current versions (8.11.x) of nodejs

[ https://issues.apache.org/jira/browse/APEXCORE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447101#comment-16447101 ] Thomas Weise commented on APEXCORE-809: --- Since the user docs are generated with mkdocs I assume

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

+1 (binding) - verified signatures - build from source archive - tests pass - run pi demo on YARN 2.7.1 When updating the download page after the release, please also remove the md5 links from it. Thanks, Thomas On Sat, Apr 14, 2018 at 11:48 AM, Pramod Immaneni wrote:

Re: Core release 3.7.0

t; > > > > On 4/9/18 16:13, Pramod Immaneni wrote: > > > >> I lost my gpg key and had to generate a new one, folks please sign it > when > >> you can. > >> > >> http://pgp.mit.edu/pks/lookup?op=get=0x79480420239E728D > >> > >>

Re: Core release 3.7.0

> > On 4/9/18 08:32, Pramod Immaneni wrote: > > > >> The branch release-3.7 has been created and master changed to > >> 3.8.0-SNAPSHOT. > >> > >> On Fri, Apr 6, 2018 at 1:03 PM, Pramod Immaneni <pra...@datatorrent.com > > > >> wrote

Re: Core release 3.7.0

Thanks > > On Sat, Feb 24, 2018 at 5:16 AM, Pramod Immaneni <pra...@datatorrent.com> > wrote: > > > ok > > > > On Mon, Feb 19, 2018 at 1:30 PM, Thomas Weise <t...@apache.org> wrote: > > > >> I think that should be done after the release, along

Fwd: "Standardizing" streaming SQL

Streaming SQL is an area of growing interest and several projects are moving forward supporting more functionality like windowing and also improving the tooling around it. Much of that work is driven or inspired by Apache Calcite. The arrival of a new effort to define a TCK is an exciting and

Re: Core release 3.7.0

rrent.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.. > &

[jira] [Assigned] (APEXCORE-224) Cleanup testAppPackage.mydtapp

[ https://issues.apache.org/jira/browse/APEXCORE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise reassigned APEXCORE-224: - Assignee: (was: Thomas Weise) > Cleanup testAppPackage.mydt

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

The current dependencies are based on how Apex YARN client works. YARN depends on a DFS implementation for deployment (not necessarily HDFS). I think a better way to look at this is to consider that instead of an .apa file the application is a docker image, which would contain Apex and all

Re: Core release 3.7.0

t;>> >>>> +1 for the release >>>>> >>>>> Regards, >>>>> - Tushar. >>>>> >>>>> >>>>> On Thu, Jan 18, 2018 at 3:28 AM, Amol Kekre <a...@datatorrent.com> >>>>> >>>> wrote: >

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

Thomas Weise created APEXCORE-803: - Summary: Update archetype version number in setup guide Key: APEXCORE-803 URL: https://issues.apache.org/jira/browse/APEXCORE-803 Project: Apache Apex Core

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

Thomas Weise created APEXCORE-802: - Summary: Upgrade Malhar version in archetype to 3.8.0 Key: APEXCORE-802 URL: https://issues.apache.org/jira/browse/APEXCORE-802 Project: Apache Apex Core

Core release 3.7.0

Last release was 3.6.0 in May and following issues are ready for release: https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.7.0%20AND%20project%20%3D%20APEXCORE%20ORDER%20BY%20status%20ASC Any opinions on cutting a release? Any committer interested running the release? Thanks,

[jira] [Created] (APEXMALHAR-2554) Change artifactId for Kafka 0.9 connector to malhar-kafka09

Thomas Weise created APEXMALHAR-2554: Summary: Change artifactId for Kafka 0.9 connector to malhar-kafka09 Key: APEXMALHAR-2554 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2554 Project

[jira] [Closed] (APEXMALHAR-2094) Quantiles sketch operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXMALHAR-2094. Resolution: Won't Do > Quantiles sketch opera

[jira] [Closed] (APEXMALHAR-1909) Fix existing checkstyle violations in Malhar

[ https://issues.apache.org/jira/browse/APEXMALHAR-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXMALHAR-1909. Resolution: Done Fix Version/s: 4.0.0 > Fix existing checkstyle violati

Re: [Discuss] Design of the python execution operator

ocker approach ticket should be the > right fix for virtual environments issue? https://issues.apache.org/ > jira/browse/APEXCORE-796 <https://issues.apache.org/ > jira/browse/APEXCORE-796> ( but still might not solve the thread local > configuration deployment ) > > > > Re

[jira] [Closed] (APEXCORE-801) Committer guidelines for dependency CVE failures

[ https://issues.apache.org/jira/browse/APEXCORE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXCORE-801. - > Committer guidelines for dependency CVE failu

[jira] [Updated] (APEXCORE-801) Committer guidelines for dependency CVE failures

[ https://issues.apache.org/jira/browse/APEXCORE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXCORE-801: -- Fix Version/s: (was: 3.7.0) > Committer guidelines for dependency CVE failu

[jira] [Closed] (APEXMALHAR-2034) Avro File To POJO Module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXMALHAR-2034. Resolution: Incomplete > Avro File To POJO Mod

Re: [Discuss] Design of the python execution operator

It is exciting to see this move forward, the ability to use Python opens many new possibilities. Regarding use of worker threads, this is a pattern that we are using elsewhere (for example in the Kafka input operator). When the operator performs blocking operations and consumes little memory

[jira] [Resolved] (APEXMALHAR-2548) Pubsub operators do not use the correct URL to connect to web socket server in SSL mode

[ https://issues.apache.org/jira/browse/APEXMALHAR-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2548. -- Resolution: Fixed Fix Version/s: 3.9.0 4.0.0 > Pub

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

[ https://issues.apache.org/jira/browse/APEXCORE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-800. --- Resolution: Fixed Fix Version/s: 3.7.0 > Disable the disk health checker serv

[jira] [Resolved] (APEXMALHAR-2550) NycTaxiDataReader throws exception when encountering lines with unrecognized format in the NYC taxi example

[ https://issues.apache.org/jira/browse/APEXMALHAR-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2550. -- Resolution: Fixed Fix Version/s: 3.9.0 4.0.0

[jira] [Resolved] (APEXCORE-767) Duplicate class loading in CLI for single application launch

[ https://issues.apache.org/jira/browse/APEXCORE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-767. --- Resolution: Fixed Fix Version/s: 3.7.0 > Duplicate class loading in CLI for sin

[jira] [Created] (APEXCORE-796) Docker based deployment

Thomas Weise created APEXCORE-796: - Summary: Docker based deployment Key: APEXCORE-796 URL: https://issues.apache.org/jira/browse/APEXCORE-796 Project: Apache Apex Core Issue Type: New

[jira] [Closed] (APEXCORE-794) Release guidelines show incorrect sha extension and other minor updates

[ https://issues.apache.org/jira/browse/APEXCORE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXCORE-794. - Resolution: Fixed Fix Version/s: (was: 3.7.0) > Release guidelines show incorr

[jira] [Assigned] (APEXCORE-794) Release guidelines show incorrect sha extension and other minor updates

[ https://issues.apache.org/jira/browse/APEXCORE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise reassigned APEXCORE-794: - Assignee: Ananth > Release guidelines show incorrect sha extension and other mi

Re: Process to push the documentation into ASF-site before vote for a release

Done: http://apex.apache.org/docs/malhar-3.8/ The docs just were not published (see link below the instructions that you executed). On Sun, Nov 5, 2017 at 3:20 AM, Ananth G wrote: > Hello All, > > I am having an issue completing the last step of the release process >

[jira] [Resolved] (APEXMALHAR-2461) Fix dependencies on libraries licensed under Category X

[ https://issues.apache.org/jira/browse/APEXMALHAR-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2461. -- Resolution: Fixed > Fix dependencies on libraries licensed under Categor

[ANNOUNCE] New Apache Apex Committer: Ananth Gundabattula

The Project Management Committee (PMC) for Apache Apex is pleased to announce Ananth Gundabattula as new committer. Ananth has been contributing to the project for about a year. Highlights: * Cassandra and Kudu operators with in-depth analysis/design work * Good collaboration, adherence to

[jira] [Commented] (APEXMALHAR-2549) JdbcIOAppTest.testApplication is flaky

[ https://issues.apache.org/jira/browse/APEXMALHAR-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237217#comment-16237217 ] Thomas Weise commented on APEXMALHAR-2549: -- More frequent flakes

[jira] [Commented] (APEXMALHAR-2549) JdbcIOAppTest.testApplication is flaky

[ https://issues.apache.org/jira/browse/APEXMALHAR-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237203#comment-16237203 ] Thomas Weise commented on APEXMALHAR-2549: -- It is no surprise that this test fails randomly

Re: checking dependencies for known vulnerabilities

might still be useful to fix a CVE even if there is no release, > downstream projects might be able to use it. > > On Thu, Nov 2, 2017 at 4:42 PM, Thomas Weise <t...@apache.org> wrote: > > > Check as part of PR build is needed to ensure no new issues are > introduced. &g

Re: checking dependencies for known vulnerabilities

;> On 3 Nov 2017, at 4:48 am, Sanjay Pujare <san...@datatorrent.com> > > wrote: > > >>> > > >>> I like this suggestion. Blocking the PR is too drastic. I also second > > >>> Pramod's point (made elsewhere) that we should try to encourage > > >>> contribution i

Re: Malhar release 3.8.0

; >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> On 10/25/17 15:28, Ananth G wrote: > >>>>>>>>>>> > >>>>>>>>>>> I would like to volunteer to be the rele

[jira] [Resolved] (APEXMALHAR-2547) Add ride data processing example to Apex Library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2547. -- Resolution: Implemented > Add ride data processing example to Apex Libr

Re: checking dependencies for known vulnerabilities

Considering typical behavior, unless the CI build fails, very few will be interested fixing the issues. Perhaps if after a CI failure the issue can be identified as pre-existing, we can whitelist and create a JIRA that must be addressed prior to the next release? On Wed, Nov 1, 2017 at 7:51 PM,

[jira] [Created] (APEXMALHAR-2549) JdbcIOAppTest.testApplication is flaky

Thomas Weise created APEXMALHAR-2549: Summary: JdbcIOAppTest.testApplication is flaky Key: APEXMALHAR-2549 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2549 Project: Apache Apex Malhar

Re: Malhar release 3.8.0

datatorrent.com | apex.apache.org >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 25, 2017 at 9:37 PM, Chinmay Kolhatkar < >>>>>>> chin...@datatorrent.com> >>>>>>>

[jira] [Commented] (APEXMALHAR-2461) Fix dependencies on libraries licensed under Category X

[ https://issues.apache.org/jira/browse/APEXMALHAR-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225559#comment-16225559 ] Thomas Weise commented on APEXMALHAR-2461: -- If the dependency is not strictly needed

[jira] [Updated] (APEXMALHAR-2498) Kafka exactly once output test CI failure

[ https://issues.apache.org/jira/browse/APEXMALHAR-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2498: - Fix Version/s: (was: 3.8.0) 3.9.0 > Kafka exactly once out

[jira] [Resolved] (APEXMALHAR-2462) Move JDBC related examples from datatorrent examples to apex-malhar examples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2462. -- Resolution: Incomplete > Move JDBC related examples from datatorrent examp

[jira] [Commented] (APEXMALHAR-2462) Move JDBC related examples from datatorrent examples to apex-malhar examples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225543#comment-16225543 ] Thomas Weise commented on APEXMALHAR-2462: -- Unfinished work (see PR): {quote} Package should

[jira] [Updated] (APEXMALHAR-2499) Hive test fails in dependency resolution (Travis CI)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2499: - Fix Version/s: (was: 3.8.0) > Hive test fails in dependency resolution (Tra

[jira] [Updated] (APEXMALHAR-2499) Hive test fails in dependency resolution (Travis CI)

[ https://issues.apache.org/jira/browse/APEXMALHAR-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2499: - Labels: newbie (was: ) > Hive test fails in dependency resolution (Travis

Malhar release 3.8.0

The last release was back in March, there are quite a few JIRAs that have been completed since and should be released. https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.8.0%20AND%20project%20%3D%20APEXMALHAR%20ORDER%20BY%20status%20ASC >From looking at the list there is nothing

[jira] [Closed] (APEXCORE-787) Add inactive PR policy to contribution guidelines

[ https://issues.apache.org/jira/browse/APEXCORE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise closed APEXCORE-787. - Resolution: Done > Add inactive PR policy to contribution guideli

[jira] [Resolved] (APEXMALHAR-2532) Transform Application Test flooding CI logs

[ https://issues.apache.org/jira/browse/APEXMALHAR-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2532. -- Resolution: Fixed Fix Version/s: 3.8.0 > Transform Application T

[jira] [Assigned] (APEXMALHAR-2532) Transform Application Test flooding CI logs

[ https://issues.apache.org/jira/browse/APEXMALHAR-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise reassigned APEXMALHAR-2532: Assignee: Ananth (was: Shunxin Lu) > Transform Application Test flooding

[jira] [Commented] (APEXMALHAR-2544) Flume test leads to Travis timeout

[ https://issues.apache.org/jira/browse/APEXMALHAR-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193578#comment-16193578 ] Thomas Weise commented on APEXMALHAR-2544: -- workaround in https://github.com/apache/apex

[jira] [Resolved] (APEXMALHAR-2542) enricher.ApplicationTest access to hard coded /tmp location

[ https://issues.apache.org/jira/browse/APEXMALHAR-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2542. -- Resolution: Fixed Fix Version/s: 3.8.0 > enricher.ApplicationTest acc

[jira] [Resolved] (APEXMALHAR-2472) Implement Kudu Input Operator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXMALHAR-2472. -- Resolution: Implemented Fix Version/s: 3.8.0 > Implement Kudu In

[jira] [Commented] (APEXMALHAR-2542) enricher.ApplicationTest access to hard coded /tmp location

[ https://issues.apache.org/jira/browse/APEXMALHAR-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181517#comment-16181517 ] Thomas Weise commented on APEXMALHAR-2542: -- The output is also written to the invalid

[jira] [Commented] (APEXMALHAR-2542) enricher.ApplicationTest access to hard coded /tmp location

[ https://issues.apache.org/jira/browse/APEXMALHAR-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181500#comment-16181500 ] Thomas Weise commented on APEXMALHAR-2542: -- Please never use /tmp, but rather the Java tmp

  1   2   3   4   5   6   7   8   9   10   >