hi, Vadim,
Nice suggestion. So I guess that we can do it by making the internal
metrics name as a structured object w/ tag + name, and allow actual
implementation of metric reporters to format the serialized metrics name
according to the different metrics DB.
Would you please open a JIRA for
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44935/#review125808
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On March
deployment as
well. Please add the online documentation for this feature.
- Yi Pan (Data Infrastructure)
On March 15, 2016, 5:33 p.m., Boris Shkolnik wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit
de is almost dup from the ProcessJobFactory. Can we fold
this in the config.get()? Or some utility class?
- Yi Pan (Data Infrastructure)
On March 15, 2016, 5:33 p.m., Boris Shkolnik wrote:
>
> ---
> This is an automatically gener
://reviews.apache.org/r/45324/diff/
Testing
---
Locally build via ./gradlew clean build
Thanks,
Yi Pan (Data Infrastructure)
/45144/#comment188120>
nit: the key in the example shows containerId = 1 and the values show
containerId = 139. They should be the same, right?
- Yi Pan (Data Infrastructure)
On March 24, 2016, 9:33 p.m., Jake Maes wrote:
>
> ---
> org.apache.samza.checkpoint.kafka.KafkaCheckpointManagerFactory
>
> task.checkpoint.system=kafka
>
> task.checkpoint.replication.factor=3
>
>
>
> On Tue, Mar 22, 2016 at 1:33 PM, Yi Pan <nickpa...@gmail.com> wrote:
>
> > Hi, Yuanchi,
> >
> > Did you check y
to see if that's
>> related since our current version is 2.6.0.
>>
>> Thanks!
>> Yuanchi
>>
>> On Wed, Mar 23, 2016 at 2:57 PM, Yi Pan <nickpa...@gmail.com> wrote:
>>
>>> Hi, Yuanchi,
>>>
>>> Is this related w/ the issue you repor
Hi, Yuanchi,
Is this related w/ the issue you reported earlier regarding to "problem
picking up checkpoint after upgrade" in another thread? I assume that you
are using the official Samza 0.10 release? That has jackson version 1.8.5
by default. How do you change it in your own build/package to
/45189/diff/
Testing
---
Thanks,
Yi Pan (Data Infrastructure)
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44772/#review124924
---
Ship it!
LGTM! Thanks!
- Yi Pan (Data Infrastructure
Hi, Yuanchi,
Did you check your configuration of task.checkpoint.system? What are the
config value you used in 0.9 and what's the current configuration in 0.10?
If you can share your config before and after the upgrade, + the container
log from 0.10, we can be more helpful.
Thanks!
-Yi
On Tue,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44952/#review124627
---
Ship it!
LGTM! Thanks!
- Yi Pan (Data Infrastructure
the
purpose of this section of code within if?
- Yi Pan (Data Infrastructure)
On March 4, 2016, 8:14 p.m., Navina Ramesh wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://re
Hi, Weinan,
We have not seen this hanging issue at LinkedIn. But it would be good to
track that. We will keep an eye on issue-696 as well.
Thanks for reporting!
-Yi
On Sun, Mar 13, 2016 at 8:03 PM, Weinan Zhao wrote:
> Hi all,
>
> I've encountered Samza on yarn couldn't
Hi, Jack,
There have been asks similar to yours, like SAMZA-427. As fixed in
SAMZA-59, we also included metrics to report the count of deserialization
errors. If you are asking about the actual message that caused the error to
be reported, there has to be a different way. Options are:
1) write
Hi, Rohit,
On Thu, Mar 10, 2016 at 9:53 PM, Rohit Bansal
wrote:
> 1) Is it possible to analyze the metrics (graphs of messages , disk space
> and other details for performance / status check) ? In Application master
> in YARN UI, it contains only config information and
Hi, Rohit,
RocksDB TTL is best-effort:
https://github.com/facebook/rocksdb/wiki/Time-to-Live. And the expired
records are removed during compaction.
I wonder in your test case whether the compaction has ever happened. How
long did you wait to see whether records are gone or not?
-Yi
On Thu,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43350/#review122363
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Feb. 24
068/#comment184192>
I recommend to drop this seekToLast() for now. Based on your use case
description, to achieve the backward traverse, you would need both seekToLast()
and previous() in the iterator. Adding seekToLast() only won't be sufficient.
- Yi Pan (Data Infrastructure)
On Feb. 26, 2016
/
Testing
---
Locally build and deployed w/ ./gradlew and mvn
Thanks,
Yi Pan (Data Infrastructure)
Hi, Vadim,
Glad that you figured out. Please let us know if you have further questions.
-Yi
On Wed, Mar 2, 2016 at 6:57 PM, Vadim Chekan wrote:
> Never mind, I forgot to "listen" to new metrics in my reporter, so those
> metrics which were created immediately worked
orking well, so we are thinking to update that patch later this week
> so it can be added to the main project.
>
> HTH,
>
> Jose Luis Barrueta
>
> On Wed, Mar 2, 2016 at 2:11 PM, Yi Pan <nickpa...@gmail.com> wrote:
>
> > Hi, Robert,
> >
>
issue.
samza-kafka/src/main/scala/org/apache/samza/system/kafka/BrokerProxy.scala
(line 259)
<https://reviews.apache.org/r/44293/#comment183537>
Were SREs alerted on the number of WARNs? If yes, we should reduce it to
INFO.
- Yi Pan (Data Infrastructure)
On March 2, 2016, 9:
Hi, Robert,
The main reason that ThreadJobFactory and ProcessJobFactory are not
considered "production-ready" is that there is only one container for the
job and all tasks are assigned to the single container. Hence, it is not
easy to scale out of a single host.
As Rick mentioned, Netflix has
uploaded.
Could you try to rebase and upload again?Thanks!
gradle/dependency-versions.gradle (line 23)
<https://reviews.apache.org/r/43732/#comment183340>
Please rebase w/ the latest master branch.
- Yi Pan (Data Infrastructure)
On Feb. 25, 2016, 7:39 p.m., Edi Bice
Thanks for all the +1s! I have created
https://issues.apache.org/jira/browse/SAMZA-880 to track it.
Thanks!
-Yi
On Wed, Feb 24, 2016 at 5:31 PM, Boris Shkolnik <bor...@gmail.com> wrote:
> +1 for pull requests.
>
> On Thu, Feb 18, 2016 at 3:53 PM, Yi Pan <nickpa...@gmail.co
Hi, Jose,
Glad that you have already figured out the problem!
Cheers!
-Yi
On Wed, Feb 24, 2016 at 2:50 PM, José Barrueta wrote:
> Hi all,
>
> Just to let you know, we already figured it out the problem, issue was that
> we had a dependency version conflict that result in
e AvroDataFileWriter? Can we move it
to another patch?
- Yi Pan (Data Infrastructure)
On Feb. 18, 2016, 7:46 p.m., Edi Bice wrote:
>
> ---
> This is an automatically generated e-ma
Hi, Chad,
The following code will let you find the stream name:
{code}
envelope.getSystemStreamPartition().getSystemStream().getStream();
{code}
Thanks!
-Yi
On Tue, Feb 23, 2016 at 8:14 AM, Chad Scribner
wrote:
> Hi All,
>
> First time emailing the list. I just
;> +1 - Thanks for bringing this up, Yi. I've done it both ways and feel
> >>>> pull requests are much easier.
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On Feb 18, 2016, at 4:25 PM, Navina Ramesh
> >>>
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43766/#review119907
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Feb. 19
Hi, all,
I want to start the discussion on our code review/commit process.
I felt that our code review and check-in process is a little bit
cumbersome:
- developers need to create RBs and attach diff to JIRA
- committers need to review RBs, dowload diff and apply, then push.
It would be much
.e. wrong system configuration)
- Yi Pan (Data Infrastructure)
On Feb. 18, 2016, 8:04 p.m., Boris Shkolnik wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43589/#review119654
---
Ship it!
lgtm! Thanks!
- Yi Pan (Data Infrastructure
://reviews.apache.org/r/43550/diff/
Testing
---
Ran the full set of unit tests both on Mac and Linux and both passed.
Thanks,
Yi Pan (Data Infrastructure)
O is the requirement to build a jar to run a
> job
> > > during
> > > development. I think it would be possible to define these classes in
> Java
> > > and
> > > have them call into a Clojure API but that's basically what I'm trying
> to
> > > avoid
> >
Hi, Rick and John,
Thanks for the great discussion! As Jacob said, we realized the possible
drawbacks relying solely on YARN for process liveness detection as well and
that's why SAMZA-871 was opened. Please help to comment on the JIRA so that
we can track the discussion and move the design
> On Jan. 19, 2016, 4:38 a.m., Yi Pan (Data Infrastructure) wrote:
> > pom.xml, line 289
> > <https://reviews.apache.org/r/42484/diff/1/?file=1200969#file1200969line289>
> >
> > We have observed an issue with YARN 2.6.0 AM client that would not
> > r
Hi, Avi,
Could you try to fix the jackson version to 1.9.13 in your build first? It
seems like a incompatible jackson version issue, as you have noticed in
your classpath. It would be good if you can share your maven pom.xml as
well.
Thanks!
-Yi
On Mon, Feb 8, 2016 at 1:12 PM, Avi Flax
---
Thanks,
Yi Pan (Data Infrastructure)
t end to end latency
> stats
>(total pipeline latency = commit time - event time).
>
> #3 is easily solvable with a additional plugin options. #1 and #2 require
> changing the system producer API.
>
> Roger
>
> On Tue, Feb 9, 2016 at 10:56 AM, Yi Pan <nickpa...@gmail.c
> notify the sender immediately by telephone at 857.285.1263 or by return
> email and promptly delete this message from your system.
>
> On 9 February 2016 at 22:25, Yi Pan <nickpa...@gmail.com> wrote:
>
> > Hi, Andy,
> >
> > I think that you are looking for the feature in
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43074/#review118603
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Feb. 3
method SamzaAppState.isValidContainerId(containerId) here.
- Yi Pan (Data Infrastructure)
On Feb. 10, 2016, 2:40 a.m., Jake Maes wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.
Hi, Andy,
I think that you are looking for the feature in SAMZA-697. Or are you
looking for something even more specific?
On Tue, Feb 9, 2016 at 10:22 PM, Andy Chambers <
andy.chamb...@fundingcircle.com> wrote:
> Hey Folks,
> I'm trying to build some tooling to make writing jobs in Clojure a
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43053/#review118598
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Feb. 5
/JobConfig.scala (line 46)
<https://reviews.apache.org/r/43053/#comment179879>
One more nit that I forgot: it would be nice to document why we have to add
this config: a) Kafka topic auto-creation can not be easily turned off; b)
Kafka delete topic does not work.
- Yi Pan (Data Infrastructure)
On
43074?
- Yi Pan (Data Infrastructure)
On Feb. 10, 2016, 2:40 a.m., Jake Maes wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache
Hi, Avi,
Thanks for point out the online doc problem! I messed the latest online doc
up when fixing SAMZA-782. Now it should be fixed! Please check the latest
online doc again and let us know if you see any further problems w/ it.
Thanks a lot!
-Yi
On Mon, Feb 8, 2016 at 12:39 PM, Avi Flax
Hi, all Samza lovers,
We recently submit a talk on Samza to Hadoop Summit this year. If you are
interested in seeing this talk in the conference, please help to vote on
the talk:
Hi, Ramesh,
Could you share the exact stack trace and the job configuration, especially
the Kafka producer configuration for the changelog system?
Thanks!
-Yi
On Thu, Feb 4, 2016 at 11:56 AM, Ramesh Bhojan
wrote:
> Dear team @ Samza,
> I would really appreciate some
Hi, David,
The "compaction" referred to together w/ TTL is referring to RocksDb's
compaction, not the Kafka-based changelog topic. Currently, TTL is not
applied to Kafka-based changelog topic. SAMZA-677 is opened for this.
-Yi
On Thu, Jan 28, 2016 at 11:36 AM, David Garcia
d as a check inside the method
> BlockingEnvelopeMap.put(...) - it is better to delay a bit than halt/crash
> the whole consumer due to memory limitation.
>
>
> Rgds,
> Marcelo
>
>
> From: Yi Pan <nickpa...@gmail.com>
> To: dev@samza.apache.org; Marcelo Romaniuc <mroma...
;> email Peter (CC'ed) or me about any questions. FYI: the real solution would
>> be to implement standby containers. This solution is an attempt to do the
>> same.
>>
>> On Thu, Jan 14, 2016 at 10:17 AM, Yi Pan <nickpa...@gmail.com> wrote:
>>
>>> It
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42619/#review116220
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Jan. 21
> On Dec. 8, 2015, 10:55 p.m., Yi Pan (Data Infrastructure) wrote:
> > @Amit, thanks for putting up this patch. I have two high-level comments:
> > * I would prefer to keep the return type of seek() as an iterator. The
> > pattern of the current API looks fine to me: al
Hi, Michael,
Your use case sounds much like a "customized checkpointing" to me. We have
similar cases in LinkedIn and the following are the solution in production:
1) disable Samza auto-checkpoint by setting the commit_ms to -1
2) explicitly calling TaskCoordinator.commit() in sync with closing
484/#comment175966>
Samza 0.10.0 is officially released. Hence, this change should be made in
hello-samza master branch, not latest. The latest branch is used to track and
keep in-sync with samza trunk, which is under-development branch.
- Yi Pan (Data Infrastructure)
On Jan. 19, 2016, 4:16 a.
484/#comment175968>
We have observed an issue with YARN 2.6.0 AM client that would not refresh
the token (YARN-3103). Hence, we have updated the minimum required YARN version
for Samza 0.10.0 to YARN 2.6.0. Does CDH 5.4 not having this issue?
- Yi Pan (Data Infrastructure)
On Jan. 19, 2016, 4:
roject, changed the directory into the
> project and ran ‘./gradlew’. Since it’s stated ‘./gradlew’ and the file is
> present in the project, that’s what I assumed.
>
> Cheers
> Christian
> --
>
>
>
> Christian Kniep | Release Engineer
>
> www.gaikai.com
>
&
or walking in my shoes a bit. Let's say afterwards you would have a
> howto that serve java-rockies like me as well. :)
>
> Cheers
> Christian
>
> On Fri, Jan 15, 2016 at 6:45 PM, Yi Pan <nickpa...@gmail.com> wrote:
>
> > Hi, Christian,
> >
> >
> > The
but it seems: Habemus Samza![image:
>> Inline image 1]
>>
>> On Fri, Jan 15, 2016 at 8:22 PM, Christian Kniep <ckn...@gaikai.com>
>> wrote:
>>
>>> I downloaded the tgz from http://samza.apache.org/startup/download/.
>>>
>>> I'll give a t
Hi, Stanislov,
That's awesome! It would be great to have this integrated w/ Samza
tutorial. Would you mind to create a tutorial page for the join job
implementation in Samza?
Thanks a lot!
-Yi
On Thu, Jan 14, 2016 at 7:28 AM, Stanislav Los
wrote:
> If anyone
Hi, Christian,
Which local directory are you running ./gradlew publishToMavenLocal from?
The command needs to be executed from the directory under which the Samza
project is checked out, *not* where the hello-samza project is checked out.
-Yi
On Thu, Jan 14, 2016 at 7:53 AM, Christian Kniep
It might be the mail list restriction. Could you try to my personal email
(i.e. nickpa...@gmail.com)?
On Thu, Jan 14, 2016 at 10:15 AM, Chinmay Soman <chinmay.cere...@gmail.com>
wrote:
> It shows as attached in my sent email. That's weird.
>
> On Thu, Jan 14, 2016 at 10:14 AM,
Hi, Alex,
I apologize for the late reply. Let me try to give some feedbacks/comments
below:
On Thu, Jan 7, 2016 at 3:59 PM, Alexander Filipchik
wrote:
>
> 1) What is the best way to handle partial outages. Let's say my yarn
> cluster is deployed on amazon among 3
Hi, Leo,
Samza RocksDB store stores ByteArray for keys and values on-disk. You can
define your own key and msg serde via the configuration (
http://samza.apache.org/learn/documentation/0.10/jobs/configuration-table.html#stores-key-serde,
Hi, all,
In case you missed the announcement of Samza 0.10 release before the
Christmas, please check it out here: https://blogs.apache.org/samza/ and
help to spread out the word on twitter.
And happy new year to everyone!
Thanks!
-Yi
/JobCoordinator.scala
<https://reviews.apache.org/r/41663/#comment173181>
I am a bit confused here. If the refreshJobModel() function actually
returns a different jobModel than what's already set in jobModelRef, isn't the
whole point is to replace it w/ the new one?
- Yi Pan (Data Infrastr
> On Jan. 4, 2016, 11:11 p.m., Yi Pan (Data Infrastructure) wrote:
> > samza-core/src/main/scala/org/apache/samza/coordinator/JobCoordinator.scala,
> > line 204
> > <https://reviews.apache.org/r/41663/diff/2-3/?file=1181044#file1181044line204>
> >
Hi, Rick,
Please refer to the whole discussion on SAMZA-552, which exactly targets
the issues that you are considering. We have been working on the design and
proto-type since last year. The work was paused for the last few months due
to other priorities. We are planning to resume the work this
-gradle.txt PRE-CREATION
README.md 0a71cf634a6757d8f5cfe4ca1d9cef1e45695c8f
src/main/config/wikipedia-parser.properties
8f1086f051ed9ebc5df57dc3897a5fb1497d8c18
Diff: https://reviews.apache.org/r/41636/diff/
Testing
---
All build and local deployment succeeded.
Thanks,
Yi Pan (Data
are writing
> some upstream Samza jobs. The only way to get it write in a particular
> partitioning scheme is then to write a different KafkaSystemFactory right ?
> Or perhaps patch the existing one ? I don't see a reason why it has to
> always use the default partitioning..
>
> On 17
---
Generated the site locally and test successfully.
Thanks,
Yi Pan (Data Infrastructure)
gradle.properties b18c0cb62aec7592e8bfb1f2aa83c6b8eada867f
Diff: https://reviews.apache.org/r/41576/diff/
Testing (updated)
---
Locally published all sites and traversed successfully.
Thanks,
Yi Pan (Data Infrastructure)
---
Locally published all sites and traversed successfully.
Thanks,
Yi Pan (Data Infrastructure)
Hi, Ivan,
Sorry to reply late. Could you explain what state that you have to maintain
in SystemConsumer, not in KV-store and checkpoint topics? Samza's
SystemConsumer is designed as a "pump" to simply pump the messages in to
Samza StreamTasks, where the main stateful process is executed. Why and
Hi, Anton,
It seems to me that the best option would possibly use the row number as
the IncomingMessageEnvelope's offset. Then, when Samza commits the
checkpoint, it will commit the row number as the offset. When the Samza job
restarts, the row number would be read from the checkpoint topic and
Hi, Michal,
Sorry to reply late. Actually, you are right that the "partition.class"
configuration is not used in Samza to determine the outgoing partition. In
Samza, partition is defined by the following code sections:
{code}
val topicName = envelope.getSystemStream.getStream
val partitions:
Hi, Kishore,
Could you open a JIRA for this small SST files issue? It is good to track
it s.t. we won't forget this one.
Thanks!
-Yi
On Thu, Dec 17, 2015 at 4:16 AM, Kishore N C wrote:
> Hi Tao,
>
> > I am not sure what do you mean by ulimit issues
>
> When so many small
Hi, Kishore,
First, I would like to ask which version of Samza you are running? And if
you can attach the log and config of your container (i.e. I assume the log
you attached here is a container log?), it would be greatly helpful.
Thanks a lot!
-Yi
On Mon, Dec 14, 2015 at 5:07 AM, Kishore N C
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41071/#review109387
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Dec. 8
object:
import org.apache.samza.config.JobConfig.Config2Job
- Yi Pan (Data Infrastructure)
On Dec. 8, 2015, 10:49 p.m., Tao Feng wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://re
Hi, Gordon,
Try to use --config X.Y.Z=value from the command line to run run-job.sh
On Tue, Dec 8, 2015 at 5:57 PM, Gordon Tai wrote:
> Hi Rad,
>
> Our Samza jobs run on on-premiere clusters, on top of YARN and Kafka. So
> IAM roles won't be an option either.
>
> BR,
>
> On 9
[ ] -1 disapprove (and reason why)
+1 from my side for the release.
Yi Pan
nickpa...@gmail.com
Hi, Bart,
Your question is more like "is Kafka reliable against failures"? As for the
reliability of the changelog, Samza is designed as reliable as the
underlying messaging layer provides. In the case of Kafka, there are
configurations in the Kafka producer that users can tune up to make sure of
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40934/#review108910
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Dec. 3
Hi, Elias,
Thanks a lot to put up the patch for the simple job running in Kubernetes!
As Kartik mentioned, that is well aligned w/ our goal to make Samza job
launching easier. I am glad that we actually share a lot of common ideas
from independent minds. Let me try to give my opinions on this:
1.
/TestKafkaSystemConsumer.scala
23fa9398e89edeeabfd3ee754c27a8f3bec417b0
Diff: https://reviews.apache.org/r/40624/diff/
Testing
---
./gradlew clean build passed.
run ./bin/integration-tests.sh passed as well.
Thanks,
Yi Pan (Data Infrastructure)
o move this condition to KafkaConfig as a method - boolean
> > isFetchLimitByBytesEnabled();
Make sense. Will do.
- Yi
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40624/#review107823
--
/TestKafkaSystemConsumer.scala
23fa9398e89edeeabfd3ee754c27a8f3bec417b0
Diff: https://reviews.apache.org/r/40624/diff/
Testing (updated)
---
./gradlew clean build passed.
run ./bin/integration-tests.sh passed as well.
Thanks,
Yi Pan (Data Infrastructure)
23fa9398e89edeeabfd3ee754c27a8f3bec417b0
Diff: https://reviews.apache.org/r/40624/diff/
Testing
---
./gradlew clean build passed.
Thanks,
Yi Pan (Data Infrastructure)
-test/src/main/config/perf/kafka-read-write-performance.properties
112caba4f3b5cc05570ca4f746e0bf4ecf9a21c7
Diff: https://reviews.apache.org/r/40622/diff/
Testing
---
Thanks,
Yi Pan (Data Infrastructure)
> On Nov. 20, 2015, 6:53 a.m., Yi Pan (Data Infrastructure) wrote:
> > samza-kv-rocksdb/src/test/scala/org/apache/samza/storage/kv/TestRocksDbKeyValueStore.scala,
> > line 84
> > <https://reviews.apache.org/r/40525/diff/1/?file=1133805#file1133805line84&g
/apache/samza/test/integration/TestStatefulTask.scala
(line 72)
<https://reviews.apache.org/r/40457/#comment166220>
The patch to SAMZA-754 already added this to StreamTaskTestUtils.
- Yi Pan (Data Infrastructure)
On Nov. 18, 2015, 10:13 p.m., Navina Ramesh
/apache/samza/job/yarn/YarnJob.scala (line 76)
<https://reviews.apache.org/r/40485/#comment166228>
nit: better to follow the convention that each input argument to
submitApplication() starts a newline and aligned.
- Yi Pan (Data Infrastructure)
On Nov. 19, 2015, 2:56 p.m., Aleksandar Pej
/TestRocksDbKeyValueStore.scala
(line 84)
<https://reviews.apache.org/r/40525/#comment166391>
To make sure that it is flush() that write to the disk, not close(), you
may want to keep this db open and open another db in read-only mode to verify
that the read-only db sees the data.
- Yi Pan
Hi, Rick,
I think that you are running into SAMZA-754. I have a RB available for it
already. I will upload the patch and it would be good if you can try the
patch to see whether that solves your problem.
-Yi
On Tue, Nov 17, 2015 at 12:01 PM, Rick Mangi wrote:
> Hi, getting
was calling
> next() on a range iterator twice :(.
> After removing the duplicate call everything works as expected.
>
> Thank you!
>
> Alex
>
> On Mon, Nov 16, 2015 at 10:45 PM, Yi Pan <nickpa...@gmail.com> wrote:
>
> > Hi, Alexander,
> >
>
401 - 500 of 707 matches
Mail list logo