Re: [DISCUSS] Necessity of Maven *and* SBT Build in Spark

tions to using sbt or maven ! > >> Too many exclude versions, pinned versions, etc would just make things > >> unmanageable in future. > >> > >> > >> Regards, > >> Mridul > >> > >> > >> > >> > >> On W

Re: [DISCUSS] Necessity of Maven *and* SBT Build in Spark

others. (#NelsonMandela) > >> On Feb 25, 2014, at 6:50 PM, Mridul Muralidharan wrote: >> >>> On Wed, Feb 26, 2014 at 5:31 AM, Patrick Wendell wrote: >>> Evan - this is a good thing to bring up. Wrt the shader plug-in - >>> right now we don't actuall

Re: [DISCUSS] Necessity of Maven *and* SBT Build in Spark

On Wed, Feb 26, 2014 at 5:31 AM, Patrick Wendell wrote: > Evan - this is a good thing to bring up. Wrt the shader plug-in - > right now we don't actually use it for bytecode shading - we simply > use it for creating the uber jar with excludes (which sbt supports > just fine via assembly). Not re

Re: Preparing to provide a small text files input API in mllib

Hi, I have not looked into why this would be needed, but given it is needed, I added a couple of comments to the PR. Overall, it looks promising. Regards, Mridul On Tue, Feb 25, 2014 at 8:05 AM, 尹绪森 wrote: > Hi community, > > As I moving forward to write a LDA (Latent Dirichlet Allocation) t

Re: Anyone wants to look at SPARK-1123?

Curious, what was the issue ? - Mridul On Sun, Feb 23, 2014 at 11:41 PM, Nan Zhu wrote: > OK, I know where I was wrong > > > Best, > > -- > Nan Zhu > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > On Sunday, February 23, 2014 at 12:50 PM, Nan Zhu wrote: > >> String, it should be ge

Re: [DISCUSS] Extending public API

e (sparkbank)? Curious to know how you'd decide what > should go where. > > Amandeep > > > On Feb 22, 2014, at 10:06 PM, Mridul Muralidharan > wrote: > > > > Hi, > > > > Over the past few months, I have seen a bunch of pull requests which > have

[DISCUSS] Extending public API

Hi, Over the past few months, I have seen a bunch of pull requests which have extended spark api ... most commonly RDD itself. Most of them are either relatively niche case of specialization (which might not be useful for most cases) or idioms which can be expressed (sometimes with minor perf p

Re: [DISCUSS] Necessity of Maven *and* SBT Build in Spark

I am not sure if this is resolved now - but maven was better at building the assembly jars compared to sbt. To the point where I stopped using sbt due to unpredictable order in which it unjars the dependencies to create the assembled jar (we do have quite a lot of conflicting classes in our depende

Re: Fwd: ASF Board Meeting Summary - February 19, 2014

Wonderful news ! Congrats all :-) Regards, Mridul On Feb 20, 2014 10:07 PM, "Andy Konwinski" wrote: > Congrats Spark community! I think this means we are officially now a TLP! > -- Forwarded message -- > From: "Brett Porter" > Date: Feb 19, 2014 11:26 PM > Subject: ASF Board Mee

Re: coding style discussion: explicit return type in public APIs

ideline. It is invoking a function createFoo, not > the > > constructor of Foo. > > > > > > > > > > On Wed, Feb 19, 2014 at 10:39 AM, Mridul Muralidharan > >wrote: > > > > > Without bikeshedding this too much ... It is likely incorrect (no

Re: coding style discussion: explicit return type in public APIs

e createFoo example? > > def myFunc = createFoo > > is disallowed in my guideline. It is invoking a function createFoo, not the > constructor of Foo. > > > > > On Wed, Feb 19, 2014 at 10:39 AM, Mridul Muralidharan >wrote: > > > Without bikeshedding this too much

Re: coding style discussion: explicit return type in public APIs

t up is not a matter of readability or style. If it > returns a different type, it should be declared (otherwise it is just > wrong). > > > On Wed, Feb 19, 2014 at 12:17 AM, Mridul Muralidharan >wrote: > > > You are right. > > A degenerate case would be : &g

Re: coding style discussion: explicit return type in public APIs

. It was implicit in my email, but the return type >> should be the same as the class itself. >> >> >> >> >> On Tue, Feb 18, 2014 at 10:37 PM, Mridul Muralidharan > >wrote: >> >> > Case 3 can be a potential issue. >> > Curre

Re: coding style discussion: explicit return type in public APIs

Case 3 can be a potential issue. Current implementation might be returning a concrete class which we might want to change later - making it a type change. The intention might be to return an RDD (for example), but the inferred type might be a subclass of RDD - and future changes will cause signatur

Re: Bug in spark.shuffle.spill setting? (0.9.0)

I had not resolved it in time for 0.9 - but IIRC there was a recent PR which fixed bugs in spill [1] : are you able to reproduce this with spark master ? Regards, Mridul [1] https://github.com/apache/incubator-spark/pull/533 On Wed, Feb 19, 2014 at 9:58 AM, Andrew Ash wrote: > I confirmed also

Re: oome from large map output status

There is nothing wrong with 9k partitions - I actually use much higher :-) [1] I have not really seen this interesting issue you mentioned - should investigate more, thanks for the note ! Regards, Mridul [1] I do use insanely high frame size anyway - and my workers/master run with 8g; maybe why

Re: [VOTE] Graduation of Apache Spark from the Incubator

+1 ! - Mridul On Tue, Feb 11, 2014 at 9:57 AM, Chris Mattmann wrote: > Hi Everyone, > > This is a new VOTE to decide if Apache Spark should graduate > from the Incubator. Please VOTE on the resolution pasted below > the ballot. I'll leave this VOTE open for at least 72 hours. > > Thanks! > > [ ]

Re: [0.9.0] Possible deadlock in shutdown hook?

scala/org/apache/spark/scheduler/DAGScheduler.scala#L610 >> > > >>> does >> > > >> not seem to actually cancel the jobs, only mark them as failed. So >> it >> > > >> may be a simple addition. >> > > >> >> > > >

Re: Is there any way to make a quick test on some pre-commit code?

This is neat, thanks Reynold ! Regards, Mridul On Fri, Feb 7, 2014 at 6:20 AM, Reynold Xin wrote: > You can do > > sbt/sbt assemble-deps > > > and then just run > > sbt/sbt package > > each time. > > > You can even do > > sbt/sbt ~package > > for automatic incremental compilation. > > > > On Thu

Re: [0.9.0] Possible deadlock in shutdown hook?

f-deleted temp dirs scattered across the cluster. > > How feasible do you think it'd be to interrupt the other threads? > > > On Thu, Feb 6, 2014 at 10:54 AM, Mridul Muralidharan wrote: > >> Looks like a pathological corner case here - where the the delete >> thread is

Re: Proposal for JIRA and Pull Request Policy

+1 Would be great if the JIRA tag was 'clickable' to go to the actual JIRA :-) Regards, Mridul On Fri, Feb 7, 2014 at 5:35 AM, Patrick Wendell wrote: > As a break out from the other thread. I'd like to propose two > guidelines for pull requests. These guidelines are to make things > easier to

Re: [0.9.0] Possible deadlock in shutdown hook?

han the cleanup threads can delete from disk. > > What do you think of that theory? > > > Andrew > > > > On Thu, Feb 6, 2014 at 2:30 AM, Mridul Muralidharan > wrote: >> >> shutdown hooks should not take 15 mins are you mentioned ! >> On the other hand, how bus

Re: [0.9.0] Possible deadlock in shutdown hook?

shutdown hooks should not take 15 mins are you mentioned ! On the other hand, how busy was your disk when this was happening ? (either due to spark or something else ?) It might just be that there was a lot of stuff to remove ? Regards, Mridul On Thu, Feb 6, 2014 at 3:50 PM, Andrew Ash wrote:

Re: Proposal for Spark Release Strategy

The reason I explicitly mentioned about binary compatibility was because it was sort of hand waved in the proposal as good to have. My understanding is that scala does make it painful to ensure binary compatibility - but stability of interfaces is vital to ensure dependable platforms. Recompilation

Re: Proposal for Spark Release Strategy

Before we move to 1.0, we need to address two things : a) backward compatibility not just at api level, but also at binary level (not forcing recompile). b) minimize external dependencies - some of them would go away/not be actively maintained. Regards, Mridul On Thu, Feb 6, 2014 at 11:50 AM,

