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

2018-06-18 Thread Aaron Bossert
tatsTest.testQueueSizeForContainerLocalOperators(StatsTest.java:285) On Mon, Jun 18, 2018 at 1:20 PM Aaron Bossert wrote: > I recently attempted to update Kryo from 2.24.0 to 4.0.2 to address a > serialization issue related to support for Java Instant and a couple of > other classes that are suppo

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

2018-06-18 Thread Aaron Bossert
ush count expected:<1> but was:<2> at com.datatorrent.stram.StramRecoveryTest.testWriteAheadLog(StramRecoveryTest.java:326) -- M. Aaron Bossert (571) 242-4021 Punch Cyber Analytics Group

Re: Kryo version and default serializer

2018-06-19 Thread Aaron Bossert
e to where that is in the docs? On Mon, Jun 11, 2018 at 4:20 PM Aaron Bossert wrote: > Ah, you make a good point about the dev list...I am using IntelliJ on a > Mac. When I tried building without any changes, I also encountered > failures. I can re-run the non-modified sources to do a diff and see i

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

2018-06-20 Thread Aaron Bossert
tarted by an ex-DataTorrent employee a few days back on adding a basic > UI > > to Apex so maybe there is hope. > > > > Having said that a few of us long timers have stuck it out through thick > > and thin and willing to help whenever it is possible. > > > &g

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

2018-06-20 Thread Aaron Bossert
Sorry, a bit off topic, but what replaces com.datatorrent.api.StatsListener? It is marked as deprecated. On Wed, Jun 20, 2018 at 2:12 PM Aaron Bossert wrote: > I agree. I am porting a prototype that I built using Storm to Apex. The > runtime config changes were the impetus for the swit

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

2018-06-20 Thread Aaron Bossert
ersion. I will dig in more to see what is going on. > > On Tue, Jun 19, 2018 at 6:54 PM Aaron Bossert > wrote: > > > Pramod, > > > > Thanks for taking the time to help! > > > > Here is the output (just failed parts) when running full install (clean &g

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

2018-06-20 Thread Aaron Bossert
Immaneni wrote: > That would be awesome, it would be a good use case for the platform. > > On Wed, Jun 20, 2018 at 10:54 AM Aaron Bossert > wrote: > > > I'm with you. I'm hoping to have it underpin a fairly large network > > security pipeline... > > > > On

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

2018-06-20 Thread Aaron Bossert
Thanks! On Wed, Jun 20, 2018 at 2:28 PM Pramod Immaneni wrote: > I believe it is StatsListenerWithContext > > On Wed, Jun 20, 2018 at 11:25 AM Aaron Bossert > wrote: > > > Sorry, a bit off topic, but what replaces > > com.datatorrent.api.StatsListener?

Re: Kryo version and default serializer

2018-06-19 Thread Aaron Bossert
orking. Are you > looking for an alternative to this workaround and trying to set a default > serializer for all fields of type Instant (the field type you mentioned in > the earlier email) so that you don't have to set the annotation each time? > > Thanks > > On Tue, Jun 19, 2018 at 12:

Re: Kryo version and default serializer

2018-06-19 Thread Aaron Bossert
internal errors that are bubbling up to those test > failures but not getting logged. > > Thanks > > On Tue, Jun 19, 2018 at 7:54 PM Aaron Bossert > wrote: > >> P.S. I am happy to roll up my sleeves, but from my initial attempt, >> errors >> I was seeing were not obviou

Re: Kryo version and default serializer

2018-06-19 Thread Aaron Bossert
tracking some of those down too if it would be helpful... On Tue, Jun 19, 2018 at 10:48 PM Aaron Bossert wrote: > Pramod, > > In a nutshell, yes. I can set a @FieldSerializer to the fields in > question...the only one I have run into thus far is Instant...but it would > be gr

Apex current state and roadmap

2018-09-25 Thread Aaron Bossert
versions? -- M. Aaron Bossert (571) 242-4021 Punch Cyber Analytics Group

Re: support Hadoop 3.X

2019-01-15 Thread Aaron Bossert
: class org.apache.hadoop.fs.CommonConfigurationKeysPublic On Sun, Jan 13, 2019 at 6:03 PM Aaron Bossert wrote: > Thanks! > > Sent from my iPhone > > > On Jan 13, 2019, at 18:00, Thomas Weise wrote: > > > > For the upgrade it is probably best when you chang

Re: support Hadoop 3.X

2019-01-15 Thread Aaron Bossert
OK, I have my local clone working and updated for Hadoop 3.1... On Tue, Jan 15, 2019 at 1:55 PM Aaron Bossert wrote: > OK, folks. I have imported the Master branch of apex-coreI updated > the dependency for Hadoop to 3.1.0 and here is first round of problems. Of > those listed b

Re: support Hadoop 3.X

2019-01-15 Thread Aaron Bossert
When I try to do a pull request from Intellij, I get a permissions error...I have not done this much, so it could be something really dumb on my part...do I need you to authorize my account in some way? On Tue, Jan 15, 2019 at 3:20 PM Aaron Bossert wrote: > OK, I have my local clone work

Re: support Hadoop 3.X

2019-01-15 Thread Aaron Bossert
something changed > recently. Did you try creating a PR from your branch in your fork on > github.com? > > Thanks > > On Tue, Jan 15, 2019 at 6:59 PM Aaron Bossert > wrote: > > > When I try to do a pull request from Intellij, I get a permissions > > error...I have

Re: [DISCUSS] Time for attic?

2019-01-09 Thread Aaron Bossert
From the perspective of a person experimenting with Apex coming from a background with Storm as the existing solution, Thomas’ comment is particularly relevant: there are significant barriers to entry that make Apex appealing on the surface, but very challenging to implement or port an

Re: [DISCUSS] Time for attic?

2019-01-09 Thread Aaron Bossert
ial - I > would be happy to help. > > Thomas > >> On Wed, Jan 9, 2019 at 6:30 PM Aaron Bossert wrote: >> >> From the perspective of a person experimenting with Apex coming from a >> background with Storm as the existing solution, Thomas’ comment is >> part

Re: [DISCUSS] Time for attic?

2019-01-07 Thread Aaron Bossert
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 project to Apache attic. > > Thank you, > > Vlad

Re: support Hadoop 3.X

2019-01-11 Thread Aaron Bossert
t; changes. > > > > Thank you, > > > > Vlad > > > > > On Jan 10, 2019, at 07:58, Aaron Bossert wrote: > > > > > > As requested by Thomas, I am hoping we can kick off a discussion about > a > > > short-term goal of adding sup

Re: support Hadoop 3.X

2019-01-13 Thread Aaron Bossert
org/docs/r3.0.0/ > [3] http://apex.apache.org/contributing.html > > > >> On Fri, Jan 11, 2019 at 5:14 PM Aaron Bossert wrote: >> >> at first blush, I would think, that the YARN node tagging and native Docker >> support would be particularly intriguing...the GPU node su

[jira] [Created] (APEXCORE-816) Update Apache Apex Core to use Kryo version 4

2018-05-17 Thread M. Aaron Bossert (JIRA)
M. Aaron Bossert created APEXCORE-816: - Summary: Update Apache Apex Core to use Kryo version 4 Key: APEXCORE-816 URL: https://issues.apache.org/jira/browse/APEXCORE-816 Project: Apache Apex Core