[jira] [Work started] (STREAMS-316) add “apache’ to the artifact name
[ https://issues.apache.org/jira/browse/STREAMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-316 started by Suneel Marthi. - > add “apache’ to the artifact name > - > > Key: STREAMS-316 > URL: https://issues.apache.org/jira/browse/STREAMS-316 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi >Priority: Trivial > Fix For: 0.5.1 > > > Suggestions from 0.2-rc3 vote: > - You may want to consider adding “apache’ to the artifact name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-480) Remove -incubating suffix from Release artifacts names
[ https://issues.apache.org/jira/browse/STREAMS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-480. --- Resolution: Fixed > Remove -incubating suffix from Release artifacts names > -- > > Key: STREAMS-480 > URL: https://issues.apache.org/jira/browse/STREAMS-480 > Project: Streams > Issue Type: New Feature > Components: Build >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Remove the -incubating suffix from future release artifacts - this stems from > the discussion here - > https://lists.apache.org/thread.html/17ecae7960572e3cad9ba734ea15d55a337422e27ce08d2297a1e830@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (STREAMS-480) Remove -incubating suffix from Release artifacts names
[ https://issues.apache.org/jira/browse/STREAMS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-480 started by Suneel Marthi. - > Remove -incubating suffix from Release artifacts names > -- > > Key: STREAMS-480 > URL: https://issues.apache.org/jira/browse/STREAMS-480 > Project: Streams > Issue Type: New Feature > Components: Build >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Remove the -incubating suffix from future release artifacts - this stems from > the discussion here - > https://lists.apache.org/thread.html/17ecae7960572e3cad9ba734ea15d55a337422e27ce08d2297a1e830@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962389#comment-15962389 ] Suneel Marthi commented on STREAMS-493: --- Is this still an issue? Jenkins needs to be reconfigured following the retirement of streams-master post 0.4.1 release. > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-412) ability (and instructions on how) to run processors directly from console
[ https://issues.apache.org/jira/browse/STREAMS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-412: -- Fix Version/s: (was: 0.5) 0.5.1 > ability (and instructions on how) to run processors directly from console > - > > Key: STREAMS-412 > URL: https://issues.apache.org/jira/browse/STREAMS-412 > Project: Streams > Issue Type: Improvement > Components: Processors >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5.1 > > > All of the processors currently require attachment to a run-time to use. > If processors could be configured and executed directly from the console, > they would become more valuable for casual use cases where users just want to > easily transform documents without writing or deploying custom code. > This would probably take the form of adding a main method and perhaps a > Runnable trait to each processor, that when launched resolves the appropriate > typesafe config, starts up the process, and transforms documents from STDIN > writing them to STDOUT until the input stops. > Instructions how to do this should also be added to the javadocs of the > processors and/or the markdowns of each module. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-497) Add streams prefix to project and examples artifactIds
[ https://issues.apache.org/jira/browse/STREAMS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-497. --- Resolution: Fixed > Add streams prefix to project and examples artifactIds > -- > > Key: STREAMS-497 > URL: https://issues.apache.org/jira/browse/STREAMS-497 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > It would be better if the project and example modules which do *not* > have an artifactId prefixed with "streams-" are updated to use such prefix. > Now there are for example the flink-twitter-collection-0.5-incubating, > google-gplus-0.5-incubating, etc. modules (6 modules in total) which produce > artifacts that IMO are confusing for downstream users what originating > project > they 'belong' to. > And as result their embedded NOTICE and DISCLAIMER files contain a confusing > (generated) statement like: > google-gplus > Copyright 2017 The Apache Software Foundation > By correcting the artifactIds to for example streams-provider-google-gplus > this > would yield the more clear/correct: > streams-provider-google-gplus > Copyright 2017 The Apache Software Foundation -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STREAMS-497) Add streams prefix to project and examples artifactIds
[ https://issues.apache.org/jira/browse/STREAMS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-497: - Assignee: Suneel Marthi (was: Steve Blackmon) > Add streams prefix to project and examples artifactIds > -- > > Key: STREAMS-497 > URL: https://issues.apache.org/jira/browse/STREAMS-497 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > It would be better if the project and example modules which do *not* > have an artifactId prefixed with "streams-" are updated to use such prefix. > Now there are for example the flink-twitter-collection-0.5-incubating, > google-gplus-0.5-incubating, etc. modules (6 modules in total) which produce > artifacts that IMO are confusing for downstream users what originating > project > they 'belong' to. > And as result their embedded NOTICE and DISCLAIMER files contain a confusing > (generated) statement like: > google-gplus > Copyright 2017 The Apache Software Foundation > By correcting the artifactIds to for example streams-provider-google-gplus > this > would yield the more clear/correct: > streams-provider-google-gplus > Copyright 2017 The Apache Software Foundation -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-420) reboot: cleanup JIRA
[ https://issues.apache.org/jira/browse/STREAMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893589#comment-15893589 ] Suneel Marthi commented on STREAMS-420: --- Can this be marked as 'Resolved' ? > reboot: cleanup JIRA > > > Key: STREAMS-420 > URL: https://issues.apache.org/jira/browse/STREAMS-420 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > > per the reboot theme: get rid of anything old or irrelevant in JIRA -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-453) tag each jira against one/more components.
[ https://issues.apache.org/jira/browse/STREAMS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893591#comment-15893591 ] Suneel Marthi commented on STREAMS-453: --- I guess we could mark this as 'Resolved' ? > tag each jira against one/more components. > --- > > Key: STREAMS-453 > URL: https://issues.apache.org/jira/browse/STREAMS-453 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-491. --- Resolution: Not A Problem Assignee: Suneel Marthi > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Assignee: Suneel Marthi >Priority: Trivial > Fix For: 0.5 > > Attachments: log_streams_6_ver.txt, log_streams.txt > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at
[jira] [Comment Edited] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873904#comment-15873904 ] Suneel Marthi edited comment on STREAMS-491 at 2/20/17 12:51 AM: - Its obvious from the last failure that the timeout for twitter-neo4j is still set to 2, try increasing that to 6. The issues u have identified so far in this jira are more to do with u running this on an old system with limited memory and the docker container shutting down due to initialization or shutdown failures. I would like to Resolve this jira as 'Not an Issue' and any similar issues like this are henceforth best addressed on d...@streams.incubator.apache.org mailing lists and don't need a Jira. Please move this conversation to the mail lists, resolving this jira now as 'Won't Fix' was (Author: smarthi): Its obvious from the last failure that the timeout for twitter-neo4j is still set to 2, try increasing that to 6. The issues u have identified so far in this jira are more to do with u running this on an old system with limited memory and the docker container shutting down due to initialization or shutdown failures. I would like to Resolve this jira as 'Not an Issue' and any similar issues like this are henceforth best addressed on d...@streams.incubator.apache.org mailing lists and don't need a Jira. > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > Attachments: log_streams_6_ver.txt, log_streams.txt > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start
[jira] [Commented] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873904#comment-15873904 ] Suneel Marthi commented on STREAMS-491: --- Its obvious from the last failure that the timeout for twitter-neo4j is still set to 2, try increasing that to 6. The issues u have identified so far in this jira are more to do with u running this on an old system with limited memory and the docker container shutting down due to initialization or shutdown failures. I would like to Resolve this jira as 'Not an Issue' and any similar issues like this are henceforth best addressed on d...@streams.incubator.apache.org mailing lists and don't need a Jira. > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > Attachments: log_streams_6_ver.txt, log_streams.txt > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at >
[jira] [Commented] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873289#comment-15873289 ] Suneel Marthi commented on STREAMS-491: --- Did u increase the timeout to 6? You need to do it at 2 places in the POM. Its not a problem with OSX, I am running OSX 10.12 and i don't see this issue. I have a MBP with 16gb RAM. Its pretty obvious you are running on an old machine, so shutdown all docker images except for this one, increase the timeout to 6 for both Elasticsearch and Neo4j, and then give it a try. > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > Attachments: log_streams.txt > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at >
[jira] [Commented] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872432#comment-15872432 ] Suneel Marthi commented on STREAMS-491: --- Seems like u r running on an older and slower machine, here's what u could do: 1. Make sure u r not running any other docker images 2. increase the startup time to 6 from present 2 in pom > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > Attachments: log_streams.txt > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at
[jira] [Updated] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-491: -- Rerun the maven command again with -X switch to enable full debugging and post the stacktrace here. On Fri, Feb 17, 2017 at 2:12 AM, Kwang-in (Dennis) JUNG (JIRA) < > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at
[jira] [Reopened] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reopened STREAMS-493: --- > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871188#comment-15871188 ] Suneel Marthi commented on STREAMS-491: --- Could u try shutting down ur ES 5.2, and just running the examples in Docker and see if the issue recurs ? > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at
[jira] [Resolved] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-493. --- Resolution: Fixed Fix Version/s: 0.5 > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870749#comment-15870749 ] Suneel Marthi commented on STREAMS-493: --- See https://github.com/apache/incubator-streams-examples/pull/34 > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-493: - Assignee: Suneel Marthi (was: Steve Blackmon) > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870715#comment-15870715 ] Suneel Marthi commented on STREAMS-493: --- Yup, the cause is due to not specifying snapshots.a.o as a repository. > streams-examples jenkins build fails > > > Key: STREAMS-493 > URL: https://issues.apache.org/jira/browse/STREAMS-493 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > even after streams-project completes a build and installs its snapshots. > for example, see: > https://builds.apache.org/job/streams-project/350/ > https://builds.apache.org/job/streams-examples/193/ > error is: > [ERROR] Plugin > org.apache.streams.plugins:streams-plugin-pojo:0.5-incubating-SNAPSHOT or one > of its dependencies could not be resolved: Could not find artifact > org.apache.streams.plugins:streams-plugin-pojo:jar:0.5-incubating-SNAPSHOT > i think the problem is that our master pom does not specify > snapshots.apache.org as a pluginRepository -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-71) Sysomos Provider should allow a target document or timeframe to be set
[ https://issues.apache.org/jira/browse/STREAMS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-71. -- Resolution: Won't Fix Fix Version/s: 0.5 > Sysomos Provider should allow a target document or timeframe to be set > -- > > Key: STREAMS-71 > URL: https://issues.apache.org/jira/browse/STREAMS-71 > Project: Streams > Issue Type: Improvement >Reporter: Matt Franklin >Assignee: Matt Franklin > Fix For: 0.5 > > > In order to support gaps in query time, the provider should allow for a > document ID or target time to be set -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-402) Allow specification of fields in streams-persist-elasticsearch
[ https://issues.apache.org/jira/browse/STREAMS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-402: -- Affects Version/s: 0.4.1 Fix Version/s: 0.6 Component/s: Plugins > Allow specification of fields in streams-persist-elasticsearch > -- > > Key: STREAMS-402 > URL: https://issues.apache.org/jira/browse/STREAMS-402 > Project: Streams > Issue Type: Improvement > Components: Plugins >Affects Versions: 0.4.1 >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.6 > > > Allow specification of fields in streams-persist-elasticsearch > ElasticsearchReaderConfiguration / ElasticsearchPersistReader > Module should request the specific fields and construct a document comprised > of those fields rather than relying on 'source'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-455) LICENSE, NOTICE and DISCLAIMER in source control.
[ https://issues.apache.org/jira/browse/STREAMS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-455: -- Component/s: Build > LICENSE, NOTICE and DISCLAIMER in source control. > - > > Key: STREAMS-455 > URL: https://issues.apache.org/jira/browse/STREAMS-455 > Project: Streams > Issue Type: New Feature > Components: Build >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > per discussion on IPMC mailing list during 0.4 release, the -master and > -examples git repositories should have a root LICENSE, NOTICE and DISCLAIMER > checked into source control. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-479) build accurate NOTICE file(s) in streams-examples
[ https://issues.apache.org/jira/browse/STREAMS-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-479: -- Component/s: Build > build accurate NOTICE file(s) in streams-examples > - > > Key: STREAMS-479 > URL: https://issues.apache.org/jira/browse/STREAMS-479 > Project: Streams > Issue Type: Task > Components: Build >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > containing licenses of shaded dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-491) Example failure
[ https://issues.apache.org/jira/browse/STREAMS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-491: -- Affects Version/s: 0.4.1 Fix Version/s: 0.5 Component/s: Build > Example failure > --- > > Key: STREAMS-491 > URL: https://issues.apache.org/jira/browse/STREAMS-491 > Project: Streams > Issue Type: Test > Components: Build >Affects Versions: 0.4.1 >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~I'm newbee in streams. Hope this is not a silly qustion... > I'm currently testing on running example, but keep failing on it. > The test is > http://streams.incubator.apache.org/site/0.5-incubating-SNAPSHOT/streams-examples/streams-examples-local/elasticsearch-hdfs/index.html > . > As mentioned, I am running the task with elasticsearch running. > It happens when I work on 'mvn -PdockerITs docker:start' after install. > > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Start container > 13d02afcecb7 > 14:47:32.410 elasticsearch> [2017-02-08 05:47:32,407][WARN ][bootstrap > ] unable to install syscall filter: seccomp unavailable: your kernel > is buggy and you should upgrade > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,936][INFO ][node > ] [Banshee] version[2.3.5], pid[1], > build[90f439f/2016-07-27T10:36:52Z] > 14:47:32.937 elasticsearch> [2017-02-08 05:47:32,937][INFO ][node > ] [Banshee] initializing ... > [ERROR] DOCKER> Cannot process chunk response: java.io.IOException: Bad file > descriptor > [ERROR] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 ms > while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > [INFO] DOCKER> [elasticsearch:2.3.5] "elasticsearch": Stop and remove > container 13d02afcecb7 > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] streams-examples ... FAILURE [ 27.445 > s] > [INFO] streams-examples-flink . SKIPPED > [INFO] flink-twitter-collection ... SKIPPED > [INFO] streams-examples-local . SKIPPED > [INFO] elasticsearch-hdfs . SKIPPED > [INFO] elasticsearch-reindex .. SKIPPED > [INFO] mongo-elasticsearch-sync ... SKIPPED > [INFO] twitter-follow-neo4j ... SKIPPED > [INFO] twitter-history-elasticsearch .. SKIPPED > [INFO] twitter-userstream-elasticsearch ... SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 28.342 s > [INFO] Finished at: 2017-02-08T14:47:54+09:00 > [INFO] Final Memory: 23M/285M > [INFO] > > [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.15.0:start > (default-cli) on project streams-examples: [elasticsearch:2.3.5] > "elasticsearch": Timeout after 20474 ms while waiting on url > http://localhost:32818 and on log out 'elasticsearch startup' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.15.0:start (default-cli) on project > streams-examples: [elasticsearch:2.3.5] "elasticsearch": Timeout after 20474 > ms while waiting on url http://localhost:32818 and on log out 'elasticsearch > startup' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at
[jira] [Updated] (STREAMS-485) Improve release process - no more repeated pasting of versions
[
https://issues.apache.org/jira/browse/STREAMS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi updated STREAMS-485:
--
Affects Version/s: 0.4.1
Component/s: Miscellaneous
> Improve release process - no more repeated pasting of versions
> --
>
> Key: STREAMS-485
> URL: https://issues.apache.org/jira/browse/STREAMS-485
> Project: Streams
> Issue Type: New Feature
> Components: Miscellaneous
>Affects Versions: 0.4.1
>Reporter: Steve Blackmon
>Assignee: Steve Blackmon
> Fix For: 0.5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> a) Let’s dependencyManage every org.apache.streams dependency in
> > streams-examples in the
> > examples root pom to a property ${streams.version}
> > b) Let’s update that property from x.y-incubating-SNAPSHOT
> > to x.y-incubating with a manual commit
> > prior to running release-prepare. If the release is cancelled, we’ll have
> > to rollback past this
> > manual change to build from snapshot again.
> > c) There are some flags you can pass to release plugin to avoid the
> > tedious snapshot resolution;
> > let’s add those to the release instructions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (STREAMS-485) Improve release process - no more repeated pasting of versions
[
https://issues.apache.org/jira/browse/STREAMS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857478#comment-15857478
]
Suneel Marthi commented on STREAMS-485:
---
See https://github.com/apache/incubator-streams-examples/pull/32
> Improve release process - no more repeated pasting of versions
> --
>
> Key: STREAMS-485
> URL: https://issues.apache.org/jira/browse/STREAMS-485
> Project: Streams
> Issue Type: New Feature
>Reporter: Steve Blackmon
>Assignee: Steve Blackmon
> Fix For: 0.5
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> a) Let’s dependencyManage every org.apache.streams dependency in
> > streams-examples in the
> > examples root pom to a property ${streams.version}
> > b) Let’s update that property from x.y-incubating-SNAPSHOT
> > to x.y-incubating with a manual commit
> > prior to running release-prepare. If the release is cancelled, we’ll have
> > to rollback past this
> > manual change to build from snapshot again.
> > c) There are some flags you can pass to release plugin to avoid the
> > tedious snapshot resolution;
> > let’s add those to the release instructions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (STREAMS-463) Move every class in all repos underneath org.apache.streams
[ https://issues.apache.org/jira/browse/STREAMS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-463. --- Resolution: Fixed > Move every class in all repos underneath org.apache.streams > --- > > Key: STREAMS-463 > URL: https://issues.apache.org/jira/browse/STREAMS-463 > Project: Streams > Issue Type: Task > Components: Providers >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > There are several modules with classes and testClasses that aren't under the > org.apache.streams namespace. > This results in check style failures and potential confusion for developers. > There's no reason to preserve this practice. > Move every class in all repos underneath org.apache.streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-488) Fail in build
[ https://issues.apache.org/jira/browse/STREAMS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-488. --- Resolution: Not A Problem > Fail in build > -- > > Key: STREAMS-488 > URL: https://issues.apache.org/jira/browse/STREAMS-488 > Project: Streams > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~ > I'm new on Streams. Nice to meet you. > Though, I'm stuck on 'mvn clean package'. This is the log. > ... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 01:03 min > [INFO] Finished at: 2017-02-06T23:35:57+09:00 > [INFO] Final Memory: 83M/816M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project streams-pojo: There are test failures. > [ERROR] > [ERROR] Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test > (default-test) on project streams-pojo: There are test failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91) > at > org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:320) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:892) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 20 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :streams-pojo > ... > Does anybody know about it? -- This message was sent by
[jira] [Commented] (STREAMS-488) Fail in build
[ https://issues.apache.org/jira/browse/STREAMS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857352#comment-15857352 ] Suneel Marthi commented on STREAMS-488: --- This is not a bug in the project, i suggest that you post your question on d...@streams.incubator.apache.org You first need to run mvn clean install - that does a clean build and runs all unit tests. I will resolve this jira as 'Not a Problem'. > Fail in build > -- > > Key: STREAMS-488 > URL: https://issues.apache.org/jira/browse/STREAMS-488 > Project: Streams > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~ > I'm new on Streams. Nice to meet you. > Though, I'm stuck on 'mvn clean package'. This is the log. > ... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 01:03 min > [INFO] Finished at: 2017-02-06T23:35:57+09:00 > [INFO] Final Memory: 83M/816M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project streams-pojo: There are test failures. > [ERROR] > [ERROR] Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test > (default-test) on project streams-pojo: There are test failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91) > at > org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:320) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:892) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 20 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] >
[jira] [Resolved] (STREAMS-490) Upgrade Flink to 1.2.0 and remove the remaining guava references in streams-examples
[ https://issues.apache.org/jira/browse/STREAMS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-490. --- Resolution: Fixed > Upgrade Flink to 1.2.0 and remove the remaining guava references in > streams-examples > > > Key: STREAMS-490 > URL: https://issues.apache.org/jira/browse/STREAMS-490 > Project: Streams > Issue Type: Bug > Components: Core >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-488) Fail in build
[ https://issues.apache.org/jira/browse/STREAMS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-488: -- Fix Version/s: 0.5 > Fail in build > -- > > Key: STREAMS-488 > URL: https://issues.apache.org/jira/browse/STREAMS-488 > Project: Streams > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Fix For: 0.5 > > > Hello~ > I'm new on Streams. Nice to meet you. > Though, I'm stuck on 'mvn clean package'. This is the log. > ... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 01:03 min > [INFO] Finished at: 2017-02-06T23:35:57+09:00 > [INFO] Final Memory: 83M/816M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project streams-pojo: There are test failures. > [ERROR] > [ERROR] Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test > (default-test) on project streams-pojo: There are test failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91) > at > org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:320) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:892) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 20 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :streams-pojo > ... > Does anybody know about it? -- This message was sent by Atlassian
[jira] [Commented] (STREAMS-490) Upgrade Flink to 1.2.0 and remove the remaining guava references in streams-examples
[ https://issues.apache.org/jira/browse/STREAMS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855120#comment-15855120 ] Suneel Marthi commented on STREAMS-490: --- See https://github.com/apache/incubator-streams-examples/pull/31 > Upgrade Flink to 1.2.0 and remove the remaining guava references in > streams-examples > > > Key: STREAMS-490 > URL: https://issues.apache.org/jira/browse/STREAMS-490 > Project: Streams > Issue Type: Bug > Components: Core >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-490) Upgrade Flink to 1.2.0 and remove the remaining guava references in streams-examples
Suneel Marthi created STREAMS-490: - Summary: Upgrade Flink to 1.2.0 and remove the remaining guava references in streams-examples Key: STREAMS-490 URL: https://issues.apache.org/jira/browse/STREAMS-490 Project: Streams Issue Type: Bug Components: Core Affects Versions: 0.4.1 Reporter: Suneel Marthi Assignee: Suneel Marthi Fix For: 0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-463) Move every class in all repos underneath org.apache.streams
[ https://issues.apache.org/jira/browse/STREAMS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-463 started by Suneel Marthi. - > Move every class in all repos underneath org.apache.streams > --- > > Key: STREAMS-463 > URL: https://issues.apache.org/jira/browse/STREAMS-463 > Project: Streams > Issue Type: Task > Components: Providers >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > There are several modules with classes and testClasses that aren't under the > org.apache.streams namespace. > This results in check style failures and potential confusion for developers. > There's no reason to preserve this practice. > Move every class in all repos underneath org.apache.streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-488) Fail in build
[ https://issues.apache.org/jira/browse/STREAMS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854381#comment-15854381 ] Suneel Marthi commented on STREAMS-488: --- What's your MAven version? It should be atleast Maven 3.3.9 and the project is on Java 8. > Fail in build > -- > > Key: STREAMS-488 > URL: https://issues.apache.org/jira/browse/STREAMS-488 > Project: Streams > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > > Hello~ > I'm new on Streams. Nice to meet you. > Though, I'm stuck on 'mvn clean package'. This is the log. > ... > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 01:03 min > [INFO] Finished at: 2017-02-06T23:35:57+09:00 > [INFO] Final Memory: 83M/816M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project streams-pojo: There are test failures. > [ERROR] > [ERROR] Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test > (default-test) on project streams-pojo: There are test failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures. > Please refer to > /Users/kwangin/workspace/incubator-streams/streams-pojo/target/surefire-reports > for the individual test results. > at > org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91) > at > org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:320) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:892) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > ... 20 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf
[jira] [Updated] (STREAMS-463) Move every class in all repos underneath org.apache.streams
[ https://issues.apache.org/jira/browse/STREAMS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-463: -- Component/s: Providers > Move every class in all repos underneath org.apache.streams > --- > > Key: STREAMS-463 > URL: https://issues.apache.org/jira/browse/STREAMS-463 > Project: Streams > Issue Type: Task > Components: Providers >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > There are several modules with classes and testClasses that aren't under the > org.apache.streams namespace. > This results in check style failures and potential confusion for developers. > There's no reason to preserve this practice. > Move every class in all repos underneath org.apache.streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STREAMS-463) Move every class in all repos underneath org.apache.streams
[ https://issues.apache.org/jira/browse/STREAMS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-463: - Assignee: Suneel Marthi (was: Steve Blackmon) > Move every class in all repos underneath org.apache.streams > --- > > Key: STREAMS-463 > URL: https://issues.apache.org/jira/browse/STREAMS-463 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > There are several modules with classes and testClasses that aren't under the > org.apache.streams namespace. > This results in check style failures and potential confusion for developers. > There's no reason to preserve this practice. > Move every class in all repos underneath org.apache.streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-463) Move every class in all repos underneath org.apache.streams
[ https://issues.apache.org/jira/browse/STREAMS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-463: -- Fix Version/s: 0.5 > Move every class in all repos underneath org.apache.streams > --- > > Key: STREAMS-463 > URL: https://issues.apache.org/jira/browse/STREAMS-463 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > There are several modules with classes and testClasses that aren't under the > org.apache.streams namespace. > This results in check style failures and potential confusion for developers. > There's no reason to preserve this practice. > Move every class in all repos underneath org.apache.streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-445) new consumer provider: for api.foursquare.com
[ https://issues.apache.org/jira/browse/STREAMS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-445: -- Affects Version/s: 0.4.1 Component/s: Providers > new consumer provider: for api.foursquare.com > - > > Key: STREAMS-445 > URL: https://issues.apache.org/jira/browse/STREAMS-445 > Project: Streams > Issue Type: New Feature > Components: Providers >Affects Versions: 0.4.1 >Reporter: Steve Blackmon > > Objects: > 4sq:User > 4sq:Venue > Activities: > 4sq:Checkin > Converters: > 4sq:User -> as:Page > 4sq:Venue -> as:Place > 4sq:Checkin -> as:Checkin > Possibly use https://github.com/dan-zx/foursquare4j > https://developer.foursquare.com/docs/users/checkins > https://api.foursquare.com/v2/users/USER_ID/venuehistory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STREAMS-257) Remove incomplete DEPENDENCIES file from src zip artifact
[ https://issues.apache.org/jira/browse/STREAMS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-257: - Assignee: Suneel Marthi > Remove incomplete DEPENDENCIES file from src zip artifact > - > > Key: STREAMS-257 > URL: https://issues.apache.org/jira/browse/STREAMS-257 > Project: Streams > Issue Type: Bug >Affects Versions: 0.3 >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > > Remove incomplete DEPENDENCIES file from src zip artifact. > It is not necessary for a source/binary release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-438) Create coding guidelines document for website
[ https://issues.apache.org/jira/browse/STREAMS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-438. --- Resolution: Fixed > Create coding guidelines document for website > - > > Key: STREAMS-438 > URL: https://issues.apache.org/jira/browse/STREAMS-438 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-316) add “apache’ to the artifact name
[ https://issues.apache.org/jira/browse/STREAMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-316: -- Fix Version/s: (was: 0.5) 0.6 > add “apache’ to the artifact name > - > > Key: STREAMS-316 > URL: https://issues.apache.org/jira/browse/STREAMS-316 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi >Priority: Trivial > Fix For: 0.6 > > > Suggestions from 0.2-rc3 vote: > - You may want to consider adding “apache’ to the artifact name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-480) Remove -incubating suffix from Release artifacts names
[ https://issues.apache.org/jira/browse/STREAMS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-480. --- Resolution: Won't Fix Let's keep the -incubating suffix until the project Graduates to TLP. > Remove -incubating suffix from Release artifacts names > -- > > Key: STREAMS-480 > URL: https://issues.apache.org/jira/browse/STREAMS-480 > Project: Streams > Issue Type: New Feature > Components: Build >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Remove the -incubating suffix from future release artifacts - this stems from > the discussion here - > https://lists.apache.org/thread.html/17ecae7960572e3cad9ba734ea15d55a337422e27ce08d2297a1e830@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-480) Remove -incubating suffix from Release artifacts names
[ https://issues.apache.org/jira/browse/STREAMS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844120#comment-15844120 ] Suneel Marthi commented on STREAMS-480: --- [~steveblackmon] given that IPMC would still like to keep the -incubating suffix, i am gonna resolve this as 'Won't Fix' if you agree. > Remove -incubating suffix from Release artifacts names > -- > > Key: STREAMS-480 > URL: https://issues.apache.org/jira/browse/STREAMS-480 > Project: Streams > Issue Type: New Feature > Components: Build >Affects Versions: 0.4.1 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Remove the -incubating suffix from future release artifacts - this stems from > the discussion here - > https://lists.apache.org/thread.html/17ecae7960572e3cad9ba734ea15d55a337422e27ce08d2297a1e830@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-255) Merge streams-master into streams-project
[ https://issues.apache.org/jira/browse/STREAMS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-255. --- Resolution: Fixed > Merge streams-master into streams-project > - > > Key: STREAMS-255 > URL: https://issues.apache.org/jira/browse/STREAMS-255 > Project: Streams > Issue Type: Sub-task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > > Merge important parts of streams-master into streams-project and remove > parent relationship. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-481) Update .travis.yml to use Java 8
[ https://issues.apache.org/jira/browse/STREAMS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-481. --- Resolution: Fixed Fix Version/s: 0.5 > Update .travis.yml to use Java 8 > > > Key: STREAMS-481 > URL: https://issues.apache.org/jira/browse/STREAMS-481 > Project: Streams > Issue Type: Bug >Reporter: Joey Frazee >Assignee: Joey Frazee > Fix For: 0.5 > > > Current .travis.yml is set to use oraclejdk7 but Streams has been updated to > use Java 8 as of STREAMS-432 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-480) Remove -incubating suffix from Release artifacts names
Suneel Marthi created STREAMS-480: - Summary: Remove -incubating suffix from Release artifacts names Key: STREAMS-480 URL: https://issues.apache.org/jira/browse/STREAMS-480 Project: Streams Issue Type: New Feature Components: Build Affects Versions: 0.4.1 Reporter: Suneel Marthi Assignee: Suneel Marthi Fix For: 0.5 Remove the -incubating suffix from future release artifacts - this stems from the discussion here - https://lists.apache.org/thread.html/17ecae7960572e3cad9ba734ea15d55a337422e27ce08d2297a1e830@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-255) Merge streams-master into streams-project
[ https://issues.apache.org/jira/browse/STREAMS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-255: -- Fix Version/s: (was: 0.2) > Merge streams-master into streams-project > - > > Key: STREAMS-255 > URL: https://issues.apache.org/jira/browse/STREAMS-255 > Project: Streams > Issue Type: Sub-task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > > Merge important parts of streams-master into streams-project and remove > parent relationship. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-472) Fix failing IT in streams-plugins
[ https://issues.apache.org/jira/browse/STREAMS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-472: -- Affects Version/s: 0.4.1 > Fix failing IT in streams-plugins > - > > Key: STREAMS-472 > URL: https://issues.apache.org/jira/browse/STREAMS-472 > Project: Streams > Issue Type: Bug >Affects Versions: 0.4.1 >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Appears that these test poms have an outdated version dependency, > 0.4-incubating-SNAPSHOT instead of 0.5-incubating-SNAPSHO -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-472) Fix failing IT in streams-plugins
[ https://issues.apache.org/jira/browse/STREAMS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-472: -- Fix Version/s: 0.5 > Fix failing IT in streams-plugins > - > > Key: STREAMS-472 > URL: https://issues.apache.org/jira/browse/STREAMS-472 > Project: Streams > Issue Type: Bug >Affects Versions: 0.4.1 >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Appears that these test poms have an outdated version dependency, > 0.4-incubating-SNAPSHOT instead of 0.5-incubating-SNAPSHO -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-438) Create coding guidelines document for website
[ https://issues.apache.org/jira/browse/STREAMS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-438: -- Fix Version/s: (was: 0.4.1) 0.5 > Create coding guidelines document for website > - > > Key: STREAMS-438 > URL: https://issues.apache.org/jira/browse/STREAMS-438 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-455) LICENSE, NOTICE and DISCLAIMER in source control.
[ https://issues.apache.org/jira/browse/STREAMS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-455: -- Fix Version/s: (was: 0.4.1) 0.5 > LICENSE, NOTICE and DISCLAIMER in source control. > - > > Key: STREAMS-455 > URL: https://issues.apache.org/jira/browse/STREAMS-455 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > per discussion on IPMC mailing list during 0.4 release, the -master and > -examples git repositories should have a root LICENSE, NOTICE and DISCLAIMER > checked into source control. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-476) Remove guava dependency from streams-example project
[ https://issues.apache.org/jira/browse/STREAMS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-476. --- Resolution: Fixed > Remove guava dependency from streams-example project > > > Key: STREAMS-476 > URL: https://issues.apache.org/jira/browse/STREAMS-476 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.4 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Replace Guava APIs with equivalent Java 8 or Apache APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (STREAMS-476) Remove guava dependency from streams-example project
[ https://issues.apache.org/jira/browse/STREAMS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-476 started by Suneel Marthi. - > Remove guava dependency from streams-example project > > > Key: STREAMS-476 > URL: https://issues.apache.org/jira/browse/STREAMS-476 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.4 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.5 > > > Replace Guava APIs with equivalent Java 8 or Apache APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-477) Fix link for checkstyle.xml
Suneel Marthi created STREAMS-477:
-
Summary: Fix link for checkstyle.xml
Key: STREAMS-477
URL: https://issues.apache.org/jira/browse/STREAMS-477
Project: Streams
Issue Type: Bug
Affects Versions: 0.4
Reporter: Suneel Marthi
Assignee: Steve Blackmon
Fix For: 0.5
Fix the link for checkstyle.xml to be independent of ${project.version}, since
its very unlikely that the checkstyle would be changing frequently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (STREAMS-476) Remove guava dependency from streams-example project
Suneel Marthi created STREAMS-476: - Summary: Remove guava dependency from streams-example project Key: STREAMS-476 URL: https://issues.apache.org/jira/browse/STREAMS-476 Project: Streams Issue Type: Improvement Affects Versions: 0.4 Reporter: Suneel Marthi Assignee: Suneel Marthi Fix For: 0.5 Replace Guava APIs with equivalent Java 8 or Apache APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-155) Build hadoop modules with Apache artifacts
[ https://issues.apache.org/jira/browse/STREAMS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15718517#comment-15718517 ] Suneel Marthi commented on STREAMS-155: --- What's remaining to be done on this? > Build hadoop modules with Apache artifacts > -- > > Key: STREAMS-155 > URL: https://issues.apache.org/jira/browse/STREAMS-155 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > > Rather than cloudera. Ensure README for those modules documents what to > change in order to build and run on a cloudera cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-449) Enforce Java code conventions with auto-formatter
[ https://issues.apache.org/jira/browse/STREAMS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698617#comment-15698617 ] Suneel Marthi commented on STREAMS-449: --- In IntelliJ, its Shift + Cmd + L to autoformat code. > Enforce Java code conventions with auto-formatter > - > > Key: STREAMS-449 > URL: https://issues.apache.org/jira/browse/STREAMS-449 > Project: Streams > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5 > > > As more people start to contribute to the project again, getting people > adhering to the same coding conventions will be necessary. To help this > along, we should consider enforcing this with an auto-formatter that runs as > part of the build and/or contrib-check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-441) Remove compile dependency on guava for core packages
[ https://issues.apache.org/jira/browse/STREAMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-441. --- Resolution: Fixed > Remove compile dependency on guava for core packages > > > Key: STREAMS-441 > URL: https://issues.apache.org/jira/browse/STREAMS-441 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4.1 > > > To simplify the transitive dependency tree and reduce odds of users hitting > shading issues. > streams-util > streams-config > streams-core > streams-pojo > streams-pojo-extensions > streams-schemas/* > streams-verbs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-424) Add maven-surefire-plugin and modify POM to be able to run unit tests in parallel
[ https://issues.apache.org/jira/browse/STREAMS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-424. --- Resolution: Won't Fix Fix Version/s: (was: 0.5) 0.4.1 Resolving this as 'Won't Fix', can revisit this once streams-local and streams-monitoring are re-implemented. > Add maven-surefire-plugin and modify POM to be able to run unit tests in > parallel > - > > Key: STREAMS-424 > URL: https://issues.apache.org/jira/browse/STREAMS-424 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.3 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.4.1 > > > Add maven-surefire-plugin and modify POM to be able to run unit tests in > parallel. Presently the tests are run sequentially and the build takes a very > long time to complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (STREAMS-196) Implement Datum Monitoring through JMX
[ https://issues.apache.org/jira/browse/STREAMS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi closed STREAMS-196. - > Implement Datum Monitoring through JMX > -- > > Key: STREAMS-196 > URL: https://issues.apache.org/jira/browse/STREAMS-196 > Project: Streams > Issue Type: Improvement >Reporter: Ryan Ebanks > Fix For: 0.2 > > > Allow datum monitoring through JMX > * Implement class that will replace Datum Countable > * Depricate DatumCountable > * Change StreamsTasks to use new classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-196) Implement Datum Monitoring through JMX
[ https://issues.apache.org/jira/browse/STREAMS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-196. --- Resolution: Fixed Fix Version/s: 0.2 > Implement Datum Monitoring through JMX > -- > > Key: STREAMS-196 > URL: https://issues.apache.org/jira/browse/STREAMS-196 > Project: Streams > Issue Type: Improvement >Reporter: Ryan Ebanks > Fix For: 0.2 > > > Allow datum monitoring through JMX > * Implement class that will replace Datum Countable > * Depricate DatumCountable > * Change StreamsTasks to use new classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (STREAMS-441) Remove compile dependency on guava for core packages
[ https://issues.apache.org/jira/browse/STREAMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-441 started by Suneel Marthi. - > Remove compile dependency on guava for core packages > > > Key: STREAMS-441 > URL: https://issues.apache.org/jira/browse/STREAMS-441 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4.1 > > > To simplify the transitive dependency tree and reduce odds of users hitting > shading issues. > streams-util > streams-config > streams-core > streams-pojo > streams-pojo-extensions > streams-schemas/* > streams-verbs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-423) reboot: cleanup source code using import .*;
[ https://issues.apache.org/jira/browse/STREAMS-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696535#comment-15696535 ] Suneel Marthi commented on STREAMS-423: --- I guess this would have been addressed by checkstyle ? > reboot: cleanup source code using import .*; > > > Key: STREAMS-423 > URL: https://issues.apache.org/jira/browse/STREAMS-423 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > > as ~smarthi mentioned, using import .*; is bad practice > correct this in the >100 files where it occurs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-316) add “apache’ to the artifact name
[ https://issues.apache.org/jira/browse/STREAMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696531#comment-15696531 ] Suneel Marthi commented on STREAMS-316: --- Do we still wanna address this? > add “apache’ to the artifact name > - > > Key: STREAMS-316 > URL: https://issues.apache.org/jira/browse/STREAMS-316 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi >Priority: Trivial > Fix For: 0.5 > > > Suggestions from 0.2-rc3 vote: > - You may want to consider adding “apache’ to the artifact name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-451) Remove CHANGELOG.md
[ https://issues.apache.org/jira/browse/STREAMS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-451. --- Resolution: Fixed Assignee: Suneel Marthi Fix Version/s: 0.5 > Remove CHANGELOG.md > --- > > Key: STREAMS-451 > URL: https://issues.apache.org/jira/browse/STREAMS-451 > Project: Streams > Issue Type: Task >Reporter: Joey Frazee >Assignee: Suneel Marthi > Fix For: 0.5 > > > CHANGELOG.md hasn't been updated for the last two releases (since 0.2) and is > mostly redundant with stuff that could be automatically generated out of JIRA > or GitHub, so it's probably best off to remove it and link to JIRA or GitHub. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-439) Maven plugin that can validate all classes meet certain criteria.
[ https://issues.apache.org/jira/browse/STREAMS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-439. --- Resolution: Fixed > Maven plugin that can validate all classes meet certain criteria. > - > > Key: STREAMS-439 > URL: https://issues.apache.org/jira/browse/STREAMS-439 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Time Spent: 0.25h > Remaining Estimate: 0h > > To start with, that there is a minimal javadoc header. > Align enforcement with requirements documented by STREAMS-348 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-455) LICENSE, NOTICE and DISCLAIMER in source control.
[ https://issues.apache.org/jira/browse/STREAMS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691574#comment-15691574 ] Suneel Marthi commented on STREAMS-455: --- If we merge Master and project, one less thing to worry about by way of maintaining licenses. > LICENSE, NOTICE and DISCLAIMER in source control. > - > > Key: STREAMS-455 > URL: https://issues.apache.org/jira/browse/STREAMS-455 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > per discussion on IPMC mailing list during 0.4 release, the -master and > -examples git repositories should have a root LICENSE, NOTICE and DISCLAIMER > checked into source control. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-316) add “apache’ to the artifact name
[ https://issues.apache.org/jira/browse/STREAMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi updated STREAMS-316: -- Fix Version/s: (was: 0.4) 0.5 > add “apache’ to the artifact name > - > > Key: STREAMS-316 > URL: https://issues.apache.org/jira/browse/STREAMS-316 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Suneel Marthi >Priority: Trivial > Fix For: 0.5 > > > Suggestions from 0.2-rc3 vote: > - You may want to consider adding “apache’ to the artifact name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-446) RAT check fails in prep for 0.4-incubating release
[ https://issues.apache.org/jira/browse/STREAMS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-446. --- Resolution: Fixed > RAT check fails in prep for 0.4-incubating release > -- > > Key: STREAMS-446 > URL: https://issues.apache.org/jira/browse/STREAMS-446 > Project: Streams > Issue Type: Bug >Affects Versions: 0.3 >Reporter: Suneel Marthi >Assignee: Joey Frazee > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-447) Scala-plugin failures in prep for 0.4-incubating release
[ https://issues.apache.org/jira/browse/STREAMS-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-447. --- Resolution: Fixed > Scala-plugin failures in prep for 0.4-incubating release > > > Key: STREAMS-447 > URL: https://issues.apache.org/jira/browse/STREAMS-447 > Project: Streams > Issue Type: Bug >Affects Versions: 0.3 >Reporter: Suneel Marthi >Assignee: Suneel Marthi > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-447) Scala-plugin failures in prep for 0.4-incubating release
Suneel Marthi created STREAMS-447: - Summary: Scala-plugin failures in prep for 0.4-incubating release Key: STREAMS-447 URL: https://issues.apache.org/jira/browse/STREAMS-447 Project: Streams Issue Type: Bug Affects Versions: 0.3 Reporter: Suneel Marthi Assignee: Suneel Marthi Fix For: 0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-446) RAT check fails in prep for 0.4-incubating release
Suneel Marthi created STREAMS-446: - Summary: RAT check fails in prep for 0.4-incubating release Key: STREAMS-446 URL: https://issues.apache.org/jira/browse/STREAMS-446 Project: Streams Issue Type: Bug Affects Versions: 0.3 Reporter: Suneel Marthi Assignee: Joey Frazee Fix For: 0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-411) ability (and instructions on how) to run providers directly from console
[ https://issues.apache.org/jira/browse/STREAMS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-411. --- Resolution: Fixed > ability (and instructions on how) to run providers directly from console > > > Key: STREAMS-411 > URL: https://issues.apache.org/jira/browse/STREAMS-411 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.4 > > > All of the providers currently require attachment to a run-time to use. > If providers could be configured and executed directly from the console, they > would become more valuable for casual use cases where users just want to > easily grab documents without writing or deploying custom code. > This would probably take the form of adding a main method and perhaps a > Runnable trait to each provider, that when launched resolves the appropriate > typesafe config, starts up the provider, and pulls documents out of the > outbound queue and writes them to STDOUT as long as the streams is running. > Instructions how to do this should also be added to the javadocs of the > providers and/or the markdowns of each module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-159) Add facebook page feed provider
[ https://issues.apache.org/jira/browse/STREAMS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-159. --- Resolution: Fixed > Add facebook page feed provider > --- > > Key: STREAMS-159 > URL: https://issues.apache.org/jira/browse/STREAMS-159 > Project: Streams > Issue Type: Bug >Reporter: Ryan Ebanks >Assignee: Steve Blackmon > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-436) Put a timeout on all Provider Integration Tests
[ https://issues.apache.org/jira/browse/STREAMS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-436. --- Resolution: Fixed > Put a timeout on all Provider Integration Tests > > > Key: STREAMS-436 > URL: https://issues.apache.org/jira/browse/STREAMS-436 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.4 > > > They should not be able to halt the build indefinitely if they have problems. > This has happened several time on Jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-437) DatumFromMetadataProcessorIT failing during 0.4 release
[ https://issues.apache.org/jira/browse/STREAMS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-437. --- Resolution: Fixed > DatumFromMetadataProcessorIT failing during 0.4 release > --- > > Key: STREAMS-437 > URL: https://issues.apache.org/jira/browse/STREAMS-437 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > > DatumFromMetadataProcessorIT is failing during 0.4 release. > Figure out why and fix -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-158) Sysomos Processor exceptions result in failed processor thread
[ https://issues.apache.org/jira/browse/STREAMS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15599938#comment-15599938 ] Suneel Marthi commented on STREAMS-158: --- Sorry that should read Sysomos. > Sysomos Processor exceptions result in failed processor thread > -- > > Key: STREAMS-158 > URL: https://issues.apache.org/jira/browse/STREAMS-158 > Project: Streams > Issue Type: Bug >Reporter: Matt Franklin > Fix For: 0.3 > > > Sysomos Processor exceptions result in failed processor thread -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-413) Update dependency and plugin versions - Q4 2016
[ https://issues.apache.org/jira/browse/STREAMS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-413. --- Resolution: Fixed Assignee: Suneel Marthi (was: Steve Blackmon) fixed by streams-master PR#9 > Update dependency and plugin versions - Q4 2016 > --- > > Key: STREAMS-413 > URL: https://issues.apache.org/jira/browse/STREAMS-413 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > > Update dependency and plugin versions in poms through-out > incubator-streams-master and streams-project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-132) RegexUtils does not ensure that content is non-null
[ https://issues.apache.org/jira/browse/STREAMS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-132. --- Resolution: Fixed Fix Version/s: 0.4 Resolved by STREAMS-431 > RegexUtils does not ensure that content is non-null > --- > > Key: STREAMS-132 > URL: https://issues.apache.org/jira/browse/STREAMS-132 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas >Assignee: Joey Frazee > Fix For: 0.4 > > Original Estimate: 1h > Remaining Estimate: 1h > > In the getMatches function of the RegexUtils class, the content object that > gets passed in is not checked to ensure that it is non-null. When a null > content is passed in, a RunTimeException is thrown and that stream is > effectively blocked. > A solution to this problem is to check to see if the content is null before > trying to find matches on it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-432) Update to Java 8
[ https://issues.apache.org/jira/browse/STREAMS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-432. --- Resolution: Fixed Fix Version/s: 0.4 > Update to Java 8 > > > Key: STREAMS-432 > URL: https://issues.apache.org/jira/browse/STREAMS-432 > Project: Streams > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joey Frazee > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-258) Prevent signing of .asc, .m5, and .sha1 artifacts
[ https://issues.apache.org/jira/browse/STREAMS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15599912#comment-15599912 ] Suneel Marthi commented on STREAMS-258: --- You may want to disable maven-gpg-plugin in POM, that should prevent the double signing OR Remove the gpg credentials from apache-release profile in ur .m2/settings.xml > Prevent signing of .asc, .m5, and .sha1 artifacts > - > > Key: STREAMS-258 > URL: https://issues.apache.org/jira/browse/STREAMS-258 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon > > 0.1-rc1 wound up with superfluous signatures. gpg-maven-plugin is supposed > to exclude .asc, .m5, and .sha1 artifacts but apparently did not. figure out > why and fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-434) Delete CustomDateTimeFormat which is not used anywhere
[ https://issues.apache.org/jira/browse/STREAMS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-434. --- Resolution: Fixed > Delete CustomDateTimeFormat which is not used anywhere > -- > > Key: STREAMS-434 > URL: https://issues.apache.org/jira/browse/STREAMS-434 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STREAMS-434) Delete CustomDateTimeFormat which is not used anywhere
[ https://issues.apache.org/jira/browse/STREAMS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-434: - Assignee: Suneel Marthi (was: Steve Blackmon) > Delete CustomDateTimeFormat which is not used anywhere > -- > > Key: STREAMS-434 > URL: https://issues.apache.org/jira/browse/STREAMS-434 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (STREAMS-276) Upgrade providers to supply StreamsDateTimeFormat, DocumentClassifier, and ActivityConverter implementations
[ https://issues.apache.org/jira/browse/STREAMS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi closed STREAMS-276. - > Upgrade providers to supply StreamsDateTimeFormat, DocumentClassifier, and > ActivityConverter implementations > > > Key: STREAMS-276 > URL: https://issues.apache.org/jira/browse/STREAMS-276 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon > Fix For: 0.3 > > > For each provider where the proposed re-factoring improvement is feasible, > create sub-tasks to perform the following: > 1) Add DocumentClassifier(s) capable of classifying each provider-specific > type combination the provider expects to receive from all upstream end-points. > 2) Add a test demonstrating one and only one of these Classifiers returns > true across a set of example origin documents. > 3) Add an ActivityConverter for each objectType/Verb combination the provider > expects to emit. requiredClass should be one of String.class, > ObjectNode.class, or a POJO which extends Serializable. > 4) Add tests demonstrating that individual ActivityConverters are able to > convert the set of example origin documents into activities with correct > objectType/verb. > 5) Add tests demonstrating that ActivityConverterProcessor is able to convert > the set of example origin documents into activities with correct > objectType/verb. > 6) Add a StreamsDateTimeFormat for each non-RFC3339 date string the provider > expects to receive. > 7) Add a test demonstrating that StreamsJacksonMapper is able to convert > matching date strings to DateTimes. > 8) Mark legacy TypeConverters as Deprecated, or delete if they are now > unmaintainable. > 9) Mark legacy EventClassifiers as Deprecated, or delete if they are now > unmaintainable. > 10) Mark legacy StreamsMappers as Deprecated, or delete if they are now > unmaintainable. > For any provider where the proposed re-factoring improvement is not feasible, > document why in the module README and/or create issues for whatever > refactoring would be necessary to make that provider compatible with > ActivityConverterProcessor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-276) Upgrade providers to supply StreamsDateTimeFormat, DocumentClassifier, and ActivityConverter implementations
[ https://issues.apache.org/jira/browse/STREAMS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-276. --- Resolution: Fixed Fix Version/s: 0.3 > Upgrade providers to supply StreamsDateTimeFormat, DocumentClassifier, and > ActivityConverter implementations > > > Key: STREAMS-276 > URL: https://issues.apache.org/jira/browse/STREAMS-276 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon > Fix For: 0.3 > > > For each provider where the proposed re-factoring improvement is feasible, > create sub-tasks to perform the following: > 1) Add DocumentClassifier(s) capable of classifying each provider-specific > type combination the provider expects to receive from all upstream end-points. > 2) Add a test demonstrating one and only one of these Classifiers returns > true across a set of example origin documents. > 3) Add an ActivityConverter for each objectType/Verb combination the provider > expects to emit. requiredClass should be one of String.class, > ObjectNode.class, or a POJO which extends Serializable. > 4) Add tests demonstrating that individual ActivityConverters are able to > convert the set of example origin documents into activities with correct > objectType/verb. > 5) Add tests demonstrating that ActivityConverterProcessor is able to convert > the set of example origin documents into activities with correct > objectType/verb. > 6) Add a StreamsDateTimeFormat for each non-RFC3339 date string the provider > expects to receive. > 7) Add a test demonstrating that StreamsJacksonMapper is able to convert > matching date strings to DateTimes. > 8) Mark legacy TypeConverters as Deprecated, or delete if they are now > unmaintainable. > 9) Mark legacy EventClassifiers as Deprecated, or delete if they are now > unmaintainable. > 10) Mark legacy StreamsMappers as Deprecated, or delete if they are now > unmaintainable. > For any provider where the proposed re-factoring improvement is not feasible, > document why in the module README and/or create issues for whatever > refactoring would be necessary to make that provider compatible with > ActivityConverterProcessor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-412) ability (and instructions on how) to run processors directly from console
[ https://issues.apache.org/jira/browse/STREAMS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-412. --- Resolution: Fixed Fix Version/s: (was: 0.5) 0.4 > ability (and instructions on how) to run processors directly from console > - > > Key: STREAMS-412 > URL: https://issues.apache.org/jira/browse/STREAMS-412 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon > Fix For: 0.4 > > > All of the processors currently require attachment to a run-time to use. > If processors could be configured and executed directly from the console, > they would become more valuable for casual use cases where users just want to > easily transform documents without writing or deploying custom code. > This would probably take the form of adding a main method and perhaps a > Runnable trait to each processor, that when launched resolves the appropriate > typesafe config, starts up the process, and transforms documents from STDIN > writing them to STDOUT until the input stops. > Instructions how to do this should also be added to the javadocs of the > processors and/or the markdowns of each module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-399) Add any missing fields to tweet.json
[ https://issues.apache.org/jira/browse/STREAMS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-399. --- Resolution: Fixed Fix Version/s: 0.4 > Add any missing fields to tweet.json > > > Key: STREAMS-399 > URL: https://issues.apache.org/jira/browse/STREAMS-399 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.4 > > > Noticed some new fields in tweets: > is_quote_status > quoted_status_id > quoted_status > Add these and any other missing fields to tweet.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-399) Add any missing fields to tweet.json
[ https://issues.apache.org/jira/browse/STREAMS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15598250#comment-15598250 ] Suneel Marthi commented on STREAMS-399: --- I can take this on for 0.4 release. > Add any missing fields to tweet.json > > > Key: STREAMS-399 > URL: https://issues.apache.org/jira/browse/STREAMS-399 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > Noticed some new fields in tweets: > is_quote_status > quoted_status_id > quoted_status > Add these and any other missing fields to tweet.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-236) AbstractRegexExtensionExtractor should not allow duplicate entities
[ https://issues.apache.org/jira/browse/STREAMS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-236. --- Resolution: Won't Fix Fix Version/s: 0.3 > AbstractRegexExtensionExtractor should not allow duplicate entities > --- > > Key: STREAMS-236 > URL: https://issues.apache.org/jira/browse/STREAMS-236 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas > Fix For: 0.3 > > > AbstractRegexExtensionExtractor should not allow duplicate entities -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-122) Build appropriate serializer classes
[ https://issues.apache.org/jira/browse/STREAMS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-122. --- Resolution: Fixed Fix Version/s: 0.3 > Build appropriate serializer classes > > > Key: STREAMS-122 > URL: https://issues.apache.org/jira/browse/STREAMS-122 > Project: Streams > Issue Type: Sub-task >Reporter: Steve Blackmon > Fix For: 0.3 > > > Build appropriate serializer classes for Instagram object types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-186) Platform-level 'detectConfiguration'
[ https://issues.apache.org/jira/browse/STREAMS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi resolved STREAMS-186. --- Resolution: Fixed Fix Version/s: 0.4 Implemented both Streams-215 and Streams-217 > Platform-level 'detectConfiguration' > > > Key: STREAMS-186 > URL: https://issues.apache.org/jira/browse/STREAMS-186 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > > Many modules are currently providing Configurator classes that all do pretty > much the same thing: typesafe -> jackson -> pojo. Provide a static generic > method in streams-config that reduces the amount of duplicated / redundant > code and deprecate all or some of the module-internal Configurators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-186) Platform-level 'detectConfiguration'
[ https://issues.apache.org/jira/browse/STREAMS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15596159#comment-15596159 ] Suneel Marthi commented on STREAMS-186: --- Gonna mark this as 'Resolved' since both the sub-tasks are now complete. > Platform-level 'detectConfiguration' > > > Key: STREAMS-186 > URL: https://issues.apache.org/jira/browse/STREAMS-186 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon > > Many modules are currently providing Configurator classes that all do pretty > much the same thing: typesafe -> jackson -> pojo. Provide a static generic > method in streams-config that reduces the amount of duplicated / redundant > code and deprecate all or some of the module-internal Configurators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (STREAMS-217) Delete unneeded Configurator classes
[ https://issues.apache.org/jira/browse/STREAMS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-217 started by Suneel Marthi. - > Delete unneeded Configurator classes > > > Key: STREAMS-217 > URL: https://issues.apache.org/jira/browse/STREAMS-217 > Project: Streams > Issue Type: Sub-task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > > Quick hit list: Delete or at least @Deprecate each of these classes > GMailConfigurator.java > GPlusConfigurator.java > HttpConfigurator.java > ElasticsearchConfigurator.java > HbaseConfigurator.java > HdfsConfigurator.java > KafkaConfigurator.java > MongoConfigurator.java > S3Configurator.java > DatasiftStreamConfigurator.java > FacebookStreamConfigurator.java > InstagramConfigurator.java > MoreoverConfigurator.java > RssStreamConfigurator.java > SysomosConfigurator.java > TwitterConfigurator.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STREAMS-217) Delete unneeded Configurator classes
[ https://issues.apache.org/jira/browse/STREAMS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suneel Marthi reassigned STREAMS-217: - Assignee: Suneel Marthi > Delete unneeded Configurator classes > > > Key: STREAMS-217 > URL: https://issues.apache.org/jira/browse/STREAMS-217 > Project: Streams > Issue Type: Sub-task >Reporter: Steve Blackmon >Assignee: Suneel Marthi > Fix For: 0.4 > > > Quick hit list: Delete or at least @Deprecate each of these classes > GMailConfigurator.java > GPlusConfigurator.java > HttpConfigurator.java > ElasticsearchConfigurator.java > HbaseConfigurator.java > HdfsConfigurator.java > KafkaConfigurator.java > MongoConfigurator.java > S3Configurator.java > DatasiftStreamConfigurator.java > FacebookStreamConfigurator.java > InstagramConfigurator.java > MoreoverConfigurator.java > RssStreamConfigurator.java > SysomosConfigurator.java > TwitterConfigurator.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-227) Array out of bounds Exception running FacebookTypeConverter
[
https://issues.apache.org/jira/browse/STREAMS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi resolved STREAMS-227.
---
Resolution: Fixed
> Array out of bounds Exception running FacebookTypeConverter
> ---
>
> Key: STREAMS-227
> URL: https://issues.apache.org/jira/browse/STREAMS-227
> Project: Streams
> Issue Type: Bug
>Reporter: Steve Blackmon
>
> Facebookactivityutil : line 211 need to make sure that array has at least one
> element
> 83601 [pool-1-thread-1] ERROR o.a.s.f.p.FacebookTypeConverter - Exception
> switching types : {}
> 13:20:48 java.lang.IndexOutOfBoundsException: Index: 0,
> Size: 0
> 13:20:48 at
> java.util.ArrayList.rangeCheck(ArrayList.java:635) ~[na:1.7.0_67]
> 13:20:48 at
> java.util.ArrayList.get(ArrayList.java:411) ~[na:1.7.0_67]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (STREAMS-227) Array out of bounds Exception running FacebookTypeConverter
[
https://issues.apache.org/jira/browse/STREAMS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi updated STREAMS-227:
--
Fix Version/s: 0.3
> Array out of bounds Exception running FacebookTypeConverter
> ---
>
> Key: STREAMS-227
> URL: https://issues.apache.org/jira/browse/STREAMS-227
> Project: Streams
> Issue Type: Bug
>Reporter: Steve Blackmon
> Fix For: 0.3
>
>
> Facebookactivityutil : line 211 need to make sure that array has at least one
> element
> 83601 [pool-1-thread-1] ERROR o.a.s.f.p.FacebookTypeConverter - Exception
> switching types : {}
> 13:20:48 java.lang.IndexOutOfBoundsException: Index: 0,
> Size: 0
> 13:20:48 at
> java.util.ArrayList.rangeCheck(ArrayList.java:635) ~[na:1.7.0_67]
> 13:20:48 at
> java.util.ArrayList.get(ArrayList.java:411) ~[na:1.7.0_67]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (STREAMS-227) Array out of bounds Exception running FacebookTypeConverter
[
https://issues.apache.org/jira/browse/STREAMS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suneel Marthi closed STREAMS-227.
-
> Array out of bounds Exception running FacebookTypeConverter
> ---
>
> Key: STREAMS-227
> URL: https://issues.apache.org/jira/browse/STREAMS-227
> Project: Streams
> Issue Type: Bug
>Reporter: Steve Blackmon
> Fix For: 0.3
>
>
> Facebookactivityutil : line 211 need to make sure that array has at least one
> element
> 83601 [pool-1-thread-1] ERROR o.a.s.f.p.FacebookTypeConverter - Exception
> switching types : {}
> 13:20:48 java.lang.IndexOutOfBoundsException: Index: 0,
> Size: 0
> 13:20:48 at
> java.util.ArrayList.rangeCheck(ArrayList.java:635) ~[na:1.7.0_67]
> 13:20:48 at
> java.util.ArrayList.get(ArrayList.java:411) ~[na:1.7.0_67]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