Re: [DISCUSS] Graduating as a TLP

Great news ! +1 Regards, Mridul On Fri, Jan 24, 2014 at 4:15 AM, Matei Zaharia wrote: > Hi folks, > > We’ve been working on the transition to Apache for a while, and our last > shepherd’s report says the following: > > > Spark > > Alan Cabrera (acabrera): > > Seems like

Re: Config properties broken in master

are included since you raised the issues in prev RC? > > Thanks, > > Henry > > On Sun, Jan 19, 2014 at 10:33 AM, Mridul Muralidharan > wrote: >> Oh great, just saw the PR from Matei ... for some odd reason, the dev >> mails are coming to be horribly delayed. &g

Re: Config properties broken in master

ptions which had a.b and a.b.c... they > should all work in the new RC. > > On Sun, Jan 19, 2014 at 4:56 AM, Mridul Muralidharan wrote: >> Chanced upon spill related config which exhibit same pattern ... >> >> - Mridul >> >> On Sun, Jan 19, 2014 at 1:10 AM,

Re: Config properties broken in master

tei Zaharia > wrote: > >> This is definitely an important issue to fix. Instead of renaming >> properties, one solution would be to replace Typesafe Config with just >> reading Java system properties, and disable config files for this release. >> I kind of like that over

Re: Config properties broken in master

