Not a fan of a generic 'extensions' collection. I have, though, found
use in defining entities collection for items referenced in the
content section. The style mimics the approach from App.net messaging
schema. From your examples, this would only address hashtags,
mentions, and urls. The gender of
Steve Blackmon created STREAMS-70:
-
Summary: Generic Json Processors
Key: STREAMS-70
URL: https://issues.apache.org/jira/browse/STREAMS-70
Project: Streams
Issue Type: New Feature
Steve Blackmon created STREAMS-69:
-
Summary: Improve tweet jsonschema - add Hashtag object
Key: STREAMS-69
URL: https://issues.apache.org/jira/browse/STREAMS-69
Project: Streams
Issue Type: I
GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/5
STREAMS-62 | Serializability in processors
Ensured that all processors were serializable (already merged into
apache/incubator-streams)
You can merge this pull request into a Git reposi
Github user robdouglas closed the pull request at:
https://github.com/apache/incubator-streams/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
[
https://issues.apache.org/jira/browse/STREAMS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984642#comment-13984642
]
ASF GitHub Bot commented on STREAMS-62:
---
GitHub user robdouglas opened a pull reques
[
https://issues.apache.org/jira/browse/STREAMS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984643#comment-13984643
]
ASF GitHub Bot commented on STREAMS-62:
---
Github user robdouglas closed the pull requ
Hi Vijay,
We have some examples streams in this github repo:
https://github.com/w2ogroup/streams-examples
twitter-history-elasticsearch , twitter-userstream-local , then
twitter-gardenhose-dualwriter are a good sequence for ramping up.
Please note that the kafka persister is not finished (STREA
I¹m working on mocking up the new schema at the moment, but Œextensions¹
would become a new top-level element in the json structure. Each of the
proposed extensions would then be a sub-element in that Œextensions¹
element.
On 4/29/14, 11:12 AM, "James M Snell" wrote:
>In this proposal, how would
In this proposal, how would these manifest in the json structure?
On Tue, Apr 29, 2014 at 8:57 AM, Robert Douglas [W2O Digital]
wrote:
> Hi all,
>
> Given that there are certain attributes that are similar across multiple
> social media feeds (ie. A ‘like’ on Facebook, ‘favorite’ on twitter, and
Hi all,
Given that there are certain attributes that are similar across multiple social
media feeds (ie. A ‘like’ on Facebook, ‘favorite’ on twitter, and ‘+1’ on
Google+ are all equivalent) I think it makes sense to break these out into
generalized extensions. I’d like to propose the following
Matt Franklin created STREAMS-68:
Summary: ActivitySerializer should be ActivityConverter
Key: STREAMS-68
URL: https://issues.apache.org/jira/browse/STREAMS-68
Project: Streams
Issue Type: Im
[
https://issues.apache.org/jira/browse/STREAMS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Franklin resolved STREAMS-67.
--
Resolution: Fixed
Assignee: Matt Franklin
> Mongo PersistWriter counts do not match provi
[
https://issues.apache.org/jira/browse/STREAMS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Franklin resolved STREAMS-66.
--
Resolution: Fixed
> Streams Local times out for low volume providers
>
14 matches
Mail list logo
