[jira] [Commented] (DL-146) Fix Stream typo : initiaize

[ https://issues.apache.org/jira/browse/DL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763540#comment-15763540 ] ASF GitHub Bot commented on DL-146: --- GitHub user xieliang opened a pull request: https:

[GitHub] incubator-distributedlog pull request #79: DL-146 : fix Stream typo : initia...

GitHub user xieliang opened a pull request: https://github.com/apache/incubator-distributedlog/pull/79 DL-146 : fix Stream typo : initiaize -> initialize You can merge this pull request into a Git repository by running: $ git pull https://github.com/xieliang/incubator-distribu

[jira] [Created] (DL-146) Fix Stream typo : initiaize

Liang Xie created DL-146: Summary: Fix Stream typo : initiaize Key: DL-146 URL: https://issues.apache.org/jira/browse/DL-146 Project: DistributedLog Issue Type: Improvement Components: dist

[jira] [Commented] (DL-126) Fix the url of distributedlog blog post

[ https://issues.apache.org/jira/browse/DL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763536#comment-15763536 ] ASF GitHub Bot commented on DL-126: --- Github user asfgit closed the pull request at: htt

[GitHub] incubator-distributedlog pull request #52: DL-126: Fix the url of distribute...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-distributedlog/pull/52 --- 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 th

incubator-distributedlog git commit: DL-126: Fix the url of distributedlog blog post

Repository: incubator-distributedlog Updated Branches: refs/heads/master 60610047a -> 6e67a377f DL-126: Fix the url of distributedlog blog post fix the url for the blog post and but still keep the wrong url and make it redirect to the right url. Author: Sijie Guo Reviewers: Franck Cuny , L

[jira] [Commented] (DL-122) Use assertions from Junit rather than assert() for tests

[ https://issues.apache.org/jira/browse/DL-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763524#comment-15763524 ] Hudson commented on DL-122: --- UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #162

[jira] [Commented] (DL-123) Every tests should have timeout

[ https://issues.apache.org/jira/browse/DL-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763523#comment-15763523 ] Hudson commented on DL-123: --- UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #162

[jira] [Commented] (DL-136) Avoid empty catch blocks

[ https://issues.apache.org/jira/browse/DL-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763525#comment-15763525 ] Hudson commented on DL-136: --- UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #162

[jira] [Commented] (DL-28) generate java code failed using scrooge

[ https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763526#comment-15763526 ] Hudson commented on DL-28: -- UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #162 (S

[jira] [Commented] (DL-145) Fix the flaky testServiceTimeout

[ https://issues.apache.org/jira/browse/DL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763511#comment-15763511 ] ASF GitHub Bot commented on DL-145: --- GitHub user xieliang opened a pull request: https:

[GitHub] incubator-distributedlog pull request #78: DL-145 : the write requests shoul...

GitHub user xieliang opened a pull request: https://github.com/apache/incubator-distributedlog/pull/78 DL-145 : the write requests should be error out immediately even if the rolling writer still be creating Passed all test cases locally, now TestDistributedLogService#testServiceTi

[jira] [Commented] (DL-28) generate java code failed using scrooge

[ https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763408#comment-15763408 ] ASF GitHub Bot commented on DL-28: -- Github user asfgit closed the pull request at: https:

[GitHub] incubator-distributedlog pull request #73: DL-28 : using /* */ style comment...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-distributedlog/pull/73 --- 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 th

incubator-distributedlog git commit: DL-28: using /* */ style comment to avoid scrooge windows platform issue

Repository: incubator-distributedlog Updated Branches: refs/heads/master 306a2a97c -> 60610047a DL-28: using /* */ style comment to avoid scrooge windows platform issue Author: xieliang Reviewers: Sijie Guo , Leigh Stewart Closes #73 from xieliang/DL-28 Project: http://git-wip-us.apache.

[jira] [Commented] (DL-122) Use assertions from Junit rather than assert() for tests

[ https://issues.apache.org/jira/browse/DL-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763399#comment-15763399 ] ASF GitHub Bot commented on DL-122: --- Github user asfgit closed the pull request at: htt

[GitHub] incubator-distributedlog pull request #77: DL-122: Use assertions from Junit...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-distributedlog/pull/77 --- 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 th

incubator-distributedlog git commit: DL-122: Use assertions from Junit rather than assert() for tests

Repository: incubator-distributedlog Updated Branches: refs/heads/master dadd59220 -> 306a2a97c DL-122: Use assertions from Junit rather than assert() for tests * changed all instances of `assert()` to junit versions in `src/test` Here is the script I used to find all instances of `assert()`

[GitHub] incubator-distributedlog pull request #75: DL-123: Every tests should have t...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-distributedlog/pull/75 --- 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 th

[jira] [Commented] (DL-123) Every tests should have timeout

[ https://issues.apache.org/jira/browse/DL-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763394#comment-15763394 ] ASF GitHub Bot commented on DL-123: --- Github user asfgit closed the pull request at: htt

[jira] [Commented] (DL-136) Avoid empty catch blocks

[ https://issues.apache.org/jira/browse/DL-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763391#comment-15763391 ] ASF GitHub Bot commented on DL-136: --- Github user asfgit closed the pull request at: htt

incubator-distributedlog git commit: DL-123: Every tests should have timeout

Repository: incubator-distributedlog Updated Branches: refs/heads/master deb8d3755 -> dadd59220 DL-123: Every tests should have timeout * used a simple bash script to find any tests without a timeout Here is the below bash executed from the root directory. This could be expanded to take in m

[GitHub] incubator-distributedlog pull request #74: DL-136: Avoid empty catch blocks

Github user asfgit closed the pull request at: https://github.com/apache/incubator-distributedlog/pull/74 --- 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 th

incubator-distributedlog git commit: DL-136: Avoid empty catch blocks

Repository: incubator-distributedlog Updated Branches: refs/heads/master 53f7b5821 -> deb8d3755 DL-136: Avoid empty catch blocks * resolves the 9 empty catch blocks in `src/main` * leaves 49 errors within `src/test` unchanged * if we want to resolve those as well let me know, wasn't sure how

[jira] [Commented] (DL-136) Avoid empty catch blocks

[ https://issues.apache.org/jira/browse/DL-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763387#comment-15763387 ] ASF GitHub Bot commented on DL-136: --- Github user sijie commented on the issue: https://

[GitHub] incubator-distributedlog issue #74: DL-136: Avoid empty catch blocks

Github user sijie commented on the issue: https://github.com/apache/incubator-distributedlog/pull/74 The change looks good to me +1 @brennonyork thank you for your contribution. --- If your project is set up for it, you can reply to this email and have your reply appear on G

[result] [discuss] Official Slack or Gitter channel for Distributedlog

To conclude this thread: 7 +1 for Slack 3 +1 for either Slack or Gitter 0 -1 So I think we will go for Slack. Can any IPMC member help on setting this or point me any links on how to set this up? Sijie On Dec 19, 2016 9:52 AM, "Arun Khetarpal" wrote: > +1 for Slack > > On 19-Dec-2016, at 10:

Re: Hello

Thanks a lot. I’ll try building the code myself today. Regards, Arun > On 19-Dec-2016, at 12:44 AM, Asko Kauppi wrote: > > Hi Arun, > > I am also a newcomer to DistributedLog, and spent some time reading the > documentation. I'd like to share some tips with you, to hopefully make your > jour

Re: [discuss] Official Slack or Gitter channel for Distributedlog

+1 for Slack > On 19-Dec-2016, at 10:06 PM, Gerrit Sundaram wrote: > > +1 for Slack > > On Thu, Dec 15, 2016 at 9:59 AM, Asko Kauppi wrote: > >> Either works for me, too. >> >>> On 14 Dec 2016, at 10.32, Stevo Slavić wrote: >>> >>> Either works for me, as long as it's documented in project

Re: [discuss] Official Slack or Gitter channel for Distributedlog

Either works for me. - KN On Thu, Dec 15, 2016 at 9:59 AM, Asko Kauppi wrote: > Either works for me, too. > > > On 14 Dec 2016, at 10.32, Stevo Slavić wrote: > > > > Either works for me, as long as it's documented in project website and > > readme file. > >

Re: [discuss] Official Slack or Gitter channel for Distributedlog

+1 for Slack On Thu, Dec 15, 2016 at 9:59 AM, Asko Kauppi wrote: > Either works for me, too. > > > On 14 Dec 2016, at 10.32, Stevo Slavić wrote: > > > > Either works for me, as long as it's documented in project website and > > readme file. > >

Re: [Discuss] Transaction Support

Thanks liang. - Xi On Sun, Dec 18, 2016 at 5:52 PM, liang xie wrote: > The developers upload the design doc onto JIRA at least for > HADOOP/HBase/Cassandra/... projects > > On Mon, Dec 19, 2016 at 12:48 AM, Sijie Guo wrote: > > Hi Xi, > > > > sorry for late response. I will review it soon. > >

Re: [Discuss] Transaction Support

Sijie, No. I thought it might be easier for people to comment on a google doc to gather the initial feedback. I will put the content back to wiki page once addressing the comments. Does that sound good to you? And thank you in advance. - Xi On Sun, Dec 18, 2016 at 8:48 AM, Sijie Guo wrote: