Re: Anyone else mis-interpret the "KafkaConsumer" and "KafkaProducer" all the time?

inner > connection and channel would be better. > > 2018-03-23 2:28 GMT+08:00 Dale LaBossiere <dlab...@apache.org>: > >> I see the new RabbitMQ connector followed the same API scheme as the Kafka >> connector. i.e., adding Rabbitmq{Consumer,Producer} for the

Re: Anyone else mis-interpret the "KafkaConsumer" and "KafkaProducer" all the time?

o.a.e.connectors.rabbitmq.Rabbitmq{Consumer,Producer} instead of just RabbitmqStreams? — Dale > On Mar 22, 2018, at 1:11 PM, Dale LaBossiere <dml.apa...@gmail.com> wrote: > > Hi Chris. Hopefully the background provided some useful context. But like I > said, I don’t feel strongly a

Re: Rename "iotp" to "iot-ibm" or similar?

Yeah, “iotp” isn’t very clear/helpful. I’ve often used “wiotp” when referring to “Watson IoT Platform”. FWIW, wiotp's API’s base package name is com.ibm.iotf (IoT Framework) and Edgent’s connector was originally named “iotf”. Then renamed when they changed the name, but not package name, to

Re: [disscuss] make TStream support groupBy operator?

ogy/src/main/java/org/apache/edgent/samples/topology/SensorsAggregates.java> [2] http://edgent.apache.org/docs/faq <http://edgent.apache.org/docs/faq> [3] http://edgent.apache.org/docs/power-of-edgent.html <http://edgent.apache.org/docs/power-of-edgent.html> > On Mar 22, 2

Re: Anyone else mis-interpret the "KafkaConsumer" and "KafkaProducer" all the time?

Hi Chris. Hopefully the background provided some useful context. But like I said, I don’t feel strongly about some renaming if folks agree that’s the right think to do. — Dale > On Mar 22, 2018, at 12:56 PM, Christofer Dutz > wrote: > It was just something I had

Re: [disscuss] make TStream support groupBy operator?

Hi, (I’ve been in my first month of retirement, yeah it would be helpful if other original Edgent developers chimed in) Edgent provides count or time based Windows of tuples. A window inherently supports multiple independently managed partitions by a key. Continuous or batch aggregations

Re: Anyone else mis-interpret the "KafkaConsumer" and "KafkaProducer" all the time?

A bit of background… The Kafka connector is two classes instead of a single KafkaStreams connector (with publish(),subscribe()) because at least a while ago, don’t know if this is still the case, Kafka had two completely separate classes for a “consumer” and a “producer" each with very

life event

All, My first day of retirement starts tomorrow! At this time it’s unclear what my level of participation in Edgent and PLC4X will become. We’ll just have to see how it goes. I’m encouraged by the synergy between Edgent and PLC4X. Chris is a great promoter and contributor so I’m optimistic

Re: High res Edgent logo?

FWIW it was Queenie who provided the assistance/reference not me :-) > On Feb 21, 2018, at 2:14 PM, Christofer Dutz > wrote: > > Hi Dale, > > unfortunately this seems to be too small ( > > I'll check with our companies designers, if they could vectorize the image.

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371922#comment-16371922 ] Dale LaBossiere commented on EDGENT-440: update: Chris's latest changes addressed

Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin

Thanks Chris. I’ve rerun the process and all of the test files are now eliminated from the staged repo. yay! +1 on starting the vote to release the plugin. Followup questions: - are we in agreement that the edgent-parent source-release files in the repo should NOT be present? (to clarify,

Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin

-plugin:jar:1.0.0-SNAPSHOT in apache-plugins-snapshots (https://repository.apache.org/content/repositories/snapshots) -> [Help 1] > On Feb 20, 2018, at 2:46 PM, Dale LaBossiere <dml.apa...@gmail.com> wrote: > > Thanks Chris. Good news, bad news :-) > > -DignoreSnaps

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370557#comment-16370557 ] Dale LaBossiere commented on EDGENT-440: These unwanted files are still present in a newly

Re: release:prepare fails due to the new edgent-deployment-filter-maven-plugin

ojo.html#allowTimestampedSnapshots> > option for testing. > > Chris > > Outlook for Android<https://aka.ms/ghei36> herunterladen > > > From: Dale LaBossiere <dml.apa...@gmail.com> > Sent: Tuesday, February 20, 2018 4:49:09

Re: Problem running some examples with non US locales

Just to close off this thread… +1 on “Precision.round()” especially that the component already depends on commons-math3. I know you already delivered the fix :-) Thanks, — Dale > On Feb 14, 2018, at 4:13 PM, Christofer Dutz > wrote: > > What would you think about

release:prepare fails due to the new edgent-deployment-filter-maven-plugin

Hi Chris, I updated my workspace to the latest develop bits and am trying to run through the release process to verify the doc etc. I’m running into a problem with the new plugin. What’s the scoop? Is this the flow and one just needs to ask to resolve it to 1.0.0? $ mvn release:prepare...

Re: My first article about Apache Edgent was accepted :-)

Nice! > On Feb 18, 2018, at 7:10 AM, Christofer Dutz > wrote: > > Hi all, > > I just got notified, that the article I submitted for an IT Magazines IoT > Special Edition (JavaSPEKTRUM) was accepted and is currently being prepared > for being printed. I also added

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360939#comment-16360939 ] Dale LaBossiere commented on EDGENT-440: Chris believes publishing of the un-wanted test jars has

Re: [DRAFT] January Podling Report

I merged info from the two drafts and will submit the following. Feel free to update the submission as I’m out the rest of the week. — Dale === Edgent Apache Edgent is a programming SDK and micro-kernel style runtime that can be embedded in gateways and small

Re: [DRAFT] January Podling Report

Hmm… I sent a draft on Jan 30th and was planning on submitting it today. https://lists.apache.org/thread.html/c23ae4d7536e911b10668de205e435bb171c529d96df4a536fd1ddcc@%3Cdev.edgent.apache.org%3E But no worries. Maybe just merge some of the info into yours. — Dale > On Feb 5, 2018, at 6:33 AM,

[jira] [Resolved] (EDGENT-445) Console testOverridePortNumber() fails in Jenkins

[ https://issues.apache.org/jira/browse/EDGENT-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-445. Resolution: Fixed Fix Version/s: Apache Edgent 1.3.0 via https://github.com/apache

[jira] [Commented] (EDGENT-445) Console testOverridePortNumber() fails in Jenkins

[ https://issues.apache.org/jira/browse/EDGENT-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345754#comment-16345754 ] Dale LaBossiere commented on EDGENT-445: Yeah the singleton and test ordering, or not spawning

[jira] [Created] (EDGENT-445) Console testOverridePortNumber() fails in Jenkins

Dale LaBossiere created EDGENT-445: -- Summary: Console testOverridePortNumber() fails in Jenkins Key: EDGENT-445 URL: https://issues.apache.org/jira/browse/EDGENT-445 Project: Edgent Issue

[DRAFT] January Podling Report Edgent

Comments? === Edgent Apache Edgent is a programming SDK and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment,

[jira] [Created] (EDGENT-444) Improve how to create aggregated javadoc

Dale LaBossiere created EDGENT-444: -- Summary: Improve how to create aggregated javadoc Key: EDGENT-444 URL: https://issues.apache.org/jira/browse/EDGENT-444 Project: Edgent Issue Type: Task

Re: reproducible release process

are correct. Naveen doesn't provide any means for the merging. I did > use the simple commands you did without any fast forward. Don't know if > Apache's git would have accepted that anyway. > > Chris > > Outlook for Android<https://aka.ms/ghei36> herunterladen > > &

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326532#comment-16326532 ] Dale LaBossiere commented on EDGENT-440: Forgot to mention that I added buildTools/check_jars.sh

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326530#comment-16326530 ] Dale LaBossiere commented on EDGENT-440: As of 1/15/2018 a release:perform still uploads

Re: reproducible release process

Now that release:perform worked… Assuming the RC vote passes and the nexus staging repository is “closed”... It looks like the maven-release-plugin doesn’t provide any merging of the release to appropriate locations. What were the exact cmds you used to merge the release to master, to create:

Re: reproducible release process

update all versions to the > release version (without SNAPSHOT) and tag that in git before updating it > again to the “new working copy version”. > > I thought these versions were self-explanatory, maybe I should elaborate a > little more on these. > > Chris > > > A

FYI, GitHub mirror default branch changed to "develop"

It was changed via [1]. Presumably now when a pull request is created it will default to “develop” as the destination. The insights page on GitHub now reports more useful commit info for “Contributors”. > [1] https://issues.apache.org/jira/browse/INFRA-15780 >

Re: reproducible release process

t too … and yes … it will do all the > steps without pushing (it will however create a Maven staging repo). The > staging repo is simply removed by a simple click and with the git repo, a > simple forced git reset should do the trick. > > If you run into any problems, I’ll try to

reproducible release process

Hi Chris, At a high level, we need to ensure someone can reproduce what you just went through for 1.2.0. It feels like I should try going through the process for a, fictitious at the moment, 1.3.0 release. i.e., going all the way up to staging the release in dist.apache.org and in Nexus

Re: [ANNOUNCE] Apache Edgent 1.2.0-incubating release

Thanks. I’ve created the 1.2.0 and 1.3.0 releases on Jira and updated the issues (assigned fixed-in versions, transitioned many to “closed”). Per the RM-guide (and apache policy) I also removed the superseded 1.1.0-incubating from dist.apache.org. > On Jan 2, 2018, at 12:02 PM, Christofer Dutz

[jira] [Closed] (EDGENT-398) intermittent test failure Execution failed for task ':connectors:wsclient-javax.websocket:test'

[ https://issues.apache.org/jira/browse/EDGENT-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-398. -- Resolution: Cannot Reproduce old jira, don't think tests are encountering these anymore so

Re: Buffering on the edge (network issues)

12:38 PM, Dale LaBossiere <dml.apa...@gmail.com> wrote: > > Hi, > > An Edgent stream is very light weight, it doesn’t have any inherent buffering > per-se. The simple model is that the “next tuple” isn’t processed until > processing of the current tuple is complete

[jira] [Closed] (EDGENT-242) desensitize IotProviderTest for timing

[ https://issues.apache.org/jira/browse/EDGENT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-242. -- Resolution: Cannot Reproduce This jira is pretty old and the tests don't seem

[jira] [Updated] (EDGENT-31) FileStreamsTextFileWriterTest testRetainAgeBased test fails with expected:<2> but was:<3>

[ https://issues.apache.org/jira/browse/EDGENT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-31: -- Fix Version/s: Apache Edgent 1.2.0 > FileStreamsTextFileWriterTest testRetainAgeBased test fa

[jira] [Closed] (EDGENT-435) CME in TrackingScheduledExecutor seen with testMultiTopologyPollWithError()

[ https://issues.apache.org/jira/browse/EDGENT-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-435. -- > CME in TrackingScheduledExecutor seen with testMultiTopologyPollWithEr

[jira] [Updated] (EDGENT-435) CME in TrackingScheduledExecutor seen with testMultiTopologyPollWithError()

[ https://issues.apache.org/jira/browse/EDGENT-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-435: --- Fix Version/s: Apache Edgent 1.2.0 > CME in TrackingScheduledExecutor s

[jira] [Updated] (EDGENT-331) HttpConnector put/post mishandling string to byte

[ https://issues.apache.org/jira/browse/EDGENT-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-331: --- Fix Version/s: Apache Edgent 1.1.0 > HttpConnector put/post mishandling string to b

[jira] [Closed] (EDGENT-374) IotProvider edgentControl commands are silent no-ops under some failure conditions

[ https://issues.apache.org/jira/browse/EDGENT-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-374. -- > IotProvider edgentControl commands are silent no-ops under some failure > cond

[jira] [Closed] (EDGENT-359) CLONE - Review release process / documentation

[ https://issues.apache.org/jira/browse/EDGENT-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-359. -- > CLONE - Review release process / documentat

[jira] [Closed] (EDGENT-381) update NOTICES for 2017

[ https://issues.apache.org/jira/browse/EDGENT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-381. -- > update NOTICES for 2017 > --- > > Key

[jira] [Closed] (EDGENT-334) Release Apache Edgent 1.1.0

[ https://issues.apache.org/jira/browse/EDGENT-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-334. -- > Release Apache Edgent 1.1.0 > --- > > Key

[jira] [Closed] (EDGENT-396) JobMonitorApp restarts job 3 times more than it should

[ https://issues.apache.org/jira/browse/EDGENT-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-396. -- > JobMonitorApp restarts job 3 times more than it sho

[jira] [Closed] (EDGENT-399) fix publish_release.sh

[ https://issues.apache.org/jira/browse/EDGENT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-399. -- > fix publish_release.sh > -- > > Key

[jira] [Updated] (EDGENT-399) fix publish_release.sh

[ https://issues.apache.org/jira/browse/EDGENT-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-399: --- Fix Version/s: Apache Edgent 1.2.0 > fix publish_release

[jira] [Closed] (EDGENT-406) Improve documentation for ApplicationServiceMXBean.registerJar()

[ https://issues.apache.org/jira/browse/EDGENT-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-406. -- > Improve documentation for ApplicationServiceMXBean.register

[jira] [Updated] (EDGENT-406) Improve documentation for ApplicationServiceMXBean.registerJar()

[ https://issues.apache.org/jira/browse/EDGENT-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-406: --- Fix Version/s: Apache Edgent 1.2.0 > Improve documentat

[jira] [Closed] (EDGENT-407) JsonFunctions: more convenience functions for creation and unpartitioned window

[ https://issues.apache.org/jira/browse/EDGENT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-407. -- > JsonFunctions: more convenience functions for creation and unpartitioned >

[jira] [Updated] (EDGENT-407) JsonFunctions: more convenience functions for creation and unpartitioned window

[ https://issues.apache.org/jira/browse/EDGENT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-407: --- Fix Version/s: Apache Edgent 1.2.0 > JsonFunctions: more convenience functions for creat

[jira] [Closed] (EDGENT-408) MqttOpenTest failing due to unhealthy test.mosquitto.org

[ https://issues.apache.org/jira/browse/EDGENT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-408. -- > MqttOpenTest failing due to unhealthy test.mosquitto.

[jira] [Closed] (EDGENT-409) Add analytic aggregations for non-JsonObject types

[ https://issues.apache.org/jira/browse/EDGENT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-409. -- > Add analytic aggregations for non-JsonObject ty

[jira] [Updated] (EDGENT-408) MqttOpenTest failing due to unhealthy test.mosquitto.org

[ https://issues.apache.org/jira/browse/EDGENT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-408: --- Fix Version/s: Apache Edgent 1.2.0 > MqttOpenTest failing due to unhealthy test.mosquitto.

[jira] [Updated] (EDGENT-409) Add analytic aggregations for non-JsonObject types

[ https://issues.apache.org/jira/browse/EDGENT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-409: --- Fix Version/s: Apache Edgent 1.2.0 > Add analytic aggregations for non-JsonObject ty

[jira] [Closed] (EDGENT-417) remove old ant-build cruft

[ https://issues.apache.org/jira/browse/EDGENT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-417. -- > remove old ant-build cruft > -- > > Key

[jira] [Updated] (EDGENT-417) remove old ant-build cruft

[ https://issues.apache.org/jira/browse/EDGENT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-417: --- Fix Version/s: Apache Edgent 1.2.0 > remove old ant-build cr

[jira] [Closed] (EDGENT-419) Remove use of java8 default interface methods by tests

[ https://issues.apache.org/jira/browse/EDGENT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-419. -- > Remove use of java8 default interface methods by te

[jira] [Updated] (EDGENT-424) Cleanup things that maven-javadoc-plugin 2.10.4 complains about

[ https://issues.apache.org/jira/browse/EDGENT-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-424: --- Fix Version/s: Apache Edgent 1.2.0 > Cleanup things that maven-javadoc-plugin 2.1

[jira] [Closed] (EDGENT-422) desensitize FileStreamsTextFileWriterTest

[ https://issues.apache.org/jira/browse/EDGENT-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-422. -- > desensitize FileStreamsTextFileWriterT

[jira] [Closed] (EDGENT-424) Cleanup things that maven-javadoc-plugin 2.10.4 complains about

[ https://issues.apache.org/jira/browse/EDGENT-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-424. -- > Cleanup things that maven-javadoc-plugin 2.10.4 complains ab

[jira] [Updated] (EDGENT-422) desensitize FileStreamsTextFileWriterTest

[ https://issues.apache.org/jira/browse/EDGENT-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-422: --- Fix Version/s: Apache Edgent 1.2.0 > desensitize FileStreamsTextFileWriterT

[jira] [Closed] (EDGENT-443) j7 api/topology is generating an undesirable test-server jar

[ https://issues.apache.org/jira/browse/EDGENT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-443. -- > j7 api/topology is generating an undesirable test-server

[jira] [Closed] (EDGENT-428) Adding support for csv in MetricsSetup

[ https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-428. -- > Adding support for csv in MetricsSe

[jira] [Updated] (EDGENT-428) Adding support for csv in MetricsSetup

[ https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-428: --- Fix Version/s: (was: Apache Edgent 1.1.0) Apache Edgent 1.2.0 > Add

[jira] [Updated] (EDGENT-439) optionally specify TCP port for Jetty HTTP server in console

[ https://issues.apache.org/jira/browse/EDGENT-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-439: --- Fix Version/s: Apache Edgent 1.3.0 > optionally specify TCP port for Jetty HTTP ser

[jira] [Closed] (EDGENT-441) Adjust Kafka tests to tolerate slow consumer startup

[ https://issues.apache.org/jira/browse/EDGENT-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-441. -- > Adjust Kafka tests to tolerate slow consumer star

[jira] [Closed] (EDGENT-442) j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc

[ https://issues.apache.org/jira/browse/EDGENT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-442. -- > j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,

[jira] [Closed] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too

[ https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-178. -- > console: stream hover should report "alias" in addition to tags; maybe oplet

[jira] [Closed] (EDGENT-327) some http urls in the website prevent full local testing

[ https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-327. -- > some http urls in the website prevent full local test

[jira] [Closed] (EDGENT-289) Verify an Eclipse runtime development environment can be setup

[ https://issues.apache.org/jira/browse/EDGENT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-289. -- > Verify an Eclipse runtime development environment can be se

[jira] [Closed] (EDGENT-364) Update instructions on how to use the binary/source release bundles

[ https://issues.apache.org/jira/browse/EDGENT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-364. -- > Update instructions on how to use the binary/source release bund

[jira] [Closed] (EDGENT-219) new keyedTimeBatchWindowTest isn't robust?

[ https://issues.apache.org/jira/browse/EDGENT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-219. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > new keyedTimeBatchWindowT

[jira] [Closed] (EDGENT-273) Add scripts, etc to enable building samples against a binary-release

[ https://issues.apache.org/jira/browse/EDGENT-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-273. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Add scripts, etc to ena

[jira] [Closed] (EDGENT-393) Wish for Ranges.outsideOf()

[ https://issues.apache.org/jira/browse/EDGENT-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-393. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Wish for Ranges.outsid

[jira] [Closed] (EDGENT-413) Simplify download experience

[ https://issues.apache.org/jira/browse/EDGENT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-413. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Simplify download experie

[jira] [Closed] (EDGENT-429) JobMonitorApp.closeJob() doesn't wait for close

[ https://issues.apache.org/jira/browse/EDGENT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-429. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > JobMonitorApp.closeJob() does

[jira] [Closed] (EDGENT-423) Range.toStringUnsigned() not supported on Java7/android

[ https://issues.apache.org/jira/browse/EDGENT-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-423. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Range.toStringUnsig

[jira] [Closed] (EDGENT-431) cleanup some console code hygiene warnings reported by IntelliJ/SonarQube

[ https://issues.apache.org/jira/browse/EDGENT-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-431. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > cleanup some console code hygi

[jira] [Closed] (EDGENT-432) Reduce runtime of some WindowsTest tests

[ https://issues.apache.org/jira/browse/EDGENT-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-432. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Reduce runtime of s

[jira] [Closed] (EDGENT-434) desentize PlumbingTest.testParallelBalanced

[ https://issues.apache.org/jira/browse/EDGENT-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-434. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > desent

[jira] [Closed] (EDGENT-438) Enhance WebSocketClientTest's "skip if can't connect"

[ https://issues.apache.org/jira/browse/EDGENT-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-438. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Enhance WebSocketClientTes

[jira] [Closed] (EDGENT-436) change tests that use complete() TMO for successful runs

[ https://issues.apache.org/jira/browse/EDGENT-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere closed EDGENT-436. -- Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > change tests that use compl

[jira] [Resolved] (EDGENT-443) j7 api/topology is generating an undesirable test-server jar

[ https://issues.apache.org/jira/browse/EDGENT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-443. Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > j7 api/topology is generat

[jira] [Resolved] (EDGENT-442) j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc

[ https://issues.apache.org/jira/browse/EDGENT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-442. Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > j7 connectors/websocket-je

[jira] [Resolved] (EDGENT-418) Think LICENSE/NOTICE in binary release .jar & .war are wrong

[ https://issues.apache.org/jira/browse/EDGENT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-418. Resolution: Fixed Fix Version/s: Apache Edgent 1.2.0 > Think LICENSE/NOT

Re: Buffering on the edge (network issues)

Hi, An Edgent stream is very light weight, it doesn’t have any inherent buffering per-se. The simple model is that the “next tuple” isn’t processed until processing of the current tuple is complete — accepted by all its downstream streams - ultimately by a “sink”. i.e., downstream streams

Re: [DRAFT] [ANNOUNCE] Apache Edgent 1.2.0-incubating release

che Edgent team > > [1] https://github.com/apache/incubator-edgent-samples.git > [2] https://edgent.apache.org/ > [3] https://edgent.apache.org/docs/downloads.html > > > > > Am 18.12.17, 18:44 schrieb "Dale LaBossiere" <dml.apa...@gmail.com>: >

Re: Edgent website update for 1.2.0

The live website now contains the 1.2.0 javadoc. — Dale > On Dec 15, 2017, at 3:14 PM, Dale LaBossiere <dlab...@apache.org> wrote: > > FYI, the website updates for 1.2.0 are now live. > > I’ll update the javadoc once that’s figured out. > > In summary there ar

Re: [DRAFT] [ANNOUNCE] Apache Edgent 1.2.0-incubating release

> On Dec 18, 2017, at 4:44 AM, Christofer Dutz > wrote: > Any comments to this? Or should I post this version? It’s not bad but I’m trying to figure out how it might be improved: - add a statement capturing the theme of the release - to make it easier to get started

Edgent website update for 1.2.0

Chris, thanks for pushing out the release! I’m ready to update the website with PR-97 [1] One thing that’s missing is the updated Javadoc. I know it won’t work but for reference here’s the old process related to getting the releases javadoc onto the website [2] And here’s what that javadoc

[jira] [Commented] (EDGENT-442) j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc

[ https://issues.apache.org/jira/browse/EDGENT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289645#comment-16289645 ] Dale LaBossiere commented on EDGENT-442: fixed via https://github.com/apache/incubator-edgent/pull

[jira] [Commented] (EDGENT-443) j7 api/topology is generating an undesirable test-server jar

[ https://issues.apache.org/jira/browse/EDGENT-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289630#comment-16289630 ] Dale LaBossiere commented on EDGENT-443: fixed via https://github.com/apache/incubator-edgent/pull

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289579#comment-16289579 ] Dale LaBossiere commented on EDGENT-440: See related EDGENT-443 that will eliminate the undesired

[jira] [Created] (EDGENT-443) j7 api/topology is generating an undesirable test-server jar

Dale LaBossiere created EDGENT-443: -- Summary: j7 api/topology is generating an undesirable test-server jar Key: EDGENT-443 URL: https://issues.apache.org/jira/browse/EDGENT-443 Project: Edgent

[jira] [Commented] (EDGENT-442) j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc

[ https://issues.apache.org/jira/browse/EDGENT-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289535#comment-16289535 ] Dale LaBossiere commented on EDGENT-442: The pom can't use the typical {{META-INF/**}} because

[jira] [Created] (EDGENT-442) j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc

Dale LaBossiere created EDGENT-442: -- Summary: j7 connectors/websocket-jetty jar lacks META-INF/LICENSE,etc Key: EDGENT-442 URL: https://issues.apache.org/jira/browse/EDGENT-442 Project: Edgent

[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286599#comment-16286599 ] Dale LaBossiere commented on EDGENT-440: PR-334 eliminated the staging of the edgent-test

[jira] [Assigned] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral

[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere reassigned EDGENT-440: -- Assignee: Dale LaBossiere > Adjust "release" processing so only desi

  1   2   3   4   5   6   7   8   >