[jira] [Created] (STREAMS-522) Remove mention of incubating status from code and web site
Steve Blackmon created STREAMS-522: -- Summary: Remove mention of incubating status from code and web site Key: STREAMS-522 URL: https://issues.apache.org/jira/browse/STREAMS-522 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon Remove mention of incubating status from code and web site -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (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 ] Steve Blackmon reopened STREAMS-480: Re-opening now that project has graduated 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.4.14#64029)
[jira] [Created] (STREAMS-521) Add support for twitter direct message events and web hook events
Steve Blackmon created STREAMS-521: -- Summary: Add support for twitter direct message events and web hook events Key: STREAMS-521 URL: https://issues.apache.org/jira/browse/STREAMS-521 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Add support for twitter direct message events and web hook events -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-520) Standardize how accounts of interest are enumerated to Providers
Steve Blackmon created STREAMS-520: -- Summary: Standardize how accounts of interest are enumerated to Providers Key: STREAMS-520 URL: https://issues.apache.org/jira/browse/STREAMS-520 Project: Streams Issue Type: Improvement Components: Providers Reporter: Steve Blackmon Assignee: Steve Blackmon Providers that pull details on a finite set of accounts are not currently consistent. Some accept an array of object internal to the module (gplus and youtube) while others accept an array of strings (twitter, facebook, instagram). There's no reason or benefit to this situation. It would be easier to build a set of integrated compatible pipelines if we harmonized these pipeline configuration beans, and there would be less low-value config mangling code in each module to understand, test, and maintain. I suggest that all providers that research a finite set of accounts supplied in a configuration object, should accept (only) an activity streams collection of optionally typed activityobjects, with either the id or some other identifying criteria populated such that the provider can locate the appropriate upstream object. Also, the standard use of ids should use the activity streams format of the id rather than the native format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (STREAMS-519) Support parsing dates with micro and nano precision with StreamsJacksonMapper
[ https://issues.apache.org/jira/browse/STREAMS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079674#comment-16079674 ] Steve Blackmon commented on STREAMS-519: I think the trick here is to configure sub second precision using joda builder instead of just format strings. public static final DateTimeFormatter UTC_SUB_SECOND_FMT = new DateTimeFormatterBuilder().appendPattern(BASE_FMT).appendLiteral(".").appendFractionOfSecond(1, 9).toFormatter().withZoneUTC(); Also we've got a legacy RFC3339Utils class that does a lot of heavy lifting but outside the provided framework where a list of formats are provided when getting an instance of StreamsJacksonMapper. That's problematic because adding global support for a new format requires a code change instead of a config change. My goal is to deprecate RFC3339Utils as part of this change without changing how StreamsJacksonMapper is used in typical cases. > Support parsing dates with micro and nano precision with StreamsJacksonMapper > - > > Key: STREAMS-519 > URL: https://issues.apache.org/jira/browse/STREAMS-519 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > StreamsJacksonMapper does not currently seem to support parsing dates with > greater than millisecond precision. Not surprising as Joda supports millis > as its smallest interval, but it should be possible at least to parse a date > with greater precision without throwing an exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-519) Support parsing dates with micro and nano precision with StreamsJacksonMapper
Steve Blackmon created STREAMS-519: -- Summary: Support parsing dates with micro and nano precision with StreamsJacksonMapper Key: STREAMS-519 URL: https://issues.apache.org/jira/browse/STREAMS-519 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon StreamsJacksonMapper does not currently seem to support parsing dates with greater than millisecond precision. Not surprising as Joda supports millis as its smallest interval, but it should be possible at least to parse a date with greater precision without throwing an exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-518) Support java.util.Date fields with StreamsJacksonMapper
Steve Blackmon created STREAMS-518: -- Summary: Support java.util.Date fields with StreamsJacksonMapper Key: STREAMS-518 URL: https://issues.apache.org/jira/browse/STREAMS-518 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon StreamsJacksonMapper support serializing and deserializing arbitrary formats to org.joda.time.DateTime very well. It should be able to do the same using java.util.Date, retaining the same configuration and processing mechanisms -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-517) compile error in streams-provider-instagram in master
[ https://issues.apache.org/jira/browse/STREAMS-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-517. Resolution: Fixed https://builds.apache.org/job/streams-project/380/ > compile error in streams-provider-instagram in master > - > > Key: STREAMS-517 > URL: https://issues.apache.org/jira/browse/STREAMS-517 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > https://builds.apache.org/job/streams-project/378/console -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-517) compile error in streams-provider-instagram in master
Steve Blackmon created STREAMS-517: -- Summary: compile error in streams-provider-instagram in master Key: STREAMS-517 URL: https://issues.apache.org/jira/browse/STREAMS-517 Project: Streams Issue Type: Bug Reporter: Steve Blackmon Assignee: Steve Blackmon https://builds.apache.org/job/streams-project/378/console -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-505) Add ASFv2 Licenses
[ https://issues.apache.org/jira/browse/STREAMS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-505. Resolution: Fixed > Add ASFv2 Licenses > -- > > Key: STREAMS-505 > URL: https://issues.apache.org/jira/browse/STREAMS-505 > Project: Streams > Issue Type: Bug > Components: Build >Affects Versions: 0.5.1 >Reporter: Trevor Grant >Assignee: Steve Blackmon > > publish-rc.sh > release.sh > src/main/resources/streams-java-checkstyle.xml > src/main/resources/streams-java-intellij.xml > all need asf-v2 licenses -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-512) Add @BeanProperty annotations in addition to @JsonProperty
[ https://issues.apache.org/jira/browse/STREAMS-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-512. Resolution: Fixed > Add @BeanProperty annotations in addition to @JsonProperty > -- > > Key: STREAMS-512 > URL: https://issues.apache.org/jira/browse/STREAMS-512 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > to getters, setters, anyGetter, and anySetter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-508) Utilize new third-party rest proxy capability in provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-508. Resolution: Fixed > Utilize new third-party rest proxy capability in provider-twitter > - > > Key: STREAMS-508 > URL: https://issues.apache.org/jira/browse/STREAMS-508 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STREAMS-516) switch @BeanProperty annotations to value
[ https://issues.apache.org/jira/browse/STREAMS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-516. Resolution: Fixed > switch @BeanProperty annotations to value > - > > Key: STREAMS-516 > URL: https://issues.apache.org/jira/browse/STREAMS-516 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > switch @BeanProperty annotations produced by streams-plugin-pojo > JuneauAnnotator to use value instead of name. this aligns better with the > jackson annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-516) switch @BeanProperty annotations to value
Steve Blackmon created STREAMS-516: -- Summary: switch @BeanProperty annotations to value Key: STREAMS-516 URL: https://issues.apache.org/jira/browse/STREAMS-516 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon switch @BeanProperty annotations produced by streams-plugin-pojo JuneauAnnotator to use value instead of name. this aligns better with the jackson annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (STREAMS-515) Look into simplifying message signing logic using URLEncodedUtils.parse
[ https://issues.apache.org/jira/browse/STREAMS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056893#comment-16056893 ] Steve Blackmon commented on STREAMS-515: Attached a patch file that switching use of Mapto List and uses URLEncodedUtil. But the unit tests still need to be made to pass. > Look into simplifying message signing logic using URLEncodedUtils.parse > --- > > Key: STREAMS-515 > URL: https://issues.apache.org/jira/browse/STREAMS-515 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > Feedback from https://github.com/apache/incubator-streams/pull/368 > Non-trivial change but would reduce lines of code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (STREAMS-515) Look into simplifying message signing logic using URLEncodedUtils.parse
[ https://issues.apache.org/jira/browse/STREAMS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056893#comment-16056893 ] Steve Blackmon edited comment on STREAMS-515 at 6/21/17 2:49 AM: - Attached a patch file that switches use of Mapto List and uses URLEncodedUtil. But the unit tests still need to be made to pass. was (Author: steveblackmon): Attached a patch file that switching use of Map to List and uses URLEncodedUtil. But the unit tests still need to be made to pass. > Look into simplifying message signing logic using URLEncodedUtils.parse > --- > > Key: STREAMS-515 > URL: https://issues.apache.org/jira/browse/STREAMS-515 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > Feedback from https://github.com/apache/incubator-streams/pull/368 > Non-trivial change but would reduce lines of code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-515) Look into simplifying message signing logic using URLEncodedUtils.parse
Steve Blackmon created STREAMS-515: -- Summary: Look into simplifying message signing logic using URLEncodedUtils.parse Key: STREAMS-515 URL: https://issues.apache.org/jira/browse/STREAMS-515 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Feedback from https://github.com/apache/incubator-streams/pull/368 Non-trivial change but would reduce lines of code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-514) Scope scala-lang and scala-reflect optional in streams-pojo
Steve Blackmon created STREAMS-514: -- Summary: Scope scala-lang and scala-reflect optional in streams-pojo Key: STREAMS-514 URL: https://issues.apache.org/jira/browse/STREAMS-514 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Scala 2.10 should not be a transitive dependency of streams-pojo. It should be scoped optional at a minimum, or scala bindings and helpers should be factored out into another module the user can choose to import or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STREAMS-513) Utilize new third-party rest proxy capability in provider-instagram
Steve Blackmon created STREAMS-513: -- Summary: Utilize new third-party rest proxy capability in provider-instagram Key: STREAMS-513 URL: https://issues.apache.org/jira/browse/STREAMS-513 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-508) Utilize new third-party rest proxy capability in provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-508: --- Summary: Utilize new third-party rest proxy capability in provider-twitter (was: Utilize new third-party rest proxy capability in provider-twitter and provider-instagram) > Utilize new third-party rest proxy capability in provider-twitter > - > > Key: STREAMS-508 > URL: https://issues.apache.org/jira/browse/STREAMS-508 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-508) Utilize new third-party rest proxy capability in provider-twitter and provider-instagram
[ https://issues.apache.org/jira/browse/STREAMS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045649#comment-16045649 ] Steve Blackmon commented on STREAMS-508: I'm changing STREAMS-508 to only cover twitter and cloning a new issue to cover instagram > Utilize new third-party rest proxy capability in provider-twitter and > provider-instagram > > > Key: STREAMS-508 > URL: https://issues.apache.org/jira/browse/STREAMS-508 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-500) Remove jackson-datatype-json-org from project
[ https://issues.apache.org/jira/browse/STREAMS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-500. Resolution: Fixed Assignee: Steve Blackmon > Remove jackson-datatype-json-org from project > - > > Key: STREAMS-500 > URL: https://issues.apache.org/jira/browse/STREAMS-500 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5.1 > > > Remove jackson-datatype-json-org from project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-508) Utilize new third-party rest proxy capability in provider-twitter and provider-instagram
[ https://issues.apache.org/jira/browse/STREAMS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-508 started by Steve Blackmon. -- > Utilize new third-party rest proxy capability in provider-twitter and > provider-instagram > > > Key: STREAMS-508 > URL: https://issues.apache.org/jira/browse/STREAMS-508 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (STREAMS-506) Missing ASFv2 License in Instagram Provider
[ https://issues.apache.org/jira/browse/STREAMS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon reassigned STREAMS-506: -- Assignee: Trevor Grant > Missing ASFv2 License in Instagram Provider > --- > > Key: STREAMS-506 > URL: https://issues.apache.org/jira/browse/STREAMS-506 > Project: Streams > Issue Type: Bug >Affects Versions: 0.5.1 >Reporter: Trevor Grant >Assignee: Trevor Grant > > Missing license in > streams-contrib/streams-provider-instagram/src/main/java/org/apache/streams/instagram/api/InstagramOAuthRequestSigner.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-506) Missing ASFv2 License in Instagram Provider
[ https://issues.apache.org/jira/browse/STREAMS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-506. Resolution: Fixed > Missing ASFv2 License in Instagram Provider > --- > > Key: STREAMS-506 > URL: https://issues.apache.org/jira/browse/STREAMS-506 > Project: Streams > Issue Type: Bug >Affects Versions: 0.5.1 >Reporter: Trevor Grant >Assignee: Trevor Grant > > Missing license in > streams-contrib/streams-provider-instagram/src/main/java/org/apache/streams/instagram/api/InstagramOAuthRequestSigner.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-509) Slack.com provider
[ https://issues.apache.org/jira/browse/STREAMS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020767#comment-16020767 ] Steve Blackmon commented on STREAMS-509: got basic tests working. added a few other info and list endpoints for grins. > Slack.com provider > -- > > Key: STREAMS-509 > URL: https://issues.apache.org/jira/browse/STREAMS-509 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Write a provider for https://api.slack.com/ > Basic capabilities: > authentication > get all profiles in an organization > get all channels in an organization > get recent posts in a channel -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-512) Add @BeanProperty annotations in addition to @JsonProperty
[ https://issues.apache.org/jira/browse/STREAMS-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-512 started by Steve Blackmon. -- > Add @BeanProperty annotations in addition to @JsonProperty > -- > > Key: STREAMS-512 > URL: https://issues.apache.org/jira/browse/STREAMS-512 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > to getters, setters, anyGetter, and anySetter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-512) Add @BeanProperty annotations in addition to @JsonProperty
Steve Blackmon created STREAMS-512: -- Summary: Add @BeanProperty annotations in addition to @JsonProperty Key: STREAMS-512 URL: https://issues.apache.org/jira/browse/STREAMS-512 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon to getters, setters, anyGetter, and anySetter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-511) Rewrite streams-provider-facebook omitting facebook4j
Steve Blackmon created STREAMS-511: -- Summary: Rewrite streams-provider-facebook omitting facebook4j Key: STREAMS-511 URL: https://issues.apache.org/jira/browse/STREAMS-511 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Rewrite streams-provider-facebook omitting facebook4j Instead use juneau rest-proxy -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-509) Slack.com provider
[ https://issues.apache.org/jira/browse/STREAMS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018553#comment-16018553 ] Steve Blackmon commented on STREAMS-509: Pushed client implementation, interceptor, retrys, and integration tests https://github.com/apache/incubator-streams/compare/master...steveblackmon:STREAMS-509 > Slack.com provider > -- > > Key: STREAMS-509 > URL: https://issues.apache.org/jira/browse/STREAMS-509 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Write a provider for https://api.slack.com/ > Basic capabilities: > authentication > get all profiles in an organization > get all channels in an organization > get recent posts in a channel -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-509) Slack.com provider
[ https://issues.apache.org/jira/browse/STREAMS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018318#comment-16018318 ] Steve Blackmon commented on STREAMS-509: Pushed just pom, pojos, and interfaces to meet these base requirements https://github.com/steveblackmon/incubator-streams/commit/1e432f1451fa1b1ed31dac9ccc734655a1c60422 > Slack.com provider > -- > > Key: STREAMS-509 > URL: https://issues.apache.org/jira/browse/STREAMS-509 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Write a provider for https://api.slack.com/ > Basic capabilities: > authentication > get all profiles in an organization > get all channels in an organization > get recent posts in a channel -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-509) Slack.com provider
[ https://issues.apache.org/jira/browse/STREAMS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-509 started by Steve Blackmon. -- > Slack.com provider > -- > > Key: STREAMS-509 > URL: https://issues.apache.org/jira/browse/STREAMS-509 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Write a provider for https://api.slack.com/ > Basic capabilities: > authentication > get all profiles in an organization > get all channels in an organization > get recent posts in a channel -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-461) Proof-of-concept: package and test streams provider with beam APIs / local runner
[ https://issues.apache.org/jira/browse/STREAMS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-461 started by Steve Blackmon. -- > Proof-of-concept: package and test streams provider with beam APIs / local > runner > - > > Key: STREAMS-461 > URL: https://issues.apache.org/jira/browse/STREAMS-461 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Proof-of-concept: package and test streams provider with beam APIs / local > runner -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-510) Example Pipeline: Slack Digest
Steve Blackmon created STREAMS-510: -- Summary: Example Pipeline: Slack Digest Key: STREAMS-510 URL: https://issues.apache.org/jira/browse/STREAMS-510 Project: Streams Issue Type: New Feature Reporter: Steve Blackmon Assignee: Steve Blackmon Get the last X hours of activities within a specified slack channel Prepare a time-ordered text digest for the period containing: ${actor.displayName}: ${content} with urls within the content intact -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-509) Slack.com provider
Steve Blackmon created STREAMS-509: -- Summary: Slack.com provider Key: STREAMS-509 URL: https://issues.apache.org/jira/browse/STREAMS-509 Project: Streams Issue Type: New Feature Reporter: Steve Blackmon Assignee: Steve Blackmon Write a provider for https://api.slack.com/ Basic capabilities: authentication get all profiles in an organization get all channels in an organization get recent posts in a channel -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-508) Utilize new third-party rest proxy capability in provider-twitter and provider-instagram
Steve Blackmon created STREAMS-508: -- Summary: Utilize new third-party rest proxy capability in provider-twitter and provider-instagram Key: STREAMS-508 URL: https://issues.apache.org/jira/browse/STREAMS-508 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Requires upgrade juneau dependency to 6.2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-507) Jenkins is not deploying snapshots for org/apache/streams/plugins
Steve Blackmon created STREAMS-507: -- Summary: Jenkins is not deploying snapshots for org/apache/streams/plugins Key: STREAMS-507 URL: https://issues.apache.org/jira/browse/STREAMS-507 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon Fix For: 0.5.1 Every module in streams is getting a snapshot deployed when jenkins does a new build, except for the modules within streams-plugins -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-504) Juneau Example
Steve Blackmon created STREAMS-504: -- Summary: Juneau Example Key: STREAMS-504 URL: https://issues.apache.org/jira/browse/STREAMS-504 Project: Streams Issue Type: New Feature Reporter: Steve Blackmon Assignee: Steve Blackmon Example module demonstrating how to embed streams capabilities within a Juneau Microservice. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-502) Re-implement instagram providers using juneau libraries
[ https://issues.apache.org/jira/browse/STREAMS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-502. Resolution: Fixed Fix Version/s: 0.5.1 > Re-implement instagram providers using juneau libraries > --- > > Key: STREAMS-502 > URL: https://issues.apache.org/jira/browse/STREAMS-502 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5.1 > > Original Estimate: 4h > Time Spent: 1.15h > Remaining Estimate: 2.85h > > Get rid of jinstagram while keeping all of the same features / gaining POJOs. > This will simplify transitive dependencies, promote code re-use within the > project, and demonstrate the juneau model applied first in STREAMS-496 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-496) Remove twitter4j dependency from streams-provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-496. Resolution: Fixed > Remove twitter4j dependency from streams-provider-twitter > - > > Key: STREAMS-496 > URL: https://issues.apache.org/jira/browse/STREAMS-496 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > Per discussion on legal@ releases that include modules with the json license > are not permitted after April 30, 2017. > twitter4j has such a dependency and has shown little willingness to address > it. > Switch off twitter4j to HTTP API interaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-503) MediaLink class is not being generated in streams-pojo
[ https://issues.apache.org/jira/browse/STREAMS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-503: --- Summary: MediaLink class is not being generated in streams-pojo (was: MediaLink class is not being generated in streams-poco) > MediaLink class is not being generated in streams-pojo > -- > > Key: STREAMS-503 > URL: https://issues.apache.org/jira/browse/STREAMS-503 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > Rather it is generated, but it is named ImageParent. This is wrong. > MediaLink should be a class that can be used and extended in other modules. > Image should be an instance of MediaLink. > There don't appear to be any other cases like this in streams-pojo, but we > should check the entire project to make sure generated beans have the right > classnames. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work logged] (STREAMS-502) Re-implement instagram providers using juneau libraries
[ https://issues.apache.org/jira/browse/STREAMS-502?focusedWorklogId=41052=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-41052 ] Steve Blackmon logged work on STREAMS-502: -- Author: Steve Blackmon Created on: 11/Apr/17 23:40 Start Date: 11/Apr/17 22:31 Worklog Time Spent: 1.15h Issue Time Tracking --- Worklog Id: (was: 41052) Time Spent: 1.15h Remaining Estimate: 2.85h (was: 4h) > Re-implement instagram providers using juneau libraries > --- > > Key: STREAMS-502 > URL: https://issues.apache.org/jira/browse/STREAMS-502 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Original Estimate: 4h > Time Spent: 1.15h > Remaining Estimate: 2.85h > > Get rid of jinstagram while keeping all of the same features / gaining POJOs. > This will simplify transitive dependencies, promote code re-use within the > project, and demonstrate the juneau model applied first in STREAMS-496 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-503) MediaLink class is not being generated in streams-poco
Steve Blackmon created STREAMS-503: -- Summary: MediaLink class is not being generated in streams-poco Key: STREAMS-503 URL: https://issues.apache.org/jira/browse/STREAMS-503 Project: Streams Issue Type: Bug Reporter: Steve Blackmon Assignee: Steve Blackmon Rather it is generated, but it is named ImageParent. This is wrong. MediaLink should be a class that can be used and extended in other modules. Image should be an instance of MediaLink. There don't appear to be any other cases like this in streams-pojo, but we should check the entire project to make sure generated beans have the right classnames. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-502) Re-implement instagram providers using juneau libraries
Steve Blackmon created STREAMS-502: -- Summary: Re-implement instagram providers using juneau libraries Key: STREAMS-502 URL: https://issues.apache.org/jira/browse/STREAMS-502 Project: Streams Issue Type: Improvement Reporter: Steve Blackmon Assignee: Steve Blackmon Priority: Minor Get rid of jinstagram while keeping all of the same features / gaining POJOs. This will simplify transitive dependencies, promote code re-use within the project, and demonstrate the juneau model applied first in STREAMS-496 -- 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=15964932#comment-15964932 ] Steve Blackmon commented on STREAMS-420: In lead-up to graduation, each open ticket should have added to the description *why* certain tasks/changes should be done. If there's not a clear enough purpose for either the creator or assigner to do this, the issue should be closed won't fix. > 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.1 > > > 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] [Updated] (STREAMS-501) build a full dependency license report
[ https://issues.apache.org/jira/browse/STREAMS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-501: --- Summary: build a full dependency license report (was: build a full dependency report) > build a full dependency license report > -- > > Key: STREAMS-501 > URL: https://issues.apache.org/jira/browse/STREAMS-501 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > Build a full dependency report, across the entire project or at least one > report for all of streams-project and one for all of streams-examples. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-501) build a full dependency report
[ https://issues.apache.org/jira/browse/STREAMS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-501: --- Fix Version/s: 0.5.1 > build a full dependency report > -- > > Key: STREAMS-501 > URL: https://issues.apache.org/jira/browse/STREAMS-501 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > Build a full dependency report, across the entire project or at least one > report for all of streams-project and one for all of streams-examples. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-501) build a full dependency report
Steve Blackmon created STREAMS-501: -- Summary: build a full dependency report Key: STREAMS-501 URL: https://issues.apache.org/jira/browse/STREAMS-501 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon Priority: Minor Build a full dependency report, across the entire project or at least one report for all of streams-project and one for all of streams-examples. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-486) Update release script on website
[ https://issues.apache.org/jira/browse/STREAMS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-486. Resolution: Fixed > Update release script on website > > > Key: STREAMS-486 > URL: https://issues.apache.org/jira/browse/STREAMS-486 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Release script as it is now on the Release website is inadequate and doesn't > accurately describe the release process. > A lot of changes to project structure and poms have taken place recently. > > Prior to and during the next release > > let’s make an effort to cover every single step, placing details (such as > > how to create accounts and > > generate credentials for testing) to are relevant to users as well as > > release manager outside the body > > of the release process document. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-484) Update website to reflect deprecation of streams-master
[ https://issues.apache.org/jira/browse/STREAMS-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-484. Resolution: Fixed > Update website to reflect deprecation of streams-master > --- > > Key: STREAMS-484 > URL: https://issues.apache.org/jira/browse/STREAMS-484 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Update website to reflect deprecation of streams-master -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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=15959884#comment-15959884 ] Steve Blackmon commented on STREAMS-316: Let's do this once we are able to drop incubator- prefix, clean swap > 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.3.15#6346)
[jira] [Created] (STREAMS-500) Remove jackson-datatype-json-org from project
Steve Blackmon created STREAMS-500: -- Summary: Remove jackson-datatype-json-org from project Key: STREAMS-500 URL: https://issues.apache.org/jira/browse/STREAMS-500 Project: Streams Issue Type: Task Reporter: Steve Blackmon Fix For: 0.5.1 Remove jackson-datatype-json-org from project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-499) site:stage and site:publish problem with 0.5-incubating
[ https://issues.apache.org/jira/browse/STREAMS-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-499. Resolution: Fixed Fix Version/s: 0.5.1 > site:stage and site:publish problem with 0.5-incubating > --- > > Key: STREAMS-499 > URL: https://issues.apache.org/jira/browse/STREAMS-499 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > site:stage and site:publish don't work as expected on 0.5-incubating. > when staging the site, the sub-modules don't wind up in the right place. > same when publishing. > the cause is: > > > > scm:svn:https://svn.apache.org/repos/asf/incubator/streams/site/trunk/content/site/${project.version}/${project.artifactId} > > needs to be: > > scm:svn:https://svn.apache.org/repos/asf/incubator/streams/site/trunk/content/site/${project.version}/streams-project > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-499) site:stage and site:publish problem with 0.5-incubating
Steve Blackmon created STREAMS-499: -- Summary: site:stage and site:publish problem with 0.5-incubating Key: STREAMS-499 URL: https://issues.apache.org/jira/browse/STREAMS-499 Project: Streams Issue Type: Bug Reporter: Steve Blackmon Assignee: Steve Blackmon Priority: Minor site:stage and site:publish don't work as expected on 0.5-incubating. when staging the site, the sub-modules don't wind up in the right place. same when publishing. the cause is: scm:svn:https://svn.apache.org/repos/asf/incubator/streams/site/trunk/content/site/${project.version}/${project.artifactId} needs to be: scm:svn:https://svn.apache.org/repos/asf/incubator/streams/site/trunk/content/site/${project.version}/streams-project -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-493: --- Fix Version/s: (was: 0.5) 0.5.1 > 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-316) add “apache’ to the artifact name
[ https://issues.apache.org/jira/browse/STREAMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-316: --- Sprint: 0.5.1 > 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.3.15#6346)
[jira] [Updated] (STREAMS-420) reboot: cleanup JIRA
[ https://issues.apache.org/jira/browse/STREAMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-420: --- Sprint: 0.5.0, 0.5.1 (was: 0.5.0) > 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] [Updated] (STREAMS-420) reboot: cleanup JIRA
[ https://issues.apache.org/jira/browse/STREAMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-420: --- Sprint: 0.5.0 (was: 0.5.0, 0.6.0) > 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] [Updated] (STREAMS-486) Update release script on website
[ https://issues.apache.org/jira/browse/STREAMS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-486: --- Sprint: 0.5.0, 0.6.0 (was: 0.5.0) > Update release script on website > > > Key: STREAMS-486 > URL: https://issues.apache.org/jira/browse/STREAMS-486 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Release script as it is now on the Release website is inadequate and doesn't > accurately describe the release process. > A lot of changes to project structure and poms have taken place recently. > > Prior to and during the next release > > let’s make an effort to cover every single step, placing details (such as > > how to create accounts and > > generate credentials for testing) to are relevant to users as well as > > release manager outside the body > > of the release process document. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-484) Update website to reflect deprecation of streams-master
[ https://issues.apache.org/jira/browse/STREAMS-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-484: --- Sprint: 0.5.0, 0.6.0 (was: 0.5.0) > Update website to reflect deprecation of streams-master > --- > > Key: STREAMS-484 > URL: https://issues.apache.org/jira/browse/STREAMS-484 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Update website to reflect deprecation of streams-master -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-420) reboot: cleanup JIRA
[ https://issues.apache.org/jira/browse/STREAMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-420: --- Sprint: 0.5.0, 0.6.0 (was: 0.5.0) > 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] [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 ] Steve Blackmon updated STREAMS-412: --- Sprint: 0.6.0 > 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 > > > 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] [Created] (STREAMS-498) Prune your RAT plugin configurations' exclusions settings.
Steve Blackmon created STREAMS-498: -- Summary: Prune your RAT plugin configurations' exclusions settings. Key: STREAMS-498 URL: https://issues.apache.org/jira/browse/STREAMS-498 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon Priority: Minor Suggestion from IPMC during 0.5-incubating release: prune your RAT plugin configurations' exclusions settings. You have a few in there which are suspect -- some which are implicitly excluded (e.g. target) and some which seem to be intended directories you overlay but should not be included in a release (e.g. overlays/) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-493) streams-examples jenkins build fails
[ https://issues.apache.org/jira/browse/STREAMS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-493: --- Sprint: 0.6.0 > 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] [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 ] Steve Blackmon updated STREAMS-479: --- Fix Version/s: (was: 0.5) 0.6 > 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.6 > > 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-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 ] Steve Blackmon updated STREAMS-479: --- Sprint: 0.6.0 (was: 0.5.0) > 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.6 > > 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-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 ] Steve Blackmon updated STREAMS-497: --- Sprint: 0.6.0 > 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: Steve Blackmon > Fix For: 0.6 > > 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] [Updated] (STREAMS-496) Remove twitter4j dependency from streams-provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-496: --- Sprint: 0.6.0 Fix Version/s: 0.6 > Remove twitter4j dependency from streams-provider-twitter > - > > Key: STREAMS-496 > URL: https://issues.apache.org/jira/browse/STREAMS-496 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.6 > > Original Estimate: 4h > Remaining Estimate: 4h > > Per discussion on legal@ releases that include modules with the json license > are not permitted after April 30, 2017. > twitter4j has such a dependency and has shown little willingness to address > it. > Switch off twitter4j to HTTP API interaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (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 ] Steve Blackmon updated STREAMS-497: --- Fix Version/s: 0.6 > 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: Steve Blackmon > Fix For: 0.6 > > 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] [Created] (STREAMS-497) Add streams prefix to project and examples artifactIds
Steve Blackmon created STREAMS-497: -- Summary: 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: Steve Blackmon 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] [Created] (STREAMS-496) Remove twitter4j dependency from streams-provider-twitter
Steve Blackmon created STREAMS-496: -- Summary: Remove twitter4j dependency from streams-provider-twitter Key: STREAMS-496 URL: https://issues.apache.org/jira/browse/STREAMS-496 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon Per discussion on legal@ releases that include modules with the json license are not permitted after April 30, 2017. twitter4j has such a dependency and has shown little willingness to address it. Switch off twitter4j to HTTP API interaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-495) mvn -o clean can fail when streams-plugin-pojo snapshot is not installed
[ https://issues.apache.org/jira/browse/STREAMS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-495. Resolution: Fixed > mvn -o clean can fail when streams-plugin-pojo snapshot is not installed > > > Key: STREAMS-495 > URL: https://issues.apache.org/jira/browse/STREAMS-495 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > mvn -o clean can fail when streams-plugin-pojo snapshot is not installed. > it appears this is happening because many modules bind this plugin to goal > generate-sources but not to phase generate-sources > the binding should be done in the root.pom and not in project child modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-453) tag each jira against one/more components.
[ https://issues.apache.org/jira/browse/STREAMS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-453. Resolution: Fixed I've done this for most issues. > 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] [Created] (STREAMS-495) mvn -o clean can fail when streams-plugin-pojo snapshot is not installed
Steve Blackmon created STREAMS-495: -- Summary: mvn -o clean can fail when streams-plugin-pojo snapshot is not installed Key: STREAMS-495 URL: https://issues.apache.org/jira/browse/STREAMS-495 Project: Streams Issue Type: Bug Reporter: Steve Blackmon Assignee: Steve Blackmon mvn -o clean can fail when streams-plugin-pojo snapshot is not installed. it appears this is happening because many modules bind this plugin to goal generate-sources but not to phase generate-sources the binding should be done in the root.pom and not in project child modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-494) PropertyUtilTest is not running with surefire, and doesn't adequately test PropertyUtil
Steve Blackmon created STREAMS-494: -- Summary: PropertyUtilTest is not running with surefire, and doesn't adequately test PropertyUtil Key: STREAMS-494 URL: https://issues.apache.org/jira/browse/STREAMS-494 Project: Streams Issue Type: Bug Reporter: Steve Blackmon Assignee: Steve Blackmon PropertyUtilTest has a testng annotation but surefire only runs junit tests. Also the test needs to be more detailed to ensure PropertyUtil works as intended. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-420) reboot: cleanup JIRA
[ https://issues.apache.org/jira/browse/STREAMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-420 started by Steve Blackmon. -- > 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] [Updated] (STREAMS-462) Migrate website graphviz diagrams from git to confluence
[ https://issues.apache.org/jira/browse/STREAMS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-462: --- Sprint: (was: 0.5.0) > Migrate website graphviz diagrams from git to confluence > > > Key: STREAMS-462 > URL: https://issues.apache.org/jira/browse/STREAMS-462 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Original Estimate: 4h > Remaining Estimate: 4h > > a) migrate dot files out of our source control repos and into confluence > b) place them in a page hierarchy aligned with our source hierarchy > c) we'll manage their content from here on out in confluence > d) we embed them in the web page as we currently do, using links such as > https://cwiki.apache.org/confluence/download/attachments/66854246/integration.svg.svg?api=v2 > e) the SVG representation of each diagram gets created by the confluence > plugin and exposed to the web by confluence CMS. -- 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 ] Steve Blackmon updated STREAMS-412: --- Sprint: (was: 0.5.0) > 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 > > > 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] [Work started] (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 ] Work on STREAMS-479 started by Steve Blackmon. -- > 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-349) add maven dependency graph diagrams to site documentation
[ https://issues.apache.org/jira/browse/STREAMS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-349: --- Sprint: (was: 0.5.0) > add maven dependency graph diagrams to site documentation > - > > Key: STREAMS-349 > URL: https://issues.apache.org/jira/browse/STREAMS-349 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Minor > Fix For: 0.5 > > > add dependency graph diagrams to each module in streams-project and > streams-examples site documentation -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-484) Update website to reflect deprecation of streams-master
[ https://issues.apache.org/jira/browse/STREAMS-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-484 started by Steve Blackmon. -- > Update website to reflect deprecation of streams-master > --- > > Key: STREAMS-484 > URL: https://issues.apache.org/jira/browse/STREAMS-484 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Update website to reflect deprecation of streams-master -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (STREAMS-486) Update release script on website
[ https://issues.apache.org/jira/browse/STREAMS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-486 started by Steve Blackmon. -- > Update release script on website > > > Key: STREAMS-486 > URL: https://issues.apache.org/jira/browse/STREAMS-486 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > Fix For: 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > Release script as it is now on the Release website is inadequate and doesn't > accurately describe the release process. > A lot of changes to project structure and poms have taken place recently. > > Prior to and during the next release > > let’s make an effort to cover every single step, placing details (such as > > how to create accounts and > > generate credentials for testing) to are relevant to users as well as > > release manager outside the body > > of the release process document. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (STREAMS-493) streams-examples jenkins build fails
Steve Blackmon created STREAMS-493: -- Summary: 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 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-303) implement fromActivity throughout streams-provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-303: --- Component/s: Providers > implement fromActivity throughout streams-provider-twitter > -- > > Key: STREAMS-303 > URL: https://issues.apache.org/jira/browse/STREAMS-303 > Project: Streams > Issue Type: New Feature > Components: Providers >Reporter: Steve Blackmon > > The ActivityConverter interface includes methods to convert from Activity to > native representation, but most are currently unimplemented. > Implementation of these methods would allow for streams which terminate in > publication of activities to SNS. > Implement these methods for streams-provider-twitter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-130) Elasticsearch provider signals completion with data still enqueued
[ https://issues.apache.org/jira/browse/STREAMS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-130: --- Component/s: Persist > Elasticsearch provider signals completion with data still enqueued > -- > > Key: STREAMS-130 > URL: https://issues.apache.org/jira/browse/STREAMS-130 > Project: Streams > Issue Type: Bug > Components: Persist >Reporter: Matt Franklin > > Elasticsearch provider signals completion with data still enqueued -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-104) WebHDFSPersistWriter continues to try to write to closed streams
[ https://issues.apache.org/jira/browse/STREAMS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-104: --- Component/s: Persist > WebHDFSPersistWriter continues to try to write to closed streams > > > Key: STREAMS-104 > URL: https://issues.apache.org/jira/browse/STREAMS-104 > Project: Streams > Issue Type: Bug > Components: Persist >Reporter: Matt Franklin > > WebHDFSPersistWriter continues to try to write to closed streams -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-54) Complete, test, and document lucene processor
[ https://issues.apache.org/jira/browse/STREAMS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-54: -- Component/s: Processors > Complete, test, and document lucene processor > - > > Key: STREAMS-54 > URL: https://issues.apache.org/jira/browse/STREAMS-54 > Project: Streams > Issue Type: Story > Components: Processors >Reporter: Steve Blackmon > > Complete, test, and document lucene processor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-379) LogstashUDPPersister prone to error with large payloads
[ https://issues.apache.org/jira/browse/STREAMS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-379: --- Component/s: Miscellaneous > LogstashUDPPersister prone to error with large payloads > --- > > Key: STREAMS-379 > URL: https://issues.apache.org/jira/browse/STREAMS-379 > Project: Streams > Issue Type: Bug > Components: Miscellaneous >Reporter: Steve Blackmon > > This starts happening after a while with a stream that creates additional > streams. > ERROR o.a.s.m.p.i.LogstashUdpMessagePersister - Metrics Broadcast Failed: > Message too long > Look into breaking up messages that are too large for UDP -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-388) implement fromActivityObject throughout streams-provider-twitter
[ https://issues.apache.org/jira/browse/STREAMS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-388: --- Component/s: Providers > implement fromActivityObject throughout streams-provider-twitter > > > Key: STREAMS-388 > URL: https://issues.apache.org/jira/browse/STREAMS-388 > Project: Streams > Issue Type: New Feature > Components: Providers >Reporter: Steve Blackmon > > The ActivityObjectConverter interface includes methods to convert from > ActivityObject to native representation, but most are currently unimplemented. > Implementation of these methods would allow for streams which terminate in > publication of profile updates to SNS. > Implement these methods for streams-provider-twitter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-224) Graph DB Persist Module
[ https://issues.apache.org/jira/browse/STREAMS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-224. Resolution: Fixed Converted remaining sub-tasks to issues. > Graph DB Persist Module > --- > > Key: STREAMS-224 > URL: https://issues.apache.org/jira/browse/STREAMS-224 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon > > Create a module that will build a graph representation of a stream, storing > actors and objects as vertices and activities as edges. Should be database > agnostic, with minimal new dependencies. Support neo4j and rexster graph > databases initially, but use a pattern than can be extended to other graph > DBs with a rest api. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-110) Uncaught exception in twitter streaming provider
[ https://issues.apache.org/jira/browse/STREAMS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-110: --- Component/s: Providers > Uncaught exception in twitter streaming provider > > > Key: STREAMS-110 > URL: https://issues.apache.org/jira/browse/STREAMS-110 > Project: Streams > Issue Type: Bug > Components: Providers >Reporter: Steve Blackmon > > The streaming provider has a tendency to die after several hours. The > provider should handle this by reinitializing the stream. > 14:48:16.300 [hosebird-client-io-thread-0] DEBUG > o.a.h.i.conn.DefaultClientConnection - Connection > 0.0.0.0:60667<->199.59.148.139:443 shut down > 14:48:16 14:48:16.300 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.conn.DefaultClientConnection - Connection > 0.0.0.0:60667<->199.59.148.139:443 closed > 14:48:16 14:48:16.300 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection released: [id: > 0][route: {s}->https://userstream.twitter.com][total kept alive: 0; route > allocated: 0 of 2; total allocated: 0 of 20] > 14:48:16 14:48:16.300 [hosebird-client-io-thread-0] INFO > c.twitter.hbc.httpclient.ClientBase - > apache/streams/streams-contrib/streams-provider-twitter Disconnected during > processing - will reconnect > 14:48:16 14:48:16.300 [hosebird-client-io-thread-0] INFO > c.twitter.hbc.httpclient.ClientBase - > apache/streams/streams-contrib/streams-provider-twitter Done processing, > preparing to close connection > 14:48:16 14:48:16.301 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection manager is > shutting down > 14:48:16 14:48:16.301 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection manager shut down > 14:48:16 14:48:16.309 [hosebird-client-io-thread-0] WARN > c.twitter.hbc.httpclient.ClientBase - > apache/streams/streams-contrib/streams-provider-twitter Uncaught exception > 14:48:16 java.lang.NoSuchMethodError: > com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V > 14:48:16 at > com.twitter.hbc.httpclient.Connection.close(Connection.java:63) > ~[twitter-0.1-SNAPSHOT.jar:na] > 14:48:16 at > com.twitter.hbc.httpclient.ClientBase.run(ClientBase.java:149) > ~[twitter-0.1-SNAPSHOT.jar:na] > 14:48:16 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [na:1.7.0_51] > 14:48:16 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [na:1.7.0_51] > 14:48:16 at > java.lang.Thread.run(Thread.java:744) [na:1.7.0_51] > 14:48:16 14:48:16.309 [hosebird-client-io-thread-0] INFO > c.twitter.hbc.httpclient.ClientBase - > apache/streams/streams-contrib/streams-provider-twitter exit event - > java.lang.NoSuchMethodError: > com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V > 14:48:16 14:48:16.309 [hosebird-client-io-thread-0] INFO > c.twitter.hbc.httpclient.ClientBase - > apache/streams/streams-contrib/streams-provider-twitter Shutting down > httpclient connection manager > 14:48:16 14:48:16.309 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection manager is > shutting down > 14:48:16 14:48:16.309 [hosebird-client-io-thread-0] > DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection manager shut down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-117) Support arbitrary search criteria in MongoPersistReader
[ https://issues.apache.org/jira/browse/STREAMS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-117: --- Issue Type: New Feature (was: Sub-task) Parent: (was: STREAMS-111) > Support arbitrary search criteria in MongoPersistReader > --- > > Key: STREAMS-117 > URL: https://issues.apache.org/jira/browse/STREAMS-117 > Project: Streams > Issue Type: New Feature > Components: Providers >Reporter: Steve Blackmon > > Support arbitrary search criteria in MongoPersistReader -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (STREAMS-111) PersistReaders with json-based query engines should accept a full query definition from the job config
[ https://issues.apache.org/jira/browse/STREAMS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-111. Resolution: Fixed Assignee: Steve Blackmon Converted remaining sub-tasks to issues. > PersistReaders with json-based query engines should accept a full query > definition from the job config > -- > > Key: STREAMS-111 > URL: https://issues.apache.org/jira/browse/STREAMS-111 > Project: Streams > Issue Type: New Feature >Reporter: Steve Blackmon >Assignee: Steve Blackmon > > Specifically thinking of ES and Mongo but may apply to others > Rather than be limited to > "elasticsearch": { > "source": { > "indexes": [ > ], > "types": [ > ] > } > } > it would be incredibly useful to also supply > "_search": { > ... full json doc of search request > } > and have that used to generate the stream cursor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-114) ThreadAbortExceptions are mishandled
[ https://issues.apache.org/jira/browse/STREAMS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-114: --- Component/s: Runtimes > ThreadAbortExceptions are mishandled > > > Key: STREAMS-114 > URL: https://issues.apache.org/jira/browse/STREAMS-114 > Project: Streams > Issue Type: Bug > Components: Runtimes >Reporter: Matt Franklin > > Some classes catch ThreadAbortExceptions and just move on, causing streams to > hold threads open. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-117) Support arbitrary search criteria in MongoPersistReader
[ https://issues.apache.org/jira/browse/STREAMS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-117: --- Component/s: Providers > Support arbitrary search criteria in MongoPersistReader > --- > > Key: STREAMS-117 > URL: https://issues.apache.org/jira/browse/STREAMS-117 > Project: Streams > Issue Type: Sub-task > Components: Providers >Reporter: Steve Blackmon > > Support arbitrary search criteria in MongoPersistReader -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-125) Build osgi bundle jars for contrib modules
[ https://issues.apache.org/jira/browse/STREAMS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-125: --- Component/s: Miscellaneous > Build osgi bundle jars for contrib modules > -- > > Key: STREAMS-125 > URL: https://issues.apache.org/jira/browse/STREAMS-125 > Project: Streams > Issue Type: Improvement > Components: Miscellaneous >Reporter: Steve Blackmon > > Developers should be able to version providers, processors, and persisters > independently inside an osgi container, and build pipelines with eip routes > between those modules. > Update project poms to make this possible - also create an example with > documentation showing how to describe and run a stream without building a > master jar-with-dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (STREAMS-183) streams-local closes persist-writers before datums in-flight are written
[ https://issues.apache.org/jira/browse/STREAMS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864712#comment-15864712 ] Steve Blackmon edited comment on STREAMS-183 at 2/13/17 11:53 PM: -- The basic strategy should be: runtime calls close() on component when stream is ready to shutdown component isRunning() should returns false once it has finished its work runtime waits a maximum of 'taskTimeoutMs' before shutting stream down regardless of component status was (Author: steveblackmon): The basic strategy should be: runtime calls close() on component component isRunning() returns false once it has flushed runtime waits a maximum of 'taskTimeoutMs' before shutting stream down regardless of component status > streams-local closes persist-writers before datums in-flight are written > > > Key: STREAMS-183 > URL: https://issues.apache.org/jira/browse/STREAMS-183 > Project: Streams > Issue Type: Bug > Components: Runtimes >Reporter: Steve Blackmon > > I have observed this behavior when writing datums from a readCurrent provider > through to ElasticsearchPersistWriter and ElasticsearchPersistDeleter. > The log looks like: > 421777 [pool-2-thread-7] INFO o.a.s.e.ElasticsearchPersistReader - > PersistReader done > 469271 [main] INFO o.a.s.l.builders.LocalStreamBuilder - Attempting to > shutdown tasks > 476319 [pool-2-thread-3] ERROR o.a.s.e.ElasticsearchPersistWriter - There was > an error sending the batch: No node available > 485275 [main] WARN o.a.s.l.builders.LocalStreamBuilder - Task > org.apache.streams.local.tasks.StreamsPersistWriterTask@6add646d failed to > terminate in allotted timeframe > 495276 [pool-2-thread-3] WARN o.a.s.e.ElasticsearchPersistWriter - Catchup > was interrupted. Data may be lost > followed by additional No Node Available exceptions. > When the same stream is executed as a perpetual stream, this problem does not > occur. > Possible solutions: > a) localstreambuilder waits a while between detecting providers have > completed and stopping downstream components > b) localstreambuilder does not stop downstream components until all datums > have been processed/written > c) writers refuse to close until all datums have been written -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-183) streams-local closes persist-writers before datums in-flight are written
[ https://issues.apache.org/jira/browse/STREAMS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-183: --- Component/s: Runtimes > streams-local closes persist-writers before datums in-flight are written > > > Key: STREAMS-183 > URL: https://issues.apache.org/jira/browse/STREAMS-183 > Project: Streams > Issue Type: Bug > Components: Runtimes >Reporter: Steve Blackmon > > I have observed this behavior when writing datums from a readCurrent provider > through to ElasticsearchPersistWriter and ElasticsearchPersistDeleter. > The log looks like: > 421777 [pool-2-thread-7] INFO o.a.s.e.ElasticsearchPersistReader - > PersistReader done > 469271 [main] INFO o.a.s.l.builders.LocalStreamBuilder - Attempting to > shutdown tasks > 476319 [pool-2-thread-3] ERROR o.a.s.e.ElasticsearchPersistWriter - There was > an error sending the batch: No node available > 485275 [main] WARN o.a.s.l.builders.LocalStreamBuilder - Task > org.apache.streams.local.tasks.StreamsPersistWriterTask@6add646d failed to > terminate in allotted timeframe > 495276 [pool-2-thread-3] WARN o.a.s.e.ElasticsearchPersistWriter - Catchup > was interrupted. Data may be lost > followed by additional No Node Available exceptions. > When the same stream is executed as a perpetual stream, this problem does not > occur. > Possible solutions: > a) localstreambuilder waits a while between detecting providers have > completed and stopping downstream components > b) localstreambuilder does not stop downstream components until all datums > have been processed/written > c) writers refuse to close until all datums have been written -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (STREAMS-183) streams-local closes persist-writers before datums in-flight are written
[ https://issues.apache.org/jira/browse/STREAMS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864712#comment-15864712 ] Steve Blackmon commented on STREAMS-183: The basic strategy should be: runtime calls close() on component component isRunning() returns false once it has flushed runtime waits a maximum of 'taskTimeoutMs' before shutting stream down regardless of component status > streams-local closes persist-writers before datums in-flight are written > > > Key: STREAMS-183 > URL: https://issues.apache.org/jira/browse/STREAMS-183 > Project: Streams > Issue Type: Bug > Components: Runtimes >Reporter: Steve Blackmon > > I have observed this behavior when writing datums from a readCurrent provider > through to ElasticsearchPersistWriter and ElasticsearchPersistDeleter. > The log looks like: > 421777 [pool-2-thread-7] INFO o.a.s.e.ElasticsearchPersistReader - > PersistReader done > 469271 [main] INFO o.a.s.l.builders.LocalStreamBuilder - Attempting to > shutdown tasks > 476319 [pool-2-thread-3] ERROR o.a.s.e.ElasticsearchPersistWriter - There was > an error sending the batch: No node available > 485275 [main] WARN o.a.s.l.builders.LocalStreamBuilder - Task > org.apache.streams.local.tasks.StreamsPersistWriterTask@6add646d failed to > terminate in allotted timeframe > 495276 [pool-2-thread-3] WARN o.a.s.e.ElasticsearchPersistWriter - Catchup > was interrupted. Data may be lost > followed by additional No Node Available exceptions. > When the same stream is executed as a perpetual stream, this problem does not > occur. > Possible solutions: > a) localstreambuilder waits a while between detecting providers have > completed and stopping downstream components > b) localstreambuilder does not stop downstream components until all datums > have been processed/written > c) writers refuse to close until all datums have been written -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STREAMS-204) Update Google+ serializer to handle post comments
[ https://issues.apache.org/jira/browse/STREAMS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon updated STREAMS-204: --- Component/s: Providers > Update Google+ serializer to handle post comments > - > > Key: STREAMS-204 > URL: https://issues.apache.org/jira/browse/STREAMS-204 > Project: Streams > Issue Type: Task > Components: Providers >Reporter: Robert Douglas > > As a Stream developer, I should have access to any comments that are made on > a post that I am tracking. This necessitates modifications to the Google+ > serializer to put all comments in the Activity Object's attachment section. A > top level "Comment count" should be kept in the Activity's extensions map. > Acceptance Criteria: > - All comments made about a post are persisted in activity.object.attachment > - A total comment count is stored in activity.extensions.comment_count -- This message was sent by Atlassian JIRA (v6.3.15#6346)