this release. >> I kind of like that over renaming. >> >> Matei >> >> On Jan 18, 2014, at 11:30 AM, Mridul Muralidharan >> wrote: >> >> > Hi, >> > >> > Speculation was an example, there are others in spark which are >> &g

Re: Config properties broken in master

tch? > > maybe we can restrict that all properties in Spark should be "three levels" > > > On Sat, Jan 18, 2014 at 2:10 PM, Mridul Muralidharan wrote: > >> Hi, >> >> Unless I am mistaken, the change to using typesafe ConfigFactory has >> broken s

Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc1)

I would vote -1 for this release until we resolve config property issue [1] : if there is a known resolution for this (which I could not find unfortunately, apologies if it exists !), then will change my vote. Thanks, Mridul [1] http://apache-spark-developers-list.1001551.n3.nabble.com/Config-p

Config properties broken in master

Hi, Unless I am mistaken, the change to using typesafe ConfigFactory has broken some of the system properties we use in spark. For example: if we have both -Dspark.speculation=true -Dspark.speculation.multiplier=0.95 set, then the spark.speculation property is dropped. The rules of parseProper

Re: Important: Changes to Spark's build system on master branch

hadoop2, in this context, is use of spark on a hadoop cluster without yarn but with hadoop2 interfaces. hadoop2-yarn uses yarn RM to launch a spark job (and obviously uses hadoop2 interfaces). Regards, Mridul On Wed, Aug 21, 2013 at 11:52 PM, Konstantin Boudnik wrote: > For what it worth guys -

Re: Spark 0.8 branch

Hi Matei, Not sure if it is already planned, but the write related Connection race condition Patrick reported/fixed might need to go to 0.8 also ... Regards Mridul On Aug 9, 2013 11:12 PM, "Matei Zaharia" wrote: > Hi folks, > > In order to make the 0.8 release soon, I've created a new branch

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720544#comment-13720544 ] Mridul Muralidharan commented on BOOKKEEPER-648: To add to my com

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720540#comment-13720540 ] Mridul Muralidharan commented on BOOKKEEPER-648: I was expecting

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719348#comment-13719348 ] Mridul Muralidharan commented on BOOKKEEPER-648: Flavio, I am

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719324#comment-13719324 ] Mridul Muralidharan commented on BOOKKEEPER-648: On going over

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718369#comment-13718369 ] Mridul Muralidharan commented on BOOKKEEPER-648: I tried it 3 t

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718365#comment-13718365 ] Mridul Muralidharan commented on BOOKKEEPER-648: I tried it 3 t

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718267#comment-13718267 ] Mridul Muralidharan commented on BOOKKEEPER-648: I was not abl

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568313#comment-13568313 ] Mridul Muralidharan commented on BOOKKEEPER-312: Oh great ! I saw

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568271#comment-13568271 ] Mridul Muralidharan commented on BOOKKEEPER-312: I am not sure w

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568242#comment-13568242 ] Mridul Muralidharan commented on BOOKKEEPER-312: How can I get to

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.9) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.10 Fixes license problems that Ivan

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.9) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.5) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.4) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.2) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.3) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.10) > Implementat

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.10) > Implementat

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.1) > Implementation

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565644#comment-13565644 ] Mridul Muralidharan commented on BOOKKEEPER-312: Hi Ivan, a)

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565194#comment-13565194 ] Mridul Muralidharan commented on BOOKKEEPER-312: A) About @au

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562604#comment-13562604 ] Mridul Muralidharan commented on BOOKKEEPER-312: Please note that

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.10 Trying with : git diff --no

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.10 The issue seems to be version

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch.1) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch.2) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch.2 Try to workaround the warnings generated

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch.2) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch.2) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch.2 All @RunWith tests need to have public

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551830#comment-13551830 ] Mridul Muralidharan commented on BOOKKEEPER-312: $ git a

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch.2 compile errors ? unexpected - retrying

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.9 Generated via git diff -r

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch.2 Verified to work against jms client

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.9 > Implementation of

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551558#comment-13551558 ] Mridul Muralidharan commented on BOOKKEEPER-312: Attached final p

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: (was: hedwig-client-jms.patch.9) > Implementation

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.9 > Implementation of

