[jira] [Updated] (MNEMONIC-105) Add a set of testcases for Durable Map
[ https://issues.apache.org/jira/browse/MNEMONIC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wen tong updated MNEMONIC-105: -- Due Date: 5/Sep/16 (was: 31/Aug/16) > Add a set of testcases for Durable Map > -- > > Key: MNEMONIC-105 > URL: https://issues.apache.org/jira/browse/MNEMONIC-105 > Project: Mnemonic > Issue Type: New Feature > Components: Collection >Affects Versions: 0.3.0-incubating >Reporter: Wang, Gang > Fix For: 0.3.0-incubating > > > Verify all functionalities of Durable Map -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: welcome new developers to Mnemonic project
Welcome! On Wed, Aug 31, 2016 at 8:47 PM, xiaomin song wrote: > Hi Yanping/Developers, > > I am Xiaomin Song and I work for Intel. I am interested in software > development and would like to contribute to Apache Mnemonic project. I am > looking forward to be a committer in the future. Thanks! > > Regards, > Xiaomin Song > Intel Corp. > > > On Wed, Aug 24, 2016 at 10:36 AM, Yanping Wang wrote: > > > Hi, Dev > > > > I am glad to see we had new developers joined us recently and started > > working on some JIRAs. > > > > It would be great if new developers can introduce themselves to our PPMC > > members, such as a short background, interests, and affiliation, etc > > > > again welcome and thanks > > > > yanping > > >
[jira] [Updated] (MNEMONIC-103) Durable native sorting service testcases
[ https://issues.apache.org/jira/browse/MNEMONIC-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaomin Song updated MNEMONIC-103: -- Due Date: 2/Sep/16 (was: 31/Aug/16) > Durable native sorting service testcases > > > Key: MNEMONIC-103 > URL: https://issues.apache.org/jira/browse/MNEMONIC-103 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service >Affects Versions: 0.3.0-incubating >Reporter: Wang, Gang >Assignee: Xiaomin Song > Fix For: 0.3.0-incubating > > > Add testcases to verify the functionalities of Durable native sorting service > (MNEMONIC-94) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNEMONIC-103) Durable native sorting service testcases
[ https://issues.apache.org/jira/browse/MNEMONIC-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaomin Song updated MNEMONIC-103: -- Due Date: 4/Sep/16 (was: 2/Sep/16) > Durable native sorting service testcases > > > Key: MNEMONIC-103 > URL: https://issues.apache.org/jira/browse/MNEMONIC-103 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service >Affects Versions: 0.3.0-incubating >Reporter: Wang, Gang >Assignee: Xiaomin Song > Fix For: 0.3.0-incubating > > > Add testcases to verify the functionalities of Durable native sorting service > (MNEMONIC-94) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: welcome new developers to Mnemonic project
Hi Yanping/Developers, I am Xiaomin Song and I work for Intel. I am interested in software development and would like to contribute to Apache Mnemonic project. I am looking forward to be a committer in the future. Thanks! Regards, Xiaomin Song Intel Corp. On Wed, Aug 24, 2016 at 10:36 AM, Yanping Wang wrote: > Hi, Dev > > I am glad to see we had new developers joined us recently and started > working on some JIRAs. > > It would be great if new developers can introduce themselves to our PPMC > members, such as a short background, interests, and affiliation, etc > > again welcome and thanks > > yanping >
[jira] [Updated] (MNEMONIC-109) Create a testcase to manage durable object on volatile memory service
[ https://issues.apache.org/jira/browse/MNEMONIC-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang, Gang updated MNEMONIC-109: Assignee: Chenyang Li > Create a testcase to manage durable object on volatile memory service > - > > Key: MNEMONIC-109 > URL: https://issues.apache.org/jira/browse/MNEMONIC-109 > Project: Mnemonic > Issue Type: Task > Components: Core >Affects Versions: 0.3.0-incubating >Reporter: Wang, Gang >Assignee: Chenyang Li > Fix For: 0.3.0-incubating > > > Please refer to the code of DurablePersonNGTest.java for this case -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNEMONIC-109) Create a testcase to manage durable object on volatile memory service
Wang, Gang created MNEMONIC-109: --- Summary: Create a testcase to manage durable object on volatile memory service Key: MNEMONIC-109 URL: https://issues.apache.org/jira/browse/MNEMONIC-109 Project: Mnemonic Issue Type: Task Components: Core Affects Versions: 0.3.0-incubating Reporter: Wang, Gang Fix For: 0.3.0-incubating Please refer to the code of DurablePersonNGTest.java for this case -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNEMONIC-60) Apply Transaction, Retrievable interfaces to class VolatileMemAllocator
[ https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang, Gang closed MNEMONIC-60. -- Resolution: Fixed > Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > --- > > Key: MNEMONIC-60 > URL: https://issues.apache.org/jira/browse/MNEMONIC-60 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service, Core >Affects Versions: 0.2.0-incubating >Reporter: Wang, Gang >Assignee: Chenyang Li > Fix For: 0.3.0-incubating > > > The current implementation of class VolatileMemAllocator does not support > retrieval operations so it is not possible to temporarily forget cached > durable objects efficiently like class NonVolatileMemAllocator does, > logically, volatile memory should be retrievable for durable object graphs in > a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, > therefore the VolatileMemAllocator should implement retrievable interface to > support forgettable object graphs and durable native computing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNEMONIC-96) Verify the functionalities on latest version of nvml
[ https://issues.apache.org/jira/browse/MNEMONIC-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang, Gang closed MNEMONIC-96. -- Resolution: Fixed > Verify the functionalities on latest version of nvml > > > Key: MNEMONIC-96 > URL: https://issues.apache.org/jira/browse/MNEMONIC-96 > Project: Mnemonic > Issue Type: Task > Components: Memory-Service >Affects Versions: 0.3.0-incubating >Reporter: Wang, Gang >Assignee: Yanhui Zhao > Fix For: 0.3.0-incubating > > > The nvml is one of memory service allocator, this task verifies the > functionalities along with the latest release of nvml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNEMONIC-60) Apply Transaction, Retrievable interfaces to class VolatileMemAllocator
[ https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453733#comment-15453733 ] ASF GitHub Bot commented on MNEMONIC-60: Github user lcy0816 closed the pull request at: https://github.com/apache/incubator-mnemonic/pull/19 > Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > --- > > Key: MNEMONIC-60 > URL: https://issues.apache.org/jira/browse/MNEMONIC-60 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service, Core >Affects Versions: 0.2.0-incubating >Reporter: Wang, Gang >Assignee: Chenyang Li > Fix For: 0.3.0-incubating > > > The current implementation of class VolatileMemAllocator does not support > retrieval operations so it is not possible to temporarily forget cached > durable objects efficiently like class NonVolatileMemAllocator does, > logically, volatile memory should be retrievable for durable object graphs in > a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, > therefore the VolatileMemAllocator should implement retrievable interface to > support forgettable object graphs and durable native computing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-mnemonic pull request #19: MNEMONIC-60:Apply Transaction, Retrieva...
Github user lcy0816 closed the pull request at: https://github.com/apache/incubator-mnemonic/pull/19 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (MNEMONIC-60) Apply Transaction, Retrievable interfaces to class VolatileMemAllocator
[ https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453731#comment-15453731 ] ASF GitHub Bot commented on MNEMONIC-60: GitHub user lcy0816 opened a pull request: https://github.com/apache/incubator-mnemonic/pull/19 MNEMONIC-60:Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > The current implementation of class VolatileMemAllocator does not support retrieval operations so it is not possible to temporarily forget cached durable objects efficiently like class NonVolatileMemAllocator does, logically, volatile memory should be retrievable for durable object graphs in a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, therefore the VolatileMemAllocator should implement retrievable interface to support forgettable object graphs and durable native computing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/lcy0816/incubator-mnemonic master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-mnemonic/pull/19.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #19 commit d0975c9f16c9928582c77b90f24a78b24f6282d8 Author: lcy0816 Date: 2016-08-31T23:34:36Z MNEMONIC-60:Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > --- > > Key: MNEMONIC-60 > URL: https://issues.apache.org/jira/browse/MNEMONIC-60 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service, Core >Affects Versions: 0.2.0-incubating >Reporter: Wang, Gang >Assignee: Chenyang Li > Fix For: 0.3.0-incubating > > > The current implementation of class VolatileMemAllocator does not support > retrieval operations so it is not possible to temporarily forget cached > durable objects efficiently like class NonVolatileMemAllocator does, > logically, volatile memory should be retrievable for durable object graphs in > a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, > therefore the VolatileMemAllocator should implement retrievable interface to > support forgettable object graphs and durable native computing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-mnemonic pull request #19: MNEMONIC-60:Apply Transaction, Retrieva...
GitHub user lcy0816 opened a pull request: https://github.com/apache/incubator-mnemonic/pull/19 MNEMONIC-60:Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > The current implementation of class VolatileMemAllocator does not support retrieval operations so it is not possible to temporarily forget cached durable objects efficiently like class NonVolatileMemAllocator does, logically, volatile memory should be retrievable for durable object graphs in a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, therefore the VolatileMemAllocator should implement retrievable interface to support forgettable object graphs and durable native computing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/lcy0816/incubator-mnemonic master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-mnemonic/pull/19.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #19 commit d0975c9f16c9928582c77b90f24a78b24f6282d8 Author: lcy0816 Date: 2016-08-31T23:34:36Z MNEMONIC-60:Apply Transaction, Retrievable interfaces to class VolatileMemAllocator --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (MNEMONIC-60) Apply Transaction, Retrievable interfaces to class VolatileMemAllocator
[ https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453475#comment-15453475 ] ASF GitHub Bot commented on MNEMONIC-60: Github user lcy0816 closed the pull request at: https://github.com/apache/incubator-mnemonic/pull/18 > Apply Transaction, Retrievable interfaces to class VolatileMemAllocator > --- > > Key: MNEMONIC-60 > URL: https://issues.apache.org/jira/browse/MNEMONIC-60 > Project: Mnemonic > Issue Type: New Feature > Components: Computing-Service, Core >Affects Versions: 0.2.0-incubating >Reporter: Wang, Gang >Assignee: Chenyang Li > Fix For: 0.3.0-incubating > > > The current implementation of class VolatileMemAllocator does not support > retrieval operations so it is not possible to temporarily forget cached > durable objects efficiently like class NonVolatileMemAllocator does, > logically, volatile memory should be retrievable for durable object graphs in > a applications/frameworks run-time session. > In addition, durable native computing must based on retrievable interface, > therefore the VolatileMemAllocator should implement retrievable interface to > support forgettable object graphs and durable native computing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-mnemonic pull request #18: MNEMONIC-60:Apply Transaction, Retrieva...
Github user lcy0816 closed the pull request at: https://github.com/apache/incubator-mnemonic/pull/18 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (MNEMONIC-108) Compose a dockerfile for website dev.
Wang, Gang created MNEMONIC-108: --- Summary: Compose a dockerfile for website dev. Key: MNEMONIC-108 URL: https://issues.apache.org/jira/browse/MNEMONIC-108 Project: Mnemonic Issue Type: New Feature Components: Website Affects Versions: 0.3.0-incubating Reporter: Wang, Gang Fix For: 0.3.0-incubating Create a dockerfile to facilitate website development -- This message was sent by Atlassian JIRA (v6.3.4#6332)
