Hey Yan,
Awesome! Just realized--could you also open a ticket to migrate
hello-samza/master to 0.9.0, and hello-samza/latest to 0.10.0?
Cheers,
Chris
On Wed, Apr 1, 2015 at 1:42 PM, Yan Fang wrote:
> Hi guys,
>
> Have updated website for 0.9 release. Feel free to check it. Only one thing
> rem
Hi Shekar,
I think the main question regarding your use case is the following: do you need
read-your-writes consistency?
If the answer is yes, then I'm afraid Samza is the wrong system for you. All
processing in Samza is bound to be asynchronous, so even if you tune your
systems to get a super
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32147/
---
(Updated April 1, 2015, 9:02 p.m.)
Review request for samza.
Changes
---
Hi guys,
Have updated website for 0.9 release. Feel free to check it. Only one thing
remaining - waiting for the blog account.
Thanks,
Fang, Yan
yanfang...@gmail.com
On Tue, Mar 31, 2015 at 8:44 PM, Roger Hoover
wrote:
> Nice. Thanks Yan!
>
> On Tue, Mar 31, 2015 at 3:24 PM, Yan Fang wrote:
Felix,
Since the webservices call is not maintained in a single session, how do we
tie up the incoming request to the enriched kv pair?
For example, lets take a use case
a given user (partitioned by user id) needs to be presented with all the
different regions he/she has been in to in a given tim
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32147/
---
(Updated April 1, 2015, 7:44 p.m.)
Review request for samza.
Repository: samz
Hi Vladimir,
It seems like you have decided on an architecture which is fairly similar to
the one I suggested (:
Out of curiosity, I have the following questions regarding your system:
* Are you saying the Samza tasks co-located with your k/v store nodes are
also doing processing, and not
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32147/
---
(Updated April 1, 2015, 5:37 p.m.)
Review request for samza.
Repository: samz
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32147/#review77607
---
samza-core/src/main/java/org/apache/samza/coordinator/stream/Coordi
Hi Roger,
You bring up good points, and I think the short answer is that there are
trade-offs to everything, of course (:
What I described could definitely be implemented as a Samza job, and I think
that would make a lot of sense if the data serving system was also deployed via
YARN. This way,
Hey Shekar,
To contribute to that page (or any docs), do the following:
1. Open a JIRA defining the issue (that you intend to fix) with the docs.
2. Check out samza's code base.
3. Change the docs (located in the 'docs' folder). They are markdown
formatted docs.
4. Run a `git diff` from the root
Chris,
I think I am comfortable now to add couple of steps to the multi node setup.
II am guessing I need some privileges to contribute to
http://samza.apache.org/learn/tutorials/0.7.0/run-in-multi-node-yarn.html
(need a jira ticket and privilege to add context and close it as well)
- Shekar
On
I am still not fully sure how this would pan out. Since at each stage,
producer sends an event and has no control over the consumer.
{Web services call} -> {samza enrichment1} -> {samza enrichment2}
||
||
Dear Harlan and Felix,
Many thanks for your input! In my particular case I decided to use
external KV-store sharded by the same key as partition key in Kafka
topic. KV-store shards will be colocated with samza tasks processing
corresponding topic partitions in order to minimize latency.
Best
14 matches
Mail list logo
