[jira] [Closed] (STREAMS-478) streams persist reader/writer for Apache Cassandra
[ https://issues.apache.org/jira/browse/STREAMS-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee closed STREAMS-478. --- Resolution: Fixed Fix Version/s: 0.5 Merged already in PR #345 > streams persist reader/writer for Apache Cassandra > -- > > Key: STREAMS-478 > URL: https://issues.apache.org/jira/browse/STREAMS-478 > Project: Streams > Issue Type: New Feature >Reporter: Subhobrata Dey > Fix For: 0.5 > > > This issue is created to propose the streams persist reader/writer to > get/post documents from/to apache cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (STREAMS-478) streams persist reader/writer for Apache Cassandra
[ https://issues.apache.org/jira/browse/STREAMS-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781845#comment-15781845 ] Joey Frazee edited comment on STREAMS-478 at 12/28/16 2:34 AM: --- [~sbcd90] Thanks for the contrib! I'm going to start reviewing this but thanks in advance for updating docs and including unit tests and all that. In the meantime, it doesn't look like you have an Apache ICLA [[https://www.apache.org/licenses/icla.txt]] on file, so I was wondering if you'd be able to fill that out and email it in? was (Author: jfrazee): [~sbcd90] Thanks for the contrib! I'm going to start reviewing this but thanks in advance for updating docs and including unit tests and all that. In the meantime, it doesn't look like you have an Apache ICLA [https://www.apache.org/licenses/icla.txt] on file, so I was wondering if you'd be able to fill that out and email it in? > streams persist reader/writer for Apache Cassandra > -- > > Key: STREAMS-478 > URL: https://issues.apache.org/jira/browse/STREAMS-478 > Project: Streams > Issue Type: New Feature >Reporter: Subhobrata Dey > > This issue is created to propose the streams persist reader/writer to > get/post documents from/to apache cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-478) streams persist reader/writer for Apache Cassandra
[ https://issues.apache.org/jira/browse/STREAMS-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15781845#comment-15781845 ] Joey Frazee commented on STREAMS-478: - [~sbcd90] Thanks for the contrib! I'm going to start reviewing this but thanks in advance for updating docs and including unit tests and all that. In the meantime, it doesn't look like you have an Apache ICLA [https://www.apache.org/licenses/icla.txt] on file, so I was wondering if you'd be able to fill that out and email it in? > streams persist reader/writer for Apache Cassandra > -- > > Key: STREAMS-478 > URL: https://issues.apache.org/jira/browse/STREAMS-478 > Project: Streams > Issue Type: New Feature >Reporter: Subhobrata Dey > > This issue is created to propose the streams persist reader/writer to > get/post documents from/to apache cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STREAMS-450) Remove opml.xsd and contents.xsd
[ https://issues.apache.org/jira/browse/STREAMS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee resolved STREAMS-450. - Resolution: Fixed > Remove opml.xsd and contents.xsd > > > Key: STREAMS-450 > URL: https://issues.apache.org/jira/browse/STREAMS-450 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.4 >Reporter: Joey Frazee >Assignee: Joey Frazee >Priority: Critical > > As pointed out here [1] > streams-contrib/streams-provider-rss/src/main/xmlschema/opml.xsd and > streams-contrib/streams-provider-rss/src/main/xmlschema/contents.xsd are GPL > so they need to be removed or replaced with alternatives. > 1. > http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-451) Remove CHANGELOG.md
Joey Frazee created STREAMS-451: --- Summary: Remove CHANGELOG.md Key: STREAMS-451 URL: https://issues.apache.org/jira/browse/STREAMS-451 Project: Streams Issue Type: Task Reporter: Joey Frazee 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] [Updated] (STREAMS-450) Remove opml.xsd and contents.xsd
[ https://issues.apache.org/jira/browse/STREAMS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee updated STREAMS-450: Description: As pointed out here [1] streams-contrib/streams-provider-rss/src/main/xmlschema/opml.xsd and streams-contrib/streams-provider-rss/src/main/xmlschema/contents.xsd are GPL so they need to be removed or replaced with alternatives. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e was: As pointed out here [1] opml.xsd and contents.xsd are GPL so they need to be removed or replaced with alternatives. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e > Remove opml.xsd and contents.xsd > > > Key: STREAMS-450 > URL: https://issues.apache.org/jira/browse/STREAMS-450 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.4 >Reporter: Joey Frazee >Assignee: Joey Frazee >Priority: Critical > > As pointed out here [1] > streams-contrib/streams-provider-rss/src/main/xmlschema/opml.xsd and > streams-contrib/streams-provider-rss/src/main/xmlschema/contents.xsd are GPL > so they need to be removed or replaced with alternatives. > 1. > http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STREAMS-450) Remove opml.xsd and contents.xsd
[ https://issues.apache.org/jira/browse/STREAMS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee updated STREAMS-450: Description: As pointed out here [1] opml.xsd and contents.xsd are GPL so they need to be removed or replaced with alternatives. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e was: As pointed out here [1] opal.xsd and contents.xsd are GPL so they need to be removed or replaced with alternatives. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e > Remove opml.xsd and contents.xsd > > > Key: STREAMS-450 > URL: https://issues.apache.org/jira/browse/STREAMS-450 > Project: Streams > Issue Type: Improvement >Affects Versions: 0.4 >Reporter: Joey Frazee >Assignee: Joey Frazee >Priority: Critical > > As pointed out here [1] opml.xsd and contents.xsd are GPL so they need to be > removed or replaced with alternatives. > 1. > http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-450) Remove opml.xsd and contents.xsd
Joey Frazee created STREAMS-450: --- Summary: Remove opml.xsd and contents.xsd Key: STREAMS-450 URL: https://issues.apache.org/jira/browse/STREAMS-450 Project: Streams Issue Type: Improvement Affects Versions: 0.4 Reporter: Joey Frazee Assignee: Joey Frazee Priority: Critical As pointed out here [1] opal.xsd and contents.xsd are GPL so they need to be removed or replaced with alternatives. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3c03577f39-20c5-47d0-aa46-5d7b89670...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-449) Enforce Java code conventions with auto-formatter
Joey Frazee created STREAMS-449: --- Summary: 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 Priority: Minor 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] [Work started] (STREAMS-432) Update to Java 8
[ https://issues.apache.org/jira/browse/STREAMS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on STREAMS-432 started by Joey Frazee. --- > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STREAMS-432) Update to Java 8
Joey Frazee created STREAMS-432: --- Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15595723#comment-15595723 ] Joey Frazee commented on STREAMS-132: - Should be closed because org.apache.streams.util.RegexUtils actually isn't used. and it's fixed in the regex package. See 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 > 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] [Commented] (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:comment-tabpanel=15595408#comment-15595408 ] Joey Frazee commented on STREAMS-132: - This was fixed for org.apache.streams.regex.RegexUtils in c7e7ad6 but the same bug is in org.apache.streams.regex.RegexUtils > 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 > 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] [Assigned] (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 ] Joey Frazee reassigned STREAMS-132: --- Assignee: Joey Frazee > 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 > 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] [Created] (STREAMS-405) Link to src/site/markdown/index.md in README.md is broken
Joey Frazee created STREAMS-405: --- Summary: Link to src/site/markdown/index.md in README.md is broken Key: STREAMS-405 URL: https://issues.apache.org/jira/browse/STREAMS-405 Project: Streams Issue Type: Bug Reporter: Joey Frazee Assignee: Joey Frazee Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-127) JsonSchema Replication in Datasift provider
[ https://issues.apache.org/jira/browse/STREAMS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309183#comment-15309183 ] Joey Frazee commented on STREAMS-127: - Does Datasift support need to be reviewed/deprecated? > JsonSchema Replication in Datasift provider > --- > > Key: STREAMS-127 > URL: https://issues.apache.org/jira/browse/STREAMS-127 > Project: Streams > Issue Type: Improvement >Reporter: Ryan Ebanks > > JsonSchema is replicated in multiple places for the datasift provider causing > multiple identical objects to be create by the json to pojo plugin. This > cause code duplication when writing serializers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STREAMS-74) Use maven plugin to require headers with correct license and required javadoc plugin lines
[ https://issues.apache.org/jira/browse/STREAMS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee reassigned STREAMS-74: -- Assignee: Joey Frazee > Use maven plugin to require headers with correct license and required javadoc > plugin lines > -- > > Key: STREAMS-74 > URL: https://issues.apache.org/jira/browse/STREAMS-74 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Joey Frazee >Priority: Minor > > Use maven plugin to require headers with correct license and required javadoc > plugin lines -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-314) Prevent catastrophic backtracking in RegexUtils Extraction
[ https://issues.apache.org/jira/browse/STREAMS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309176#comment-15309176 ] Joey Frazee commented on STREAMS-314: - Already closed, but not merged. Not sure what to do here. I can't find the revision. > Prevent catastrophic backtracking in RegexUtils Extraction > -- > > Key: STREAMS-314 > URL: https://issues.apache.org/jira/browse/STREAMS-314 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas > > Prevent catastrophic backtracking in RegexUtils Extraction -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-208) Integration Testing capability and reference Integration Test
[ https://issues.apache.org/jira/browse/STREAMS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309169#comment-15309169 ] Joey Frazee commented on STREAMS-208: - [~steveblackmon] This is yours. already merged. > Integration Testing capability and reference Integration Test > - > > Key: STREAMS-208 > URL: https://issues.apache.org/jira/browse/STREAMS-208 > Project: Streams > Issue Type: Test >Reporter: Steve Blackmon > > Alter project poms such that mvn verify runs all tests ending with IT. Add > an IntegrationTest demonstrating how to compose a stream such that a specific > set of datums can be passed into a mock provider and confirmed to have > arrived at a mock persist writer at the end of the stream. Keep number of > mocks required to achieve this to a minimum. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-200) StreamsProcessorTask ignores any processing
[ https://issues.apache.org/jira/browse/STREAMS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309168#comment-15309168 ] Joey Frazee commented on STREAMS-200: - Here's another already merged one. > StreamsProcessorTask ignores any processing > --- > > Key: STREAMS-200 > URL: https://issues.apache.org/jira/browse/STREAMS-200 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas > > As a developer, I should have a guarantee that any processing that occurs on > a datum is passed to the outgoing queue. As it currently stands, we disregard > the processed datum and simply pass through the document that the processor > task was originally handed. > Acceptance criteria: > - We place the processed document in the processor task's outgoing queue -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-263) FacebookTypeConverter should be able to handle Facebook Pages
[ https://issues.apache.org/jira/browse/STREAMS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309159#comment-15309159 ] Joey Frazee commented on STREAMS-263: - This is another one that didn't get closed out. > FacebookTypeConverter should be able to handle Facebook Pages > - > > Key: STREAMS-263 > URL: https://issues.apache.org/jira/browse/STREAMS-263 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas > > FacebookTypeConverter should be able to handle Facebook Pages. > It currently only supports Pages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-261) Create Facebook Bio Collector/Provider
[ https://issues.apache.org/jira/browse/STREAMS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309146#comment-15309146 ] Joey Frazee commented on STREAMS-261: - Needs closed. > Create Facebook Bio Collector/Provider > -- > > Key: STREAMS-261 > URL: https://issues.apache.org/jira/browse/STREAMS-261 > Project: Streams > Issue Type: Story >Reporter: Robert Douglas > > Following the pattern of other social media channel providers, we need to > have a way to collect biohistory or user profile information via Streams. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-22) Add Storm for pushing activities to subscriber queues
[ https://issues.apache.org/jira/browse/STREAMS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309142#comment-15309142 ] Joey Frazee commented on STREAMS-22: http://storm.apache.org Also, I think it might make sense at this point to back off to something higher level for runtimes; a Beam or something like that. > Add Storm for pushing activities to subscriber queues > - > > Key: STREAMS-22 > URL: https://issues.apache.org/jira/browse/STREAMS-22 > Project: Streams > Issue Type: New Feature >Reporter: Danny Sullivan > > http://storm-project.net/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-51) Complete, test, and document tika processor
[ https://issues.apache.org/jira/browse/STREAMS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309136#comment-15309136 ] Joey Frazee commented on STREAMS-51: [~steveblackmon] What do you mean by this? Is this for attachments/media or something else? Could be a cool idea or could be peripheral to the goal. Not sure. > Complete, test, and document tika processor > --- > > Key: STREAMS-51 > URL: https://issues.apache.org/jira/browse/STREAMS-51 > Project: Streams > Issue Type: Story >Reporter: Steve Blackmon > > Complete, test, and document tika processor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-225) Streams need to remove any of their JMX beans on shutdown/cleanup
[ https://issues.apache.org/jira/browse/STREAMS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309131#comment-15309131 ] Joey Frazee commented on STREAMS-225: - This is another one that's already merged. > Streams need to remove any of their JMX beans on shutdown/cleanup > - > > Key: STREAMS-225 > URL: https://issues.apache.org/jira/browse/STREAMS-225 > Project: Streams > Issue Type: Bug >Reporter: Robert Douglas > > As a Streams developer, I should be able to run multiple Streams in a serial > fashion without issue. Currently, JMX beans (which are used for monitoring > the Stream's activity) are not cleared when a Stream is shutdown. If a new > Stream is started afterwards (without a JVM restart) then there is a > collision in the naming of the JMX beans which causes an exception which > shuts down the subsequent Stream. Need to build in functionality to clear all > JMX beans on shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-280) Add ability to get a final document count from the Sysomos Provider
[ https://issues.apache.org/jira/browse/STREAMS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309125#comment-15309125 ] Joey Frazee commented on STREAMS-280: - This is merged already: https://github.com/apache/incubator-streams/pull/181 > Add ability to get a final document count from the Sysomos Provider > --- > > Key: STREAMS-280 > URL: https://issues.apache.org/jira/browse/STREAMS-280 > Project: Streams > Issue Type: Task >Reporter: Robert Douglas > > Add ability to get a final document count from the Sysomos Provider -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-297) Create RssLinkProvider
[ https://issues.apache.org/jira/browse/STREAMS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309124#comment-15309124 ] Joey Frazee commented on STREAMS-297: - Wouldn't this just be a transformation on full RSS activities? Is there a use case driving the priority on this? > Create RssLinkProvider > -- > > Key: STREAMS-297 > URL: https://issues.apache.org/jira/browse/STREAMS-297 > Project: Streams > Issue Type: Story >Reporter: Robert Douglas > > As a Streams Developer, I should have access to an RSS Provider which only > outputs the links of entries of a given RSS feed, instead of fully converted > activities. It's conceivable that a user would have downstream processors and > persisters that would only operate on the URLs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-344) Support batch writes in GraphHttpPersistWriter
[ https://issues.apache.org/jira/browse/STREAMS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309103#comment-15309103 ] Joey Frazee commented on STREAMS-344: - FWIW, there's a new neo4j protocol w/ an Apache licensed lib. Probably makes sense to move it over to this. https://github.com/neo4j/neo4j-java-driver > Support batch writes in GraphHttpPersistWriter > -- > > Key: STREAMS-344 > URL: https://issues.apache.org/jira/browse/STREAMS-344 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon > > Support batch writes in GraphHttpPersistWriter. > Using a separate HTTP Post for every datum is inefficient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STREAMS-344) Support batch writes in GraphHttpPersistWriter
[ https://issues.apache.org/jira/browse/STREAMS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joey Frazee reassigned STREAMS-344: --- Assignee: Joey Frazee > Support batch writes in GraphHttpPersistWriter > -- > > Key: STREAMS-344 > URL: https://issues.apache.org/jira/browse/STREAMS-344 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Assignee: Joey Frazee > > Support batch writes in GraphHttpPersistWriter. > Using a separate HTTP Post for every datum is inefficient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-74) Use maven plugin to require headers with correct license and required javadoc plugin lines
[ https://issues.apache.org/jira/browse/STREAMS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309097#comment-15309097 ] Joey Frazee commented on STREAMS-74: Need to move apache-rat-plugin outside of apache-release in ./incubator-streams-master-pom.xml so it runs as part of CI. Also let's look into relevant checkstyle checks. > Use maven plugin to require headers with correct license and required javadoc > plugin lines > -- > > Key: STREAMS-74 > URL: https://issues.apache.org/jira/browse/STREAMS-74 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Priority: Minor > > Use maven plugin to require headers with correct license and required javadoc > plugin lines -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-336) consolidate common pom sections to streams-master
[ https://issues.apache.org/jira/browse/STREAMS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309082#comment-15309082 ] Joey Frazee commented on STREAMS-336: - [~steveblackmon] This merged last year. I think the issue just didn't get closed. > consolidate common pom sections to streams-master > - > > Key: STREAMS-336 > URL: https://issues.apache.org/jira/browse/STREAMS-336 > Project: Streams > Issue Type: Improvement >Reporter: Steve Blackmon >Priority: Minor > > consolidate common pom sections from streams-project and streams-examples to > streams-master and make streams-master parent of both -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-351) add A2 license to site.xml files
[ https://issues.apache.org/jira/browse/STREAMS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309072#comment-15309072 ] Joey Frazee commented on STREAMS-351: - Are there any site.xml files besides ./src/site/site.xml? That one has the license: https://github.com/apache/incubator-streams/blob/master/src/site/site.xml > add A2 license to site.xml files > > > Key: STREAMS-351 > URL: https://issues.apache.org/jira/browse/STREAMS-351 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-44) Complete, test, and document sysomos provider
[ https://issues.apache.org/jira/browse/STREAMS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309064#comment-15309064 ] Joey Frazee commented on STREAMS-44: This is done: * https://github.com/apache/incubator-streams/blob/master/streams-contrib/streams-provider-sysomos/src/main/java/org/apache/streams/sysomos/provider/SysomosProvider.java * http://streams.incubator.apache.org/site/0.3-incubating-SNAPSHOT/streams-project/streams-contrib/streams-provider-sysomos/index.html > Complete, test, and document sysomos provider > - > > Key: STREAMS-44 > URL: https://issues.apache.org/jira/browse/STREAMS-44 > Project: Streams > Issue Type: Story >Reporter: Steve Blackmon >Assignee: Matt Franklin >Priority: Minor > > Complete, test, and document sysomos provider -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-43) Complete, test, and document g+ provider
[ https://issues.apache.org/jira/browse/STREAMS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309059#comment-15309059 ] Joey Frazee commented on STREAMS-43: These are implemented and given the uncertain future of g+, not sure whether more work needs to be done right now. Thoughts? > Complete, test, and document g+ provider > > > Key: STREAMS-43 > URL: https://issues.apache.org/jira/browse/STREAMS-43 > Project: Streams > Issue Type: Story >Reporter: Steve Blackmon >Priority: Minor > > Complete, test, and document g+ provider -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-46) Complete, test, and document facebook API provider
[ https://issues.apache.org/jira/browse/STREAMS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309048#comment-15309048 ] Joey Frazee commented on STREAMS-46: The core FB API is implemented and documented on the site and in javadoc. Can probably go ahead and close this. > Complete, test, and document facebook API provider > -- > > Key: STREAMS-46 > URL: https://issues.apache.org/jira/browse/STREAMS-46 > Project: Streams > Issue Type: Story >Reporter: Steve Blackmon >Priority: Minor > > Complete, test, and document facebook API provider -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-202) Create Google Plus Deserializer and TypeConverter
[ https://issues.apache.org/jira/browse/STREAMS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309034#comment-15309034 ] Joey Frazee commented on STREAMS-202: - Hey, it looks like this is already implemented in https://github.com/apache/incubator-streams/blob/c7490d3b621429df235b6280f7b86837623ab80c/streams-contrib/streams-provider-google/google-gplus/src/main/java/com/google/gplus/provider/GPlusUserDataCollector.java Can this be closed out? > Create Google Plus Deserializer and TypeConverter > - > > Key: STREAMS-202 > URL: https://issues.apache.org/jira/browse/STREAMS-202 > Project: Streams > Issue Type: Task >Reporter: Robert Douglas >Priority: Minor > > As a Streams developer, I should be able to take in GooglePlus Person model > objects and convert them to Activities while preserving all useful pieces of > information. > Acceptance Criteria: > - Can deserialize a JSON representation of a Person model into an actual > Person POJO > - Can process a Person POJO into an Activity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STREAMS-95) TwitterProfileProcessor needs to send a user ID in each StreamsDatum
[ https://issues.apache.org/jira/browse/STREAMS-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304801#comment-15304801 ] Joey Frazee commented on STREAMS-95: Is this still valid? createStreamsDatum() looks like it's using the id from the user object: https://github.com/apache/incubator-streams/blob/c7490d3b621429df235b6280f7b86837623ab80c/streams-contrib/streams-provider-twitter/src/main/java/org/apache/streams/twitter/processor/TwitterProfileProcessor.java#L77 > TwitterProfileProcessor needs to send a user ID in each StreamsDatum > > > Key: STREAMS-95 > URL: https://issues.apache.org/jira/browse/STREAMS-95 > Project: Streams > Issue Type: Task >Reporter: Robert Douglas > Original Estimate: 10m > Remaining Estimate: 10m > > When the TwitterProfileProcessor encounters a Retweet or User object, it > creates a new StreamsDatum that consists only of that user. The created > StreamsDatum needs to also have that user's unique identifier (passed in via > the constructor) so that we don't end up with duplicates down the stream -- This message was sent by Atlassian JIRA (v6.3.4#6332)