[jira] [Commented] (BOOKKEEPER-545) Regression in subscriber.startDelivery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551522#comment-13551522 ] Mridul Muralidharan commented on BOOKKEEPER-545: Attached test

[jira] [Updated] (BOOKKEEPER-545) Regression in subscriber.startDelivery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-545: --- Attachment: TestClient.java > Regression in subscriber.startDeliv

[jira] [Updated] (BOOKKEEPER-545) Regression in subscriber.startDelivery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-545: --- Priority: Major (was: Critical) > Regression

[jira] [Created] (BOOKKEEPER-545) Regression in subscriber.startDelivery

Mridul Muralidharan created BOOKKEEPER-545: -- Summary: Regression in subscriber.startDelivery Key: BOOKKEEPER-545 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-545 Project: Bookkeeper

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch.1 setUp and tearDown methods are expected

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch Modifies the server test code to allow

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: (was: server_test.patch) > Modify hedwig ser

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Attachment: server_test.patch Modifies the server test code to allow

[jira] [Assigned] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan reassigned BOOKKEEPER-544: -- Assignee: Mridul Muralidharan > Modify hedwig server tests

[jira] [Updated] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

[ https://issues.apache.org/jira/browse/BOOKKEEPER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-544: --- Description: Allow client testcases to start/stop hedwig server as part

[jira] [Created] (BOOKKEEPER-544) Modify hedwig server tests to allow client testcases to start/stop them as part of their tests

Mridul Muralidharan created BOOKKEEPER-544: -- Summary: Modify hedwig server tests to allow client testcases to start/stop them as part of their tests Key: BOOKKEEPER-544 URL: https://issues.apache.org

Status of JMS provider

Hi, Flavio had asked me to send a status of the effort particularly in context of the roadmap. There are three pending issues : a) JMS provider. The review comments form Matthieu Morel have been integrated and attached to the review board, there are no outstanding issues. It is pending rev

[jira] [Commented] (BOOKKEEPER-308) Add support for JMS implementation for hedwig

[ https://issues.apache.org/jira/browse/BOOKKEEPER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447411#comment-13447411 ] Mridul Muralidharan commented on BOOKKEEPER-308: Any updates on

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428669#comment-13428669 ] Mridul Muralidharan commented on BOOKKEEPER-312: The review board

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428631#comment-13428631 ] Mridul Muralidharan commented on BOOKKEEPER-312: @Flavio. There

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427161#comment-13427161 ] Mridul Muralidharan commented on BOOKKEEPER-312: I assumed re

[jira] [Commented] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426018#comment-13426018 ] Mridul Muralidharan commented on BOOKKEEPER-312: As I menti

[jira] [Commented] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424784#comment-13424784 ] Mridul Muralidharan commented on BOOKKEEPER-311: Could be adde

[jira] [Commented] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424774#comment-13424774 ] Mridul Muralidharan commented on BOOKKEEPER-311: The line length

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.5 Changed line length to roughly 100

[jira] [Updated] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-311: --- Attachment: hedwig-client.patch.5 Changed line length to roughly 100

[jira] [Commented] (BOOKKEEPER-330) System.currentTimeMillis usage in Hedwig

[ https://issues.apache.org/jira/browse/BOOKKEEPER-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422062#comment-13422062 ] Mridul Muralidharan commented on BOOKKEEPER-330: No, my point

[jira] [Commented] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420587#comment-13420587 ] Mridul Muralidharan commented on BOOKKEEPER-311: Sijie Guo

[jira] [Commented] (BOOKKEEPER-350) Revisit consume interface in Hedwig Client

[ https://issues.apache.org/jira/browse/BOOKKEEPER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420582#comment-13420582 ] Mridul Muralidharan commented on BOOKKEEPER-350: Please note

<    6   7   8   9   10   11   12   13   14   15   >