[jira] [Commented] (MNEMONIC-387) Compilation error in mnemonic-computing-services module

2017-10-26 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221730#comment-16221730
 ] 

ASF GitHub Bot commented on MNEMONIC-387:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/77


> Compilation error in mnemonic-computing-services module
> ---
>
> Key: MNEMONIC-387
> URL: https://issues.apache.org/jira/browse/MNEMONIC-387
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Computing-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Johnu George
>Assignee: Yanhui Zhao
> Fix For: 0.10.0-incubating
>
>
> Below is the compilation error desc
>  
>  [exec]   vectorIterTensor(env, nvinfo, dims, itmaddrs, , 
> , hdls, -1, chk_addr, dc_size, , count);
>  [exec]   ^
>  [exec] 
> /Users/johnugeorge/work/incubator-mnemonic/mnemonic-computing-services/mnemonic-utilities-service/src/main/native/common.c:417:6:
>  error: conflicting types for 'vectorIterTensor'
>  [exec] void vectorIterTensor(JNIEnv* env, struct NValueInfo *nvinfo,
>  [exec]  ^
>  [exec] 
> /Users/johnugeorge/work/incubator-mnemonic/mnemonic-computing-services/mnemonic-utilities-service/src/main/native/common.c:413:3:
>  note: previous implicit declaration is here
>  [exec]   vectorIterTensor(env, nvinfo, dims, itmaddrs, , 
> , hdls, -1, chk_addr, dc_size, , count);
>  [exec]   ^
>  [exec] 1 warning and 1 error generated.
>  [exec] make[2]: *** [CMakeFiles/utilitiescomputing.dir/common.c.o] Error 
> 1
>  [exec] make[1]: *** [CMakeFiles/utilitiescomputing.dir/all] Error 2
>  [exec] make: *** [all] Error 2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-275) Implement a default function to sync data to the persistent storage

2017-10-22 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214355#comment-16214355
 ] 

ASF GitHub Bot commented on MNEMONIC-275:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/76


> Implement a default function to sync data to the persistent storage
> ---
>
> Key: MNEMONIC-275
> URL: https://issues.apache.org/jira/browse/MNEMONIC-275
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Jie Liu
> Fix For: 0.9.0-incubating
>
>
> # Currently persist(), sync(), flush() calls are exposed to the user. This is 
> confusing.  Only one call should be exposed to user that provides the default 
> functionality. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-275) Implement a default function to sync data to the persistent storage

2017-10-21 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214147#comment-16214147
 ] 

ASF GitHub Bot commented on MNEMONIC-275:
-

GitHub user liujielj opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/76

MNEMONIC-275 Implement a default function to sync data to the persisent 
storage

Currently persist(), sync(), flush() calls are exposed to the user. This is 
confusing.  Only one call should be exposed to user that provides the default 
functionality. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/liujielj/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/76.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 #76


commit 9cd39fc93591fb505cf99df1318d9b6b50be18be
Author: Jie Liu 
Date:   2017-10-21T22:54:55Z

MNEMONIC-275 Implement a default function to sync data to the persistent 
storage




> Implement a default function to sync data to the persistent storage
> ---
>
> Key: MNEMONIC-275
> URL: https://issues.apache.org/jira/browse/MNEMONIC-275
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Jie Liu
> Fix For: 0.9.0-incubating
>
>
> # Currently persist(), sync(), flush() calls are exposed to the user. This is 
> confusing.  Only one call should be exposed to user that provides the default 
> functionality. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-387) Compilation error in mnemonic-computing-services module

2017-10-15 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205453#comment-16205453
 ] 

ASF GitHub Bot commented on MNEMONIC-387:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/75

MNEMONIC-387 Compilation error in mnemonic-computing-services module

Fixed an issue of function parameter mismatch.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/75.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 #75


commit bf39c43c981c7a8d4019cf63b52d00cf3e7795b5
Author: Yanhui Zhao 
Date:   2017-10-16T05:36:05Z

MNEMONIC-387 Compilation error in mnemonic-computing-services module




> Compilation error in mnemonic-computing-services module
> ---
>
> Key: MNEMONIC-387
> URL: https://issues.apache.org/jira/browse/MNEMONIC-387
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Computing-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Johnu George
>Assignee: Yanhui Zhao
> Fix For: 0.10.0-incubating
>
>
> Below is the compilation error desc
>  
>  [exec]   vectorIterTensor(env, nvinfo, dims, itmaddrs, , 
> , hdls, -1, chk_addr, dc_size, , count);
>  [exec]   ^
>  [exec] 
> /Users/johnugeorge/work/incubator-mnemonic/mnemonic-computing-services/mnemonic-utilities-service/src/main/native/common.c:417:6:
>  error: conflicting types for 'vectorIterTensor'
>  [exec] void vectorIterTensor(JNIEnv* env, struct NValueInfo *nvinfo,
>  [exec]  ^
>  [exec] 
> /Users/johnugeorge/work/incubator-mnemonic/mnemonic-computing-services/mnemonic-utilities-service/src/main/native/common.c:413:3:
>  note: previous implicit declaration is here
>  [exec]   vectorIterTensor(env, nvinfo, dims, itmaddrs, , 
> , hdls, -1, chk_addr, dc_size, , count);
>  [exec]   ^
>  [exec] 1 warning and 1 error generated.
>  [exec] make[2]: *** [CMakeFiles/utilitiescomputing.dir/common.c.o] Error 
> 1
>  [exec] make[1]: *** [CMakeFiles/utilitiescomputing.dir/all] Error 2
>  [exec] make: *** [all] Error 2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-376) Support shrinkable durable memory service

2017-10-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198189#comment-16198189
 ] 

ASF GitHub Bot commented on MNEMONIC-376:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/74


> Support shrinkable durable memory service 
> --
>
> Key: MNEMONIC-376
> URL: https://issues.apache.org/jira/browse/MNEMONIC-376
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.10.0-incubating
>
>
> The shrinkable feature would be required if we want to transfer durable 
> objects to remote nodes.  The user cannot predict how much space they need so 
> there must be some free space is not necessary to be transferred. the 
> shrinkable memory service also needs to handle the change of capacity 
> underlying.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-376) Support shrinkable durable memory service

2017-10-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197197#comment-16197197
 ] 

ASF GitHub Bot commented on MNEMONIC-376:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/74#discussion_r143510796
  
--- Diff: 
mnemonic-core/src/main/java/org/apache/mnemonic/VolatileMemAllocator.java ---
@@ -158,6 +159,19 @@ public long expand(long size) {
 return ret;
   }
 
+  @Override
+  public long shrink(long size) {
+long ret = 0L;
+if (null != m_features) {
+  if (m_features.contains(SHRINKABLE)) {
+return m_vmasvc.adjustCapacity(m_nid, (-1) * size);
--- End diff --

Please assign the result to ret variable


> Support shrinkable durable memory service 
> --
>
> Key: MNEMONIC-376
> URL: https://issues.apache.org/jira/browse/MNEMONIC-376
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
>
> The shrinkable feature would be required if we want to transfer durable 
> objects to remote nodes.  The user cannot predict how much space they need so 
> there must be some free space is not necessary to be transferred. the 
> shrinkable memory service also needs to handle the change of capacity 
> underlying.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-376) Support shrinkable durable memory service

2017-10-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197196#comment-16197196
 ] 

ASF GitHub Bot commented on MNEMONIC-376:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/74#discussion_r143510963
  
--- Diff: 
mnemonic-core/src/main/java/org/apache/mnemonic/VolatileMemAllocator.java ---
@@ -158,6 +159,19 @@ public long expand(long size) {
 return ret;
   }
 
+  @Override
+  public long shrink(long size) {
+long ret = 0L;
+if (null != m_features) {
+  if (m_features.contains(SHRINKABLE)) {
--- End diff --

Please add an else branch for this if statement.


> Support shrinkable durable memory service 
> --
>
> Key: MNEMONIC-376
> URL: https://issues.apache.org/jira/browse/MNEMONIC-376
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
>
> The shrinkable feature would be required if we want to transfer durable 
> objects to remote nodes.  The user cannot predict how much space they need so 
> there must be some free space is not necessary to be transferred. the 
> shrinkable memory service also needs to handle the change of capacity 
> underlying.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-376) Support shrinkable durable memory service

2017-10-07 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16195980#comment-16195980
 ] 

ASF GitHub Bot commented on MNEMONIC-376:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/74

MNEMONIC-376: Support shrinkable durable memory service

MNEMONIC-376: Support shrinkable durable memory service

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/74.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 #74


commit 2da83bb190f5f92e5a106c81e3da96df600fb101
Author: paleyss 
Date:   2017-10-08T05:48:36Z

MNEMONIC-376: Support shrinkable durable memory service




> Support shrinkable durable memory service 
> --
>
> Key: MNEMONIC-376
> URL: https://issues.apache.org/jira/browse/MNEMONIC-376
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
>
> The shrinkable feature would be required if we want to transfer durable 
> objects to remote nodes.  The user cannot predict how much space they need so 
> there must be some free space is not necessary to be transferred. the 
> shrinkable memory service also needs to handle the change of capacity 
> underlying.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-321) Implement Java method for durable object vectorization

2017-10-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190900#comment-16190900
 ] 

ASF GitHub Bot commented on MNEMONIC-321:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/73


> Implement Java method for durable object vectorization
> --
>
> Key: MNEMONIC-321
> URL: https://issues.apache.org/jira/browse/MNEMONIC-321
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Computing-Service
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>
> This is one of the sub-tasks under MNEMONIC issue 307 durable object 
> vectorization. This sub-task focuses on the implementation of the Java method 
> for durable object vectorization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-321) Implement Java method for durable object vectorization

2017-10-02 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189297#comment-16189297
 ] 

ASF GitHub Bot commented on MNEMONIC-321:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/73#discussion_r142317858
  
--- Diff: 
mnemonic-computing-services/mnemonic-utilities-service/src/main/java/org/apache/mnemonic/service/computing/internal/PrintServiceImpl.java
 ---
@@ -50,6 +50,11 @@ public String getServiceId() {
 return ret;
   }
 
+  @Override
+  public long[] perform(String mode, ValueInfo[] valinfos, long dcHandler, 
long dcSize) {
+return null;
--- End diff --

It is better to throw UnsupportedOperationException please,


> Implement Java method for durable object vectorization
> --
>
> Key: MNEMONIC-321
> URL: https://issues.apache.org/jira/browse/MNEMONIC-321
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Computing-Service
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>
> This is one of the sub-tasks under MNEMONIC issue 307 durable object 
> vectorization. This sub-task focuses on the implementation of the Java method 
> for durable object vectorization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-321) Implement Java method for durable object vectorization

2017-10-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187562#comment-16187562
 ] 

ASF GitHub Bot commented on MNEMONIC-321:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/73

MNEMONIC-321 Implement Java method for durable object vectorization

This is one of the sub-tasks under MNEMONIC issue 307 durable object 
vectorization. This sub-task focuses on the implementation of the Java method 
for durable object vectorization.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/73.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 #73


commit 6be0417ba3657a8d36692f22b56c123b3dda07f1
Author: Yanhui Zhao 
Date:   2017-10-01T22:20:19Z

MNEMONIC-321 Implement Java method for durable object vectorization




> Implement Java method for durable object vectorization
> --
>
> Key: MNEMONIC-321
> URL: https://issues.apache.org/jira/browse/MNEMONIC-321
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Computing-Service
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>
> This is one of the sub-tasks under MNEMONIC issue 307 durable object 
> vectorization. This sub-task focuses on the implementation of the Java method 
> for durable object vectorization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-375) Support expandable durable memory service

2017-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187286#comment-16187286
 ] 

ASF GitHub Bot commented on MNEMONIC-375:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/72


> Support expandable durable memory service
> -
>
> Key: MNEMONIC-375
> URL: https://issues.apache.org/jira/browse/MNEMONIC-375
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
>
> Fixed memory service does not allow to expand its capacity so it is not very 
> convenient for some applications. so it is necessary to support expandable 
> memory service, but this kind of expandable memory services need FS-like 
> mechanism to make it expandable. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-375) Support expandable durable memory service

2017-09-30 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16186911#comment-16186911
 ] 

ASF GitHub Bot commented on MNEMONIC-375:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/72

MNEMONIC-375: Support expandable durable memory service

MNEMONIC-375: Support expandable durable memory service

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/72.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 #72


commit c2ff608b98ae6a8637a8e76463641cedd96f2f24
Author: paleyss 
Date:   2017-09-30T06:02:17Z

MNEMONIC-375: Support expandable durable memory service




> Support expandable durable memory service
> -
>
> Key: MNEMONIC-375
> URL: https://issues.apache.org/jira/browse/MNEMONIC-375
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Memory-Service
>Affects Versions: 0.10.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
>
> Fixed memory service does not allow to expand its capacity so it is not very 
> convenient for some applications. so it is necessary to support expandable 
> memory service, but this kind of expandable memory services need FS-like 
> mechanism to make it expandable. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-344) The error message is not correct for failing test case

2017-09-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172827#comment-16172827
 ] 

ASF GitHub Bot commented on MNEMONIC-344:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/68


> The error message is not correct for failing test case 
> ---
>
> Key: MNEMONIC-344
> URL: https://issues.apache.org/jira/browse/MNEMONIC-344
> Project: Mnemonic
>  Issue Type: Bug
>  Components: TestCase, Tools
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wei
>
> Please show "[ERROR] this test case failed, please refer to " instead of 
> "[ERROR] This test case requires \"pmalloc\" memory service to pass, ..." in 
> runTestCases.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-320) Implement native method for durable object vectorization

2017-09-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172345#comment-16172345
 ] 

ASF GitHub Bot commented on MNEMONIC-320:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/71


> Implement native method for durable object vectorization
> 
>
> Key: MNEMONIC-320
> URL: https://issues.apache.org/jira/browse/MNEMONIC-320
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Computing-Service
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>
> This is one of the sub-tasks for MNEMONIC issue 307 Durable Object 
> Vectorization. This sub-task focuses on the implementation of the native 
> method for durable object vectorization. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-371) Add README.md for the project mnemonic-examples

2017-09-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171177#comment-16171177
 ] 

ASF GitHub Bot commented on MNEMONIC-371:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/70


> Add README.md for the project mnemonic-examples
> ---
>
> Key: MNEMONIC-371
> URL: https://issues.apache.org/jira/browse/MNEMONIC-371
> Project: Mnemonic
>  Issue Type: Task
>Reporter: Ganhua Zhang
>Assignee: Ganhua Zhang
>Priority: Minor
>
> Add README.md for the project mnemonic-examples to describe how to run 
> examples in this project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-371) Add README.md for the project mnemonic-examples

2017-09-18 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171029#comment-16171029
 ] 

ASF GitHub Bot commented on MNEMONIC-371:
-

GitHub user jerryZh65 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/70

MNEMONIC-371: Add README.md for the project "mnemonic-examples"



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jerryZh65/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/70.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 #70


commit bc033605c32083f64d312e4daff082fc00738b09
Author: Ganhuazhang 
Date:   2017-09-19T02:19:50Z

MNEMONIC-371: Add README.md for the project mnemonic-examples




> Add README.md for the project mnemonic-examples
> ---
>
> Key: MNEMONIC-371
> URL: https://issues.apache.org/jira/browse/MNEMONIC-371
> Project: Mnemonic
>  Issue Type: Task
>Reporter: Ganhua Zhang
>Assignee: Ganhua Zhang
>Priority: Minor
>
> Add README.md for the project mnemonic-examples to describe how to run 
> examples in this project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-343) Add a switch option to select specific example to run

2017-09-15 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167436#comment-16167436
 ] 

ASF GitHub Bot commented on MNEMONIC-343:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/69


> Add a switch option to select specific example to run
> -
>
> Key: MNEMONIC-343
> URL: https://issues.apache.org/jira/browse/MNEMONIC-343
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Example
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Ganhua Zhang
>
> The switch option is used for the user to run the different example in one 
> example application. 
> {code:none}
> $ mvn exec:exec -Pexample -pl mnemonic-examples   parameters>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-343) Add a switch option to select specific example to run

2017-09-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167335#comment-16167335
 ] 

ASF GitHub Bot commented on MNEMONIC-343:
-

GitHub user jerryZh65 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/69

MNEMONIC-343: Add a switch option to select specific example to run



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jerryZh65/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/69.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 #69


commit b938c46323e18378ee84120c406c3cdcb0e2285f
Author: Ganhuazhang 
Date:   2017-09-15T05:13:33Z

MNEMONIC-343: Add a switch option to select specific example to run




> Add a switch option to select specific example to run
> -
>
> Key: MNEMONIC-343
> URL: https://issues.apache.org/jira/browse/MNEMONIC-343
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Example
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Ganhua Zhang
>
> The switch option is used for the user to run the different example in one 
> example application. 
> {code:none}
> $ mvn exec:exec -Pexample -pl mnemonic-examples   parameters>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

2017-09-11 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162514#comment-16162514
 ] 

ASF GitHub Bot commented on MNEMONIC-304:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/66


> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-344) The error message is not correct for failing test case

2017-09-11 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162478#comment-16162478
 ] 

ASF GitHub Bot commented on MNEMONIC-344:
-

GitHub user weiho1122 reopened a pull request:

https://github.com/apache/incubator-mnemonic/pull/68

MNEMONIC-344: The error message is not correct for failing test case



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/weiho1122/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/68.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 #68


commit d13ca34e57ffbd21d437cf7f183810e04132f2b2
Author: weiho1122 
Date:   2017-09-12T04:24:18Z

MNEMONIC-344: The error message is not correct for failing test case




> The error message is not correct for failing test case 
> ---
>
> Key: MNEMONIC-344
> URL: https://issues.apache.org/jira/browse/MNEMONIC-344
> Project: Mnemonic
>  Issue Type: Bug
>  Components: TestCase, Tools
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wei
>
> Please show "[ERROR] this test case failed, please refer to " instead of 
> "[ERROR] This test case requires \"pmalloc\" memory service to pass, ..." in 
> runTestCases.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-344) The error message is not correct for failing test case

2017-09-11 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162476#comment-16162476
 ] 

ASF GitHub Bot commented on MNEMONIC-344:
-

Github user weiho1122 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/68


> The error message is not correct for failing test case 
> ---
>
> Key: MNEMONIC-344
> URL: https://issues.apache.org/jira/browse/MNEMONIC-344
> Project: Mnemonic
>  Issue Type: Bug
>  Components: TestCase, Tools
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Wei
>
> Please show "[ERROR] this test case failed, please refer to " instead of 
> "[ERROR] This test case requires \"pmalloc\" memory service to pass, ..." in 
> runTestCases.py



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-364) Add GPG failure handling in release script

2017-09-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151188#comment-16151188
 ] 

ASF GitHub Bot commented on MNEMONIC-364:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/67


> Add GPG failure handling in release script
> --
>
> Key: MNEMONIC-364
> URL: https://issues.apache.org/jira/browse/MNEMONIC-364
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Release
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> Handle GPG failure conditions  in release script.  The release script should 
> exit without proceeding if GPG fails



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

2017-09-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150963#comment-16150963
 ] 

ASF GitHub Bot commented on MNEMONIC-304:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/66#discussion_r136635894
  
--- Diff: 
mnemonic-core/src/main/java/org/apache/mnemonic/ParameterHolder.java ---
@@ -105,4 +114,20 @@ public void setHandler(long h) {
 public long getHandler() {
 return handler;
 }
+
+public void setGenericTypeAndEntityFactoryProxyPair(DurableType[] d, 
EntityFactoryProxy[] e) {
+dpt = new ImmutablePair(d, e);
+}
+
+public DurableType[] getGenericTypeFromPair() {
+return dpt.getLeft();
+}
+
+public EntityFactoryProxy[] getEntityFactoryProxyFromPair() {
--- End diff --

ditto


> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-361) Fails to generate Javadocs

2017-08-31 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149338#comment-16149338
 ] 

ASF GitHub Bot commented on MNEMONIC-361:
-

GitHub user bigdata-memory opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/64

Fixed MNEMONIC-361: Fails to generate Javadocs

Added required comments and removed an unexpected character.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/NonVolatileComputing/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/64.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 #64


commit 43b57b67ef19dcaf52fbf929efd071ba75a5add3
Author: Wang, Gang(Gary) 
Date:   2017-08-31T17:47:24Z

MNEMONIC-361: Fails to generate Javadocs




> Fails to generate Javadocs
> --
>
> Key: MNEMONIC-361
> URL: https://issues.apache.org/jira/browse/MNEMONIC-361
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs) on 
> project mnemonic-core: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/Allocator.java:36:
>  warning: no @param for addr
> [ERROR] void sync(long addr, long length, boolean autodetect);
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/Allocator.java:36:
>  warning: no @param for length
> [ERROR] void sync(long addr, long length, boolean autodetect);
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/Allocator.java:36:
>  warning: no @param for autodetect
> [ERROR] void sync(long addr, long length, boolean autodetect);
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/NonVolatileMemAllocator.java:613:
>  error: @param name not found
> [ERROR] * @param readOnly
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/SysMemAllocator.java:154:
>  warning: no description for @param
> [ERROR] * @param addr
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/SysMemAllocator.java:155:
>  warning: no description for @param
> [ERROR] * @param length
> [ERROR] ^
> [ERROR] 
> /ws/release/incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/SysMemAllocator.java:156:
>  warning: no description for @param
> [ERROR] * @param autodetect
> [ERROR] ^
> [ERROR] 
> [ERROR] Command line was: 
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.141-1.b16.el7_3.x86_64/jre/../bin/javadoc
>  @options @packages
> [ERROR] 
> [ERROR] Refer to the generated Javadoc files in 
> '/ws/release/incubator-mnemonic/mnemonic-core/target/apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

2017-08-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146613#comment-16146613
 ] 

ASF GitHub Bot commented on MNEMONIC-304:
-

Github user yzz127 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/62


> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-359) add module to source-assembly file

2017-08-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146550#comment-16146550
 ] 

ASF GitHub Bot commented on MNEMONIC-359:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/63


> add module to source-assembly file
> --
>
> Key: MNEMONIC-359
> URL: https://issues.apache.org/jira/browse/MNEMONIC-359
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
> Fix For: 0.9.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-359) add module to source-assembly file

2017-08-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146542#comment-16146542
 ] 

ASF GitHub Bot commented on MNEMONIC-359:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/63

MNEMONIC-359: add module to source-assembly file

MNEMONIC-359: add module to source-assembly file

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/63.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 #63


commit 25c6b31b17ab5bf333b13d0a8ce91e2a7cee4f0b
Author: paleyss 
Date:   2017-08-30T03:31:17Z

MNEMONIC-359: add module to source-assembly file




> add module to source-assembly file
> --
>
> Key: MNEMONIC-359
> URL: https://issues.apache.org/jira/browse/MNEMONIC-359
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-304) Add support for Pair to ParameterHolder class to handle optional parameters

2017-08-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144732#comment-16144732
 ] 

ASF GitHub Bot commented on MNEMONIC-304:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/62

MNEMONIC-304 Add suppot for Pair to ParameterHolder class

Some test cases need to pass Pair as parameters when creating durable 
class. Current ParameterHolder class doesn't have the support for this feature.

Build is successful and test case passed after ParameterHolder class is 
updated. Please review and help to double check. Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/62.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 #62


commit c9812eec2e949d73540e6356bf1b091ef9c220d4
Author: Yanhui Zhao 
Date:   2017-08-29T04:28:04Z

MNEMONIC-304 Add suppot for Pair to ParameterHolder class




> Add support for Pair to ParameterHolder class to handle optional parameters
> ---
>
> Key: MNEMONIC-304
> URL: https://issues.apache.org/jira/browse/MNEMONIC-304
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
>  Labels: features
>
> Some test cases need to pass Pair as parameters when creating durable class. 
> Current ParameterHolder class doesn't have the support for this feature.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

2017-08-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144702#comment-16144702
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/61


> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

2017-08-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144691#comment-16144691
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

GitHub user yzz127 reopened a pull request:

https://github.com/apache/incubator-mnemonic/pull/61

MNEMONIC-353 Assign fixed version number to docker Centos build

Assign a version number instead of "latest" for docker Centos build for 
compatibility concerns.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/61.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 #61


commit 529ae4ea59d65d0a5002847449e2342ca1a40516
Author: Yanhui Zhao 
Date:   2017-08-27T03:24:09Z

MNEMONIC-353 Assign fixed version number to docker Centos build




> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

2017-08-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144690#comment-16144690
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

Github user yzz127 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/61


> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-353) Assign fixed version number to docker Centos build

2017-08-26 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142991#comment-16142991
 ] 

ASF GitHub Bot commented on MNEMONIC-353:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/61

MNEMONIC-353 Assign fixed version number to docker Centos build

Assign a version number instead of "latest" for docker Centos build for 
compatibility concerns.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/61.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 #61


commit 529ae4ea59d65d0a5002847449e2342ca1a40516
Author: Yanhui Zhao 
Date:   2017-08-27T03:24:09Z

MNEMONIC-353 Assign fixed version number to docker Centos build




> Assign fixed version number to docker Centos build
> --
>
> Key: MNEMONIC-353
> URL: https://issues.apache.org/jira/browse/MNEMONIC-353
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Assign a version number instead of "latest" for docker Centos build for 
> compatibility concerns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-348) Add test command to test configuration file

2017-08-25 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142092#comment-16142092
 ] 

ASF GitHub Bot commented on MNEMONIC-348:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/60


> Add test command to test configuration file
> ---
>
> Key: MNEMONIC-348
> URL: https://issues.apache.org/jira/browse/MNEMONIC-348
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>Priority: Minor
>
> Add test command to test configuration file



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-348) Add test command to test configuration file

2017-08-24 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141129#comment-16141129
 ] 

ASF GitHub Bot commented on MNEMONIC-348:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/60

MNEMONIC-348: Add test command to test configuration file

MNEMONIC-348: Add test command to test configuration file

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/60.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 #60


commit e733c7e7de7e46ede26abc80d9f9b7cd62b2b747
Author: paleyss 
Date:   2017-08-24T05:58:54Z

MNEMONIC-348: Add test command to test configuration file




> Add test command to test configuration file
> ---
>
> Key: MNEMONIC-348
> URL: https://issues.apache.org/jira/browse/MNEMONIC-348
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>Priority: Minor
>
> Add test command to test configuration file



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-299) implement Java based memory allocator

2017-08-23 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138859#comment-16138859
 ] 

ASF GitHub Bot commented on MNEMONIC-299:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/59


> implement Java based memory allocator
> -
>
> Key: MNEMONIC-299
> URL: https://issues.apache.org/jira/browse/MNEMONIC-299
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-299) implement Java based memory allocator

2017-08-23 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138000#comment-16138000
 ] 

ASF GitHub Bot commented on MNEMONIC-299:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/59

MNEMONIC-299 and MNEMONIC-300

MNEMONIC-300: add test cases for Java based volatile memory service
MNEMONIC-299: implement Java based memory allocator

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/59.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 #59


commit 7fb7ae02233db465605181c66fd4aad2e4342343
Author: paleyss 
Date:   2017-08-23T06:48:56Z

MNEMONIC-299: implement Java based memory allocator
MNEMONIC-300: add test cases for Java based volatile memory service




> implement Java based memory allocator
> -
>
> Key: MNEMONIC-299
> URL: https://issues.apache.org/jira/browse/MNEMONIC-299
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-332) The Logo in docker page deprecated

2017-08-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126001#comment-16126001
 ] 

ASF GitHub Bot commented on MNEMONIC-332:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/58


> The Logo in docker page deprecated
> --
>
> Key: MNEMONIC-332
> URL: https://issues.apache.org/jira/browse/MNEMONIC-332
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Ganhua Zhang
>Priority: Minor
>  Labels: documentation
>
> The logo link of docker page 
> ([https://github.com/apache/incubator-mnemonic/blob/master/docker/README.md]) 
> needs to be corrected referring to the project's README.md



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-332) The Logo in docker page deprecated

2017-08-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125314#comment-16125314
 ] 

ASF GitHub Bot commented on MNEMONIC-332:
-

GitHub user jerryZh65 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/58

MNEMONIC-332: The Logo in docker page deprecated

MNEMONIC-332: The Logo in docker page deprecated.
- Updated the logo in the docker's `README.md` to use the same in the 
project's `README.md`

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jerryZh65/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/58.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 #58


commit c2d09422f3c1e544f0193fc4b2de69eab4ee8bc4
Author: Ganhuazhang 
Date:   2017-08-14T07:07:51Z

MNEMONIC-332: The Logo in docker page deprecated




> The Logo in docker page deprecated
> --
>
> Key: MNEMONIC-332
> URL: https://issues.apache.org/jira/browse/MNEMONIC-332
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Ganhua Zhang
>Priority: Minor
>  Labels: documentation
>
> The logo link of docker page 
> ([https://github.com/apache/incubator-mnemonic/blob/master/docker/README.md]) 
> needs to be corrected referring to the project's README.md



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-332) The Logo in docker page deprecated

2017-08-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125288#comment-16125288
 ] 

ASF GitHub Bot commented on MNEMONIC-332:
-

Github user jerryZh65 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/57


> The Logo in docker page deprecated
> --
>
> Key: MNEMONIC-332
> URL: https://issues.apache.org/jira/browse/MNEMONIC-332
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Ganhua Zhang
>Priority: Minor
>  Labels: documentation
>
> The logo link of docker page 
> ([https://github.com/apache/incubator-mnemonic/blob/master/docker/README.md]) 
> needs to be corrected referring to the project's README.md



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-297) Add more constructors for ParameterHolder

2017-08-02 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111431#comment-16111431
 ] 

ASF GitHub Bot commented on MNEMONIC-297:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/56


> Add more constructors for ParameterHolder
> -
>
> Key: MNEMONIC-297
> URL: https://issues.apache.org/jira/browse/MNEMONIC-297
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> Please add the following constructors to class ParameterHolder
> public ParameterHolder(A n)
> public ParameterHolder(A n, DurableType[] d)
> public ParameterHolder(A n, DurableType[] d, EntityFactoryProxy[] e)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-297) Add more constructors for ParameterHolder

2017-08-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110327#comment-16110327
 ] 

ASF GitHub Bot commented on MNEMONIC-297:
-

GitHub user lql5083psu opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/56

MNEMONIC-297:Add more constructors for ParameterHolder

MNEMONIC-297:Add more constructors for ParameterHolder

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lql5083psu/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/56.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 #56


commit 37033452ba7883a7e31e4f036110b340e3a1d704
Author: lql5083psu 
Date:   2017-08-02T05:17:20Z

MNEMONIC-297:Add more constructors for ParameterHolder




> Add more constructors for ParameterHolder
> -
>
> Key: MNEMONIC-297
> URL: https://issues.apache.org/jira/browse/MNEMONIC-297
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> Please add the following constructors to class ParameterHolder
> public ParameterHolder(A n)
> public ParameterHolder(A n, DurableType[] d)
> public ParameterHolder(A n, DurableType[] d, EntityFactoryProxy[] e)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-298) construct Java based volatile memory service class

2017-07-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093788#comment-16093788
 ] 

ASF GitHub Bot commented on MNEMONIC-298:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/54

MNEMONIC-298:construct Java based volatile memory service class

MNEMONIC-298:construct Java based volatile memory service class

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/54.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 #54


commit 09a468f69a6394faa71f6527513da86c21d9b59d
Author: paleyss 
Date:   2017-07-19T20:55:57Z

MNEMONIC-298:construct Java based volatile memory service class




> construct Java based volatile memory service class
> --
>
> Key: MNEMONIC-298
> URL: https://issues.apache.org/jira/browse/MNEMONIC-298
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Memory-Service
>Reporter: Peili SHEN
>Assignee: Peili SHEN
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-305) Implement Remove operation for Durable Trees

2017-07-18 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091158#comment-16091158
 ] 

ASF GitHub Bot commented on MNEMONIC-305:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/53


> Implement Remove operation for Durable Trees
> 
>
> Key: MNEMONIC-305
> URL: https://issues.apache.org/jira/browse/MNEMONIC-305
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.9.0-incubating
>
>
> Implement remove operation for tree datastructure



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-281) Add test case to test implemented methods to handle optional parameters when creating durable class

2017-07-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086605#comment-16086605
 ] 

ASF GitHub Bot commented on MNEMONIC-281:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/52


> Add test case to test implemented methods to handle optional parameters when 
> creating durable class 
> 
>
> Key: MNEMONIC-281
> URL: https://issues.apache.org/jira/browse/MNEMONIC-281
> Project: Mnemonic
>  Issue Type: Test
>  Components: Collection
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Sub-task of MNEMONIC-276. Add test case for overloaded methods handling 
> optional parameters.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-305) Implement Remove operation for Durable Trees

2017-07-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086482#comment-16086482
 ] 

ASF GitHub Bot commented on MNEMONIC-305:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/53

MNEMONIC-305: Implement Remove operation for Durable Trees

Implement Remove operation for Durable Trees

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/53.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 #53


commit d4766a41a47288c9472ccfb958e283d270c6b149
Author: Johnu George 
Date:   2017-07-13T21:40:15Z

MNEMONIC-305: Implement Remove operation for Durable Trees




> Implement Remove operation for Durable Trees
> 
>
> Key: MNEMONIC-305
> URL: https://issues.apache.org/jira/browse/MNEMONIC-305
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.9.0-incubating
>
>
> Implement remove operation for tree datastructure



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-95) Create a Durable Set

2017-07-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085267#comment-16085267
 ] 

ASF GitHub Bot commented on MNEMONIC-95:


Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/51


> Create a Durable Set
> 
>
> Key: MNEMONIC-95
> URL: https://issues.apache.org/jira/browse/MNEMONIC-95
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
> Fix For: 0.9.0-incubating
>
>
> Implement a durable set that is generic, the durable set is not necessary to 
> fully comply with the Set interface of Java Set, but those basic operations 
> hinted by Java Set should be implemented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-281) Add test case to test implemented methods to handle optional parameters when creating durable class

2017-07-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085166#comment-16085166
 ] 

ASF GitHub Bot commented on MNEMONIC-281:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/52

MNEMONIC-281 Add test case to test the method handling optional param…

…eters

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/52.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 #52


commit 39902717e0ca14bcf5befba1ab9a86cdc65aa4a4
Author: Yanhui Zhao 
Date:   2017-07-13T03:52:44Z

MNEMONIC-281 Add test case to test the method handling optional parameters




> Add test case to test implemented methods to handle optional parameters when 
> creating durable class 
> 
>
> Key: MNEMONIC-281
> URL: https://issues.apache.org/jira/browse/MNEMONIC-281
> Project: Mnemonic
>  Issue Type: Test
>  Components: Collection
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
>Priority: Minor
> Fix For: 0.9.0-incubating
>
>
> Sub-task of MNEMONIC-276. Add test case for overloaded methods handling 
> optional parameters.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-175) Rename the build-tools directory to bin

2017-07-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074020#comment-16074020
 ] 

ASF GitHub Bot commented on MNEMONIC-175:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/50


> Rename the build-tools directory to bin
> ---
>
> Key: MNEMONIC-175
> URL: https://issues.apache.org/jira/browse/MNEMONIC-175
> Project: Mnemonic
>  Issue Type: Task
>  Components: Tools
>Affects Versions: 0.5.0-incubating
>Reporter: Wang, Gang
>Assignee: Yanhui Zhao
>
> to conform with the naming convention about the directory that contains 
> project executable files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-175) Rename the build-tools directory to bin

2017-07-03 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073018#comment-16073018
 ] 

ASF GitHub Bot commented on MNEMONIC-175:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/50

MNEMONIC-175 Rename the build-tools directory to bin

to conform with the naming convention about the directory that contains 
project executable files.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/50.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 #50


commit 2c82bdb531c58aef6c8d32eda7358ba9fe0c261c
Author: Yanhui Zhao 
Date:   2017-07-04T01:52:20Z

MNEMONIC-175 Rename the build-tools directory to bin




> Rename the build-tools directory to bin
> ---
>
> Key: MNEMONIC-175
> URL: https://issues.apache.org/jira/browse/MNEMONIC-175
> Project: Mnemonic
>  Issue Type: Task
>  Components: Tools
>Affects Versions: 0.5.0-incubating
>Reporter: Wang, Gang
>Assignee: Yanhui Zhao
>
> to conform with the naming convention about the directory that contains 
> project executable files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-280) Add overload methods to handle optional parameters when creating durable class

2017-07-02 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071849#comment-16071849
 ] 

ASF GitHub Bot commented on MNEMONIC-280:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/49


> Add overload methods to handle optional parameters when creating durable class
> --
>
> Key: MNEMONIC-280
> URL: https://issues.apache.org/jira/browse/MNEMONIC-280
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
> Fix For: 0.9.0-incubating
>
>
> Sub-task of MNEMONIC-276. Add overloaded methods for create and restore to 
> handle optional parameters when creating/restoring durable class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-280) Add overload methods to handle optional parameters when creating durable class

2017-07-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071438#comment-16071438
 ] 

ASF GitHub Bot commented on MNEMONIC-280:
-

GitHub user yzz127 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/49

MNEMONIC-280 Add overload methods to handle optional paramters

Sub-task of MNEMONIC-276. Add overloaded methods for create and restore to 
handle optional parameters when creating/restoring durable class. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzz127/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/49.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 #49


commit 7e63e49892237c83d11a7e2f54142f9175e076cd
Author: Yanhui Zhao 
Date:   2017-07-01T22:39:30Z

MNEMONIC-280 Add overload methods to handle optional paramters




> Add overload methods to handle optional parameters when creating durable class
> --
>
> Key: MNEMONIC-280
> URL: https://issues.apache.org/jira/browse/MNEMONIC-280
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Yanhui Zhao
>Assignee: Yanhui Zhao
> Fix For: 0.9.0-incubating
>
>
> Sub-task of MNEMONIC-276. Add overloaded methods for create and restore to 
> handle optional parameters when creating/restoring durable class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-293) Provide a way to persist the Bytebuffers created out of a durable chunk

2017-07-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071430#comment-16071430
 ] 

ASF GitHub Bot commented on MNEMONIC-293:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/48

MNEMONIC-293:Provide a way to persist the Bytebuffers created out of a 
durable chunk

MNEMONIC-293:Provide a way to persist the Bytebuffers created out of a 
durable chunk

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/48.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 #48


commit 071009d84bb13147d864225d7c0bfc11285fb0f8
Author: paley 
Date:   2017-07-01T22:42:06Z

MNEMONIC-293:Provide a way to persist the Bytebuffers created out of a 
durable chunk




> Provide a way to persist the Bytebuffers created out of a durable chunk
> ---
>
> Key: MNEMONIC-293
> URL: https://issues.apache.org/jira/browse/MNEMONIC-293
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: ramkrishna.s.vasudevan
>Assignee: Peili SHEN
>
> MNEMONIC-289 provided a way to create buffers out of a DurableChunk. It would 
> be nice to have a provision to persist() these buffers that are created out 
> of the Chunk by passing an offset and length so that what ever portion of the 
> Bytebuffers needs to be persisted can be done using these new API(s).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-292) Set initial limit for ChunkBuffers(equal to capacity)

2017-06-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067857#comment-16067857
 ] 

ASF GitHub Bot commented on MNEMONIC-292:
-

Github user johnugeorge closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/47


> Set initial limit for ChunkBuffers(equal to capacity)
> -
>
> Key: MNEMONIC-292
> URL: https://issues.apache.org/jira/browse/MNEMONIC-292
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.9.0-incubating
>Reporter: Johnu George
>Assignee: Wang, Gang
> Fix For: 0.9.0-incubating
>
>
> Capacity of chunkbuffers is set to the size specified by the user. But limit 
> is not set by default.  However, it is safer to set limit in the constructor. 
> (as done in java bytebuffer source) Else, user may see unexpected results.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-23 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061639#comment-16061639
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/46


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048115#comment-16048115
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121739249
  
--- Diff: docker/README.md ---
@@ -34,7 +33,8 @@ For old version docker v1.10 below, Please replace ARG 
with ENV and set its valu
 Build from git repository
 
 ```bash
-  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-CentOS
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-Ubuntu
--- End diff --

Please correct the folder name as well


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048116#comment-16048116
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121739198
  
--- Diff: docker/README.md ---
@@ -34,7 +33,8 @@ For old version docker v1.10 below, Please replace ARG 
with ENV and set its valu
 Build from git repository
 
 ```bash
-  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-CentOS
--- End diff --

Please correct the folder name as well


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047178#comment-16047178
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121546613
  
--- Diff: docker/README.md ---
@@ -2,24 +2,23 @@
 
  
 
-This is the "Dockerfile" that will automatically build the environment of 
this project. 
+This is the "Dockerfile" that will automatically build the centos/ubuntu 
of this project under ubuntu. 
--- End diff --

Please correct this sentence.


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047177#comment-16047177
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121546187
  
--- Diff: docker/README.md ---
@@ -34,7 +33,8 @@ For old version docker v1.10 below, Please replace ARG 
with ENV and set its valu
 Build from git repository
 
 ```bash
-  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-centos
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-ubuntu
--- End diff --

Please note the use of letter case, using docker-Ubuntu instead of 
docker-ubuntu.
Please also correct the corresponding folder name


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047176#comment-16047176
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121546082
  
--- Diff: docker/README.md ---
@@ -34,7 +33,8 @@ For old version docker v1.10 below, Please replace ARG 
with ENV and set its valu
 Build from git repository
 
 ```bash
-  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-centos
--- End diff --

Please note the use of letter case, using docker-CentOS instead of 
docker-centos.


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-278) Re-structure the folders of docker

2017-06-12 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047175#comment-16047175
 ] 

ASF GitHub Bot commented on MNEMONIC-278:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/46#discussion_r121546202
  
--- Diff: docker/README.md ---
@@ -34,7 +33,8 @@ For old version docker v1.10 below, Please replace ARG 
with ENV and set its valu
 Build from git repository
 
 ```bash
-  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker
+  $ docker build -t NAME[:TAG] 
https://github.com/apache/incubator-mnemonic.git#:docker:docker-centos
--- End diff --

Please also correct the corresponding folder name


> Re-structure the folders of docker
> --
>
> Key: MNEMONIC-278
> URL: https://issues.apache.org/jira/browse/MNEMONIC-278
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Docker
>Affects Versions: 0.8.0-incubating
>Reporter: Wang, Gang
>Assignee: Lan Lin
>
> The docker folders i.e. docker/ docker-ubuntu/ could be re-organized as 
> follows to improve the structure of docker related files.
> {code}
> incubator-mnemonic
> .|docker/
> ...|_docker-CentOS/
> |Dockerfile
> ...|_docker-Ubuntu/
> |Dockerfile
> ...|_README.md
> {code}
> Please also include the docker/ in build-tools/source-assembly.xml



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MNEMONIC-274) Add another Dockerfile for Ubuntu system

2017-06-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036553#comment-16036553
 ] 

ASF GitHub Bot commented on MNEMONIC-274:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/45


> Add another Dockerfile for Ubuntu system
> 
>
> Key: MNEMONIC-274
> URL: https://issues.apache.org/jira/browse/MNEMONIC-274
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Docker
>Affects Versions: 0.9.0-incubating
>Reporter: Wang, Gang
>Assignee: Yanhui Zhao
> Fix For: 0.9.0-incubating
>
>
> The existed Dockerfile has described how to setup Mnemonic development 
> environment for CentOS only, so we need another one for Ubuntu, because the 
> Ubuntu also is one of most popular server system.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-255) Add Insert and Search functionality for durable trees

2017-05-02 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993913#comment-15993913
 ] 

ASF GitHub Bot commented on MNEMONIC-255:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/44


> Add Insert and Search functionality for durable trees
> -
>
> Key: MNEMONIC-255
> URL: https://issues.apache.org/jira/browse/MNEMONIC-255
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.8.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.8.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-255) Add Insert and Search functionality for durable trees

2017-05-02 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993530#comment-15993530
 ] 

ASF GitHub Bot commented on MNEMONIC-255:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/44

MNEMONIC-255: Add Insert and Search functionality for balanced BST

This implements insert and search functions for balanced binary search 
tree(implemented as RB tree)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/44.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 #44


commit 5c54177dd80d224c9c111d8cb1a0bb05d5e63c4b
Author: Johnu George 
Date:   2017-05-02T19:07:04Z

MNEMONIC-255: Add Insert and Search functionality for balanced BST




> Add Insert and Search functionality for durable trees
> -
>
> Key: MNEMONIC-255
> URL: https://issues.apache.org/jira/browse/MNEMONIC-255
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.8.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.8.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-254) Set function goes into loop with cyclic structures

2017-05-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991245#comment-15991245
 ] 

ASF GitHub Bot commented on MNEMONIC-254:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/43


> Set function goes into loop with cyclic structures
> --
>
> Key: MNEMONIC-254
> URL: https://issues.apache.org/jira/browse/MNEMONIC-254
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.8.0-incubating
>
>
> In generated Set functions of durable structures, registerAutoReclaim() and 
> CancelAutoReclaim() functions are called on linked fields.  Hence, if it is 
> cyclic structure, it causes infinite loop. Solution is to call 
> registerAutoReclaim only if reclaim was not already set on the linked field 
> and vice versa.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-254) Set function goes into loop with cyclic structures

2017-04-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989780#comment-15989780
 ] 

ASF GitHub Bot commented on MNEMONIC-254:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/43

MNEMONIC-254: Avoid loops in set functions for cyclic structures



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/43.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 #43


commit fa04538dbd7420c7e84803826608283ab68b4081
Author: Johnu George 
Date:   2017-04-29T05:55:08Z

MNEMONIC-254: Avoid loops in set functions for cyclic structures




> Set function goes into loop with cyclic structures
> --
>
> Key: MNEMONIC-254
> URL: https://issues.apache.org/jira/browse/MNEMONIC-254
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.8.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.8.0-incubating
>
>
> In generated Set functions of durable structures, registerAutoReclaim() and 
> CancelAutoReclaim() functions are called on linked fields.  Hence, if it is 
> cyclic structure, it causes infinite loop. Solution is to call 
> registerAutoReclaim only if reclaim was not already set on the linked field 
> and vice versa.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-239) Compilation Error when durable field type is boolean

2017-04-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977713#comment-15977713
 ] 

ASF GitHub Bot commented on MNEMONIC-239:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/42


> Compilation Error when durable field type is boolean
> 
>
> Key: MNEMONIC-239
> URL: https://issues.apache.org/jira/browse/MNEMONIC-239
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.7.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.7.0-incubating
>
>
> Lossy conversion from int to boolean compilation error occurs when durable 
> field type is boolean. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-239) Compilation Error when durable field type is boolean

2017-04-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977610#comment-15977610
 ] 

ASF GitHub Bot commented on MNEMONIC-239:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/42

MNEMONIC-239: Fix compilation error for boolean durable field types



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/42.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 #42


commit 2bc10415b79ac10e224542b8901ccf960276a192
Author: Johnu George 
Date:   2017-04-20T19:01:46Z

MNEMONIC-239: Fix compilation error for boolean durable field types




> Compilation Error when durable field type is boolean
> 
>
> Key: MNEMONIC-239
> URL: https://issues.apache.org/jira/browse/MNEMONIC-239
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.7.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.7.0-incubating
>
>
> Lossy conversion from int to boolean compilation error occurs when durable 
> field type is boolean. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-237) Incorrect offset for fields with primitive types

2017-04-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971759#comment-15971759
 ] 

ASF GitHub Bot commented on MNEMONIC-237:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/41


> Incorrect offset for fields with primitive types 
> -
>
> Key: MNEMONIC-237
> URL: https://issues.apache.org/jira/browse/MNEMONIC-237
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Johnu George
>Assignee: Johnu George
>
> Currently all fields use default size of 8 bytes even if it is a byte field



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-237) Incorrect offset for fields with primitive types

2017-04-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971736#comment-15971736
 ] 

ASF GitHub Bot commented on MNEMONIC-237:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/41

MNEMONIC-237: Incorrect offset for primitive type fields

Right offsets are provided for primitive type fields based on the field 
lengths.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/41.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 #41


commit c7ce58c21d90a95abcb1ed9e9c6e05a89bdf9737
Author: Johnu George 
Date:   2017-04-17T22:09:59Z

MNEMONIC-237: Incorrect offset for primitive type fields




> Incorrect offset for fields with primitive types 
> -
>
> Key: MNEMONIC-237
> URL: https://issues.apache.org/jira/browse/MNEMONIC-237
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Johnu George
>Assignee: Johnu George
>
> Currently all fields use default size of 8 bytes even if it is a byte field



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-234) Reorder field destroy of a durable data structure

2017-03-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947782#comment-15947782
 ] 

ASF GitHub Bot commented on MNEMONIC-234:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/40


> Reorder field destroy of a durable data structure
> -
>
> Key: MNEMONIC-234
> URL: https://issues.apache.org/jira/browse/MNEMONIC-234
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.6.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.6.0-incubating
>
>
> Holder destroy must be called at last after destroying all fields of the data 
> structure. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-234) Reorder field destroy of a durable data structure

2017-03-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947746#comment-15947746
 ] 

ASF GitHub Bot commented on MNEMONIC-234:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/40

MNEMONIC-234: Reorder field destroy of a durable data structure

Holder must be destroyed at last after destroying other fields. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/40.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 #40


commit b62fb0d31528087a95c4ec19ef408344b8ddacd7
Author: Johnu George 
Date:   2017-03-29T19:20:18Z

MNEMONIC-234: Reorder field destroy of a durable data structure




> Reorder field destroy of a durable data structure
> -
>
> Key: MNEMONIC-234
> URL: https://issues.apache.org/jira/browse/MNEMONIC-234
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.6.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.6.0-incubating
>
>
> Holder destroy must be called at last after destroying all fields of the data 
> structure. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-233) Managed resources must be restored before destroy of Generic Field

2017-03-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947737#comment-15947737
 ] 

ASF GitHub Bot commented on MNEMONIC-233:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/39


> Managed resources must be restored before destroy of Generic Field
> --
>
> Key: MNEMONIC-233
> URL: https://issues.apache.org/jira/browse/MNEMONIC-233
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.6.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.6.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-233) Managed resources must be restored before destroy of Generic Field

2017-03-29 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947701#comment-15947701
 ] 

ASF GitHub Bot commented on MNEMONIC-233:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/39

MNEMONIC-233: Restore the resources before destroy of Generic Field

There will be memory leaks if resources are not restored during destroy of 
a generic field.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/39.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 #39


commit 9c9312e51d17689926babdc5487ba46055046ab4
Author: Johnu George 
Date:   2017-03-29T18:54:09Z

MNEMONIC-233: Restore the resources before destroy




> Managed resources must be restored before destroy of Generic Field
> --
>
> Key: MNEMONIC-233
> URL: https://issues.apache.org/jira/browse/MNEMONIC-233
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.6.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.6.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-228) Create Iterators for durable arrays

2017-03-22 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937107#comment-15937107
 ] 

ASF GitHub Bot commented on MNEMONIC-228:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/38


> Create Iterators for durable arrays
> ---
>
> Key: MNEMONIC-228
> URL: https://issues.apache.org/jira/browse/MNEMONIC-228
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Reporter: Johnu George
>Assignee: Johnu George
>
> Provide Iterator implementations for Durable Arrays



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-228) Create Iterators for durable arrays

2017-03-22 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936944#comment-15936944
 ] 

ASF GitHub Bot commented on MNEMONIC-228:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/38

MNEMONIC-228: Implement iterators for durable arrays



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/38.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 #38


commit e912470d078f34d3b0b290d09fa4de152767c86b
Author: Johnu George 
Date:   2017-03-22T19:05:54Z

MNEMONIC-228: Implement iterators for durable arrays




> Create Iterators for durable arrays
> ---
>
> Key: MNEMONIC-228
> URL: https://issues.apache.org/jira/browse/MNEMONIC-228
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Reporter: Johnu George
>Assignee: Johnu George
>
> Provide Iterator implementations for Durable Arrays



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-95) Create a Durable Set

2017-03-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15934115#comment-15934115
 ] 

ASF GitHub Bot commented on MNEMONIC-95:


Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/37


> Create a Durable Set
> 
>
> Key: MNEMONIC-95
> URL: https://issues.apache.org/jira/browse/MNEMONIC-95
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Debo Dutta
> Fix For: 0.6.0-incubating
>
>
> Implement a durable set that is generic, the durable set is not necessary to 
> fully comply with the Set interface of Java Set, but those basic operations 
> hinted by Java Set should be implemented.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-221) Create a DurableArray

2017-03-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15933730#comment-15933730
 ] 

ASF GitHub Bot commented on MNEMONIC-221:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/36


> Create a DurableArray
> -
>
> Key: MNEMONIC-221
> URL: https://issues.apache.org/jira/browse/MNEMONIC-221
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
>
> The DurableArray is a data structure which stores a sequential collection of 
> elements of the same generic type on durable memory space.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-221) Create a DurableArray

2017-03-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15933385#comment-15933385
 ] 

ASF GitHub Bot commented on MNEMONIC-221:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/36#discussion_r106997111
  
--- Diff: 
mnemonic-collections/src/main/java/org/apache/mnemonic/collections/DurableArrayFactory.java
 ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.mnemonic.collections;
+
+import org.apache.mnemonic.DurableType;
+import org.apache.mnemonic.EntityFactoryProxy;
+import org.apache.mnemonic.OutOfHybridMemory;
+import org.apache.mnemonic.RestorableAllocator;
+import org.apache.mnemonic.RestoreDurableEntityError;
+
+public class DurableArrayFactory {
+  public static , E> DurableArray
+  create(A allocator) throws OutOfHybridMemory {
+return create(allocator, 0, false);
+  }
+
+  public static , E> DurableArray
+  create(A allocator, int size) throws OutOfHybridMemory {
+return create(allocator, size, false);
+  }
+
+  public static , E> DurableArray
+  create(A allocator, int size, boolean autoreclaim) throws 
OutOfHybridMemory {
+return create(allocator, null, null, size, autoreclaim);
+  }
+
+  public static , E> DurableArray
+  create(A allocator, EntityFactoryProxy[] factoryproxys, 
DurableType[] gfields,
+   int size, boolean autoreclaim) throws OutOfHybridMemory 
{
+DurableArrayImpl entity = new DurableArrayImpl();
+entity.setSize(size);
--- End diff --

Could pass the size as the parameter of the constructor of class 
DurableArrayImpl, because, if the modifier setSize() is public, the user might 
misuse it as what Resize() does.


> Create a DurableArray
> -
>
> Key: MNEMONIC-221
> URL: https://issues.apache.org/jira/browse/MNEMONIC-221
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
>
> The DurableArray is a data structure which stores a sequential collection of 
> elements of the same generic type on durable memory space.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-221) Create a DurableArray

2017-03-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15933288#comment-15933288
 ] 

ASF GitHub Bot commented on MNEMONIC-221:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/36

MNEMONIC-221: Implement get and set for durable array

This PR tracks the implementation of new Durable Array datastructure with 
get and set of generic types

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/36.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 #36


commit f36002537c8967b776f0f1875ab1ee035bb5899d
Author: Johnu George 
Date:   2017-03-20T18:24:31Z

MNEMONIC-221: Implement get and set for durable array




> Create a DurableArray
> -
>
> Key: MNEMONIC-221
> URL: https://issues.apache.org/jira/browse/MNEMONIC-221
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Collection
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
>
> The DurableArray is a data structure which stores a sequential collection of 
> elements of the same generic type on durable memory space.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-216) Support Hadoop mapred APIs

2017-03-15 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926855#comment-15926855
 ] 

ASF GitHub Bot commented on MNEMONIC-216:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/35

MNEMONIC-216 & MNEMONIC-220

NEMONIC-220: Remove the dependency on OutputDir of FileOutputFormat
MNEMONIC-216: Support Hadoop mapred APIs

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/35.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 #35


commit 224ef2feceaa0da78b38f306f94f73b7d9a4d53e
Author: paley 
Date:   2017-03-15T16:46:48Z

MNEMONIC-216: Support Hadoop mapred APIs
MNEMONIC-220: Remove the dependency on OutputDir of FileOutputFormat




> Support Hadoop mapred APIs
> --
>
> Key: MNEMONIC-216
> URL: https://issues.apache.org/jira/browse/MNEMONIC-216
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Hadoop-Integration
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.6.0-incubating
>
>
> Implement the interfaces of Hadoop mapred to support inputformat/outputformat 
> and reader/writer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-218) Make inputSession & outputSession to accept the Configration parameter

2017-03-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925338#comment-15925338
 ] 

ASF GitHub Bot commented on MNEMONIC-218:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/34


> Make inputSession & outputSession to accept the Configration parameter
> --
>
> Key: MNEMONIC-218
> URL: https://issues.apache.org/jira/browse/MNEMONIC-218
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Hadoop-Integration
>Affects Versions: 0.6.0-incubating
>Reporter: Peili SHEN
>Assignee: Peili SHEN
> Fix For: 0.6.0-incubating
>
>
> Add the constructor of MneDurableOutputSession and MneDurableInputSession to 
> accept Configuration parameter.
> Create setter & getter for Configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-218) Make inputSession & outputSession to accept the Configration parameter

2017-03-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925227#comment-15925227
 ] 

ASF GitHub Bot commented on MNEMONIC-218:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/34#discussion_r106051332
  
--- Diff: 
mnemonic-hadoop/mnemonic-hadoop-mapreduce/src/main/java/org/apache/mnemonic/hadoop/MneDurableInputSession.java
 ---
@@ -144,4 +150,12 @@ public NonVolatileMemAllocator getAllocator() {
   public long getHandler() {
 return m_handler;
   }
+
+public Configuration getConfiguration() {
+   return configuration;
+}
+
+public void setConfiguration(Configuration configuration) {
+   this.configuration = configuration;
--- End diff --

ditto.


> Make inputSession & outputSession to accept the Configration parameter
> --
>
> Key: MNEMONIC-218
> URL: https://issues.apache.org/jira/browse/MNEMONIC-218
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Hadoop-Integration
>Affects Versions: 0.6.0-incubating
>Reporter: Peili SHEN
>Assignee: Peili SHEN
> Fix For: 0.6.0-incubating
>
>
> Add the constructor of MneDurableOutputSession and MneDurableInputSession to 
> accept Configuration parameter.
> Create setter & getter for Configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-218) Make inputSession & outputSession to accept the Configration parameter

2017-03-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925228#comment-15925228
 ] 

ASF GitHub Bot commented on MNEMONIC-218:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/34#discussion_r106051307
  
--- Diff: 
mnemonic-hadoop/mnemonic-hadoop-mapreduce/src/main/java/org/apache/mnemonic/hadoop/MneDurableInputSession.java
 ---
@@ -144,4 +150,12 @@ public NonVolatileMemAllocator getAllocator() {
   public long getHandler() {
 return m_handler;
   }
+
+public Configuration getConfiguration() {
+   return configuration;
--- End diff --

Please use spaces instead of a Tab


> Make inputSession & outputSession to accept the Configration parameter
> --
>
> Key: MNEMONIC-218
> URL: https://issues.apache.org/jira/browse/MNEMONIC-218
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Hadoop-Integration
>Affects Versions: 0.6.0-incubating
>Reporter: Peili SHEN
>Assignee: Peili SHEN
> Fix For: 0.6.0-incubating
>
>
> Add the constructor of MneDurableOutputSession and MneDurableInputSession to 
> accept Configuration parameter.
> Create setter & getter for Configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-105) Add a set of testcases for Durable Map

2017-03-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925213#comment-15925213
 ] 

ASF GitHub Bot commented on MNEMONIC-105:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/33


> Add a set of testcases for Durable Map
> --
>
> Key: MNEMONIC-105
> URL: https://issues.apache.org/jira/browse/MNEMONIC-105
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.4.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
> Fix For: 0.4.0-incubating
>
>
> Verify all functionalities of Durable Map



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-105) Add a set of testcases for Durable Map

2017-03-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923601#comment-15923601
 ] 

ASF GitHub Bot commented on MNEMONIC-105:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/33

MNEMONIC-105: Adding Testcases for durable buffers and chunks

Added missing testcases for having durable buffer/chunks as HashMap values

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/33.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 #33


commit c165b1d6e6bd11a5a92da3cb73cb214729498883
Author: Johnu George 
Date:   2017-03-14T05:26:20Z

MNEMONIC-105: Adding Testcases for durable buffers and chunks




> Add a set of testcases for Durable Map
> --
>
> Key: MNEMONIC-105
> URL: https://issues.apache.org/jira/browse/MNEMONIC-105
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Affects Versions: 0.4.0-incubating
>Reporter: Wang, Gang
>Assignee: Johnu George
> Fix For: 0.4.0-incubating
>
>
> Verify all functionalities of Durable Map



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-215) Memory leak when LinkedList element is destroyed

2017-03-13 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922868#comment-15922868
 ] 

ASF GitHub Bot commented on MNEMONIC-215:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/32

MNEMONIC-215: Cleanup of memory leaks in Linkedlist implementation

Possible memory leaks are cleaned up when Linkedlist is removed.  Verified 
that there are no memory leaks with DurableHashMapNGTest

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/32.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 #32


commit 0a92221c7e3f4f5d58772517a0394c5580a2cf1e
Author: Johnu George 
Date:   2017-03-13T20:14:25Z

MNEMONIC-215: Cleanup of memory leaks in Linkedlist impl




> Memory leak when LinkedList element is destroyed
> 
>
> Key: MNEMONIC-215
> URL: https://issues.apache.org/jira/browse/MNEMONIC-215
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Johnu George
>Assignee: Johnu George
>Priority: Critical
> Fix For: 0.6.0-incubating
>
>
> Here is the implementation of the destroy function in LinkedList node
>   @Override
>   public void destroy() throws RetrieveDurableEntityError {
> m_holder.destroy();
> if (null != m_item) {
>   m_item.destroy();
>   m_item = null;
> }
> if (null != m_next) {
>   m_next.destroy();
>   m_next = null;
> }
>   }
> Next is destroyed only when m_next is not null. m_next can also be null if 
> next item is not loaded into memory from PMem. It is required to first 
> restore the item using getNext and then call destroy. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-214) Make MneDurableInputSession rewind-able

2017-03-07 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900073#comment-15900073
 ] 

ASF GitHub Bot commented on MNEMONIC-214:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/30


> Make MneDurableInputSession rewind-able
> ---
>
> Key: MNEMONIC-214
> URL: https://issues.apache.org/jira/browse/MNEMONIC-214
> Project: Mnemonic
>  Issue Type: New Feature
>  Components: Hadoop-Integration
>Affects Versions: 0.6.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.6.0-incubating
>
>
> This feature could allow user re-visit the input data set from begin without 
> the need of re-create and re-configure a new session object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-208) Implement GET/PUT/DELETE Map operations

2017-03-06 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898167#comment-15898167
 ] 

ASF GitHub Bot commented on MNEMONIC-208:
-

Github user bigdata-memory commented on a diff in the pull request:

https://github.com/apache/incubator-mnemonic/pull/29#discussion_r104529676
  
--- Diff: 
mnemonic-collections/src/main/java/org/apache/mnemonic/collections/DurableHashMapImpl.java
 ---
@@ -0,0 +1,447 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.mnemonic.collections;
+
+import org.apache.mnemonic.EntityFactoryProxy;
+import org.apache.mnemonic.DurableType;
+import org.apache.mnemonic.MemChunkHolder;
+import org.apache.mnemonic.MemoryDurableEntity;
+import org.apache.mnemonic.OutOfHybridMemory;
+import org.apache.mnemonic.RestorableAllocator;
+import org.apache.mnemonic.RestoreDurableEntityError;
+import org.apache.mnemonic.RetrieveDurableEntityError;
+import org.apache.mnemonic.Utils;
+import org.apache.commons.lang3.tuple.Pair;
+import org.apache.commons.lang3.ArrayUtils;
+import sun.misc.Unsafe;
+
+@SuppressWarnings("restriction")
+public class DurableHashMapImpl, K, V>
+extends DurableHashMap implements MemoryDurableEntity {
+
+  private static final long DEFAULT_MAP_SIZE = 16;
+  private static final float DEFAULT_MAP_LOAD_FACTOR = 0.75f;
+  private static final long MAX_OBJECT_SIZE = 8;
+  private static long[][] fieldInfo;
+  private Unsafe unsafe;
+  private EntityFactoryProxy[] factoryProxy;
+  private EntityFactoryProxy[] listefproxies;
+  private DurableType[] genericField;
+  private DurableType[] listgftypes;
+  private volatile boolean autoResize = true;
+  private volatile boolean autoReclaim;
+  private MemChunkHolder holder;
+  private MemChunkHolder chunkAddr;
+  private A allocator;
+  /**
+   * Set initial capacity for a hashmap. It can grow in size.
+   * 
+   * @param capacity
+   *  Initial capacity to be set
+   */
+  public void setCapacityHint(long capacity) {
+if (0 == capacity) {
+  totalCapacity = DEFAULT_MAP_SIZE;
+} else {
+  totalCapacity = 1;
+  while (totalCapacity < capacity) {
+totalCapacity <<= 1;
+  }
+}
+threshold = (long) (totalCapacity * DEFAULT_MAP_LOAD_FACTOR);
+  }
+
+  /**
+   * Add a new key-value pair to map
+   * 
+   * @param key
+   *  the key to be set
+   *
+   * @param value
+   *  the value to be set
+   *
+   * @return previous value with key else return null
+   */
+  @Override
+  public V put(K key, V value) {
+int hash = hash(key.hashCode());
+long bucketIndex = getBucketIndex(hash);
+long bucketAddr = holder.get() + MAX_OBJECT_SIZE * bucketIndex;
+V retVal = addEntry(key, value, bucketAddr);
+if (autoResize && (mapSize >= threshold)) {
+  resize(2 * totalCapacity);
+}
+return retVal;
+  }
+
+  /**
+   * Add a new key-value pair to map at a given bucket address
+   * 
+   * @param key
+   *  the key to be set
+   *
+   * @param value
+   *  the value to be set
+   *
+   * @param bucketAddr
+   *  the addr of the bucket where key is hashed
+   *
+   * @return previous value with key else return null
+   */
+  public V addEntry(K key, V value, long bucketAddr) {
+V retValue = null;
+long handler = unsafe.getAddress(bucketAddr);
+if (0L == handler) {
+  DurableSinglyLinkedList> head = 
DurableSinglyLinkedListFactory.create(allocator, 
+  listefproxies, listgftypes, false);
+  MapEntry entry = MapEntryFactory.create(allocator, 
factoryProxy, genericField, false);
+  entry.setKey(key, false);
+  entry.setValue(value, 

[jira] [Commented] (MNEMONIC-208) Implement GET/PUT/DELETE Map operations

2017-03-06 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897888#comment-15897888
 ] 

ASF GitHub Bot commented on MNEMONIC-208:
-

GitHub user johnugeorge opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/29

MNEMONIC-208: Adding PUT/GET/DELETE for durable maps.

This pull request defines durable map data structure and basic operations- 
PUT, GET , DELETE and RESIZE.  

Implementation details:

Durable maps are implemented on memory chunks(buckets) where each memory 
allocated chunk stores a durable linkedlist.   Below figure shows a map with 
capacity 4 and size 3

  |_bucket 1_|  --->null
  |_bucket 2_| --->|__LinkedList elem1__|--->null
  |_bucket 3_|>null
  |_bucket 4_|>|__LinkedList elem1__|--->|__LinkedList 
elem2__|--->null
  

During instantiation of a durable map data structure,  the user can opt to 
choose initialCapacity as a constructor parameter to specify the number of 
buckets to be allocated.  If it is not provided, default map capacity(16) 
number of buckets are initially allocated. If map size exceeds a configurable 
threshold, map is resized automatically to twice the current capacity.  This 
incurs reallocation cost and hence it is preferred to provide initialCapacity 
hint if user knows approximate size of the input dataset. 

Map keys are hashed to buckets and GET/PUT/DELETE operations are executed 
on the corresponding LinkedList structure.

The restore of durable maps is implemented in an indirect way. The handler 
of the buckets memory chunk is stored in a different memory chunk, which is 
returned to the user via getHandler() method. The handler of buckets memory 
chunk will be changed during resize operation and hence, it cannot be provided 
to the user directly.
 
Destroy will be revisited after the fix for [Jira: 
215](https://issues.apache.org/jira/browse/MNEMONIC-215)

The test cases are added that demonstrates the usage of Primitive/Generic 
Objects as Keys and Values in a durable map. 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnugeorge/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/29.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 #29


commit 4be77912bff8343077a849f320ab32df27d90979
Author: Johnu George 
Date:   2017-03-06T18:38:27Z

MNEMONIC-208: Adding PUT/GET/DELETE for durable maps.




> Implement GET/PUT/DELETE Map operations  
> -
>
> Key: MNEMONIC-208
> URL: https://issues.apache.org/jira/browse/MNEMONIC-208
> Project: Mnemonic
>  Issue Type: Sub-task
>  Components: Collection
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.5.0-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-200) Rewrite runall script in Python

2017-02-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889601#comment-15889601
 ] 

ASF GitHub Bot commented on MNEMONIC-200:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/28


> Rewrite runall script in Python
> ---
>
> Key: MNEMONIC-200
> URL: https://issues.apache.org/jira/browse/MNEMONIC-200
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Tools
>Affects Versions: 0.5.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.5.0-incubating
>
>
> Along with increasing test cases need to be managed by runall, it is 
> necessary to implement a more flexible and re-usable script to handle new 
> test cases instead of manually adding duplicated commands to runall script.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-200) Rewrite runall script in Python

2017-02-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889493#comment-15889493
 ] 

ASF GitHub Bot commented on MNEMONIC-200:
-

GitHub user paleyss opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/28

MNEMONIC-200: Rewrite runall script in Python



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paleyss/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/28.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 #28


commit 9ef706dc6a7f7cac3db32549cb5d188af1f2fe3c
Author: paley 
Date:   2017-03-01T04:05:59Z

MNEMONIC-200: Rewrite runall script in Python

commit 84151b08bb46b94c404750967aefb307f0c88013
Author: paley 
Date:   2017-03-01T04:17:15Z

MNEMONIC-200: Rewrite runall script in Python




> Rewrite runall script in Python
> ---
>
> Key: MNEMONIC-200
> URL: https://issues.apache.org/jira/browse/MNEMONIC-200
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Tools
>Affects Versions: 0.5.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.5.0-incubating
>
>
> Along with increasing test cases need to be managed by runall, it is 
> necessary to implement a more flexible and re-usable script to handle new 
> test cases instead of manually adding duplicated commands to runall script.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-205) Adding Durability to resized Memory Allocations

2017-02-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889004#comment-15889004
 ] 

ASF GitHub Bot commented on MNEMONIC-205:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/27


> Adding Durability to resized Memory Allocations
> ---
>
> Key: MNEMONIC-205
> URL: https://issues.apache.org/jira/browse/MNEMONIC-205
> Project: Mnemonic
>  Issue Type: Bug
>Affects Versions: 0.5.0-incubating
>Reporter: Johnu George
>Assignee: Johnu George
> Fix For: 0.5.0-incubating
>
>
> Adding Durable to resized memory allocations that are created via 
> resizeBuffer and resizeChunks. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-204) Fix issues with the pmalloc service on MacOS

2017-02-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888756#comment-15888756
 ] 

ASF GitHub Bot commented on MNEMONIC-204:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/26


> Fix issues with the pmalloc service on MacOS
> 
>
> Key: MNEMONIC-204
> URL: https://issues.apache.org/jira/browse/MNEMONIC-204
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Debo Dutta
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-204) Fix issues with the pmalloc service on MacOS

2017-02-28 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887563#comment-15887563
 ] 

ASF GitHub Bot commented on MNEMONIC-204:
-

GitHub user ddutta opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/26

MNEMONIC-204

Added /usr/local to CMakeList

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ddutta/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/26.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 #26


commit 276cc4f3c9c12afa71a7ff1910ae6ddbe63d3408
Author: Debo Dutta 
Date:   2017-02-28T08:38:11Z

MNEMONIC-204




> Fix issues with the pmalloc service on MacOS
> 
>
> Key: MNEMONIC-204
> URL: https://issues.apache.org/jira/browse/MNEMONIC-204
> Project: Mnemonic
>  Issue Type: Bug
>Reporter: Debo Dutta
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-191) Add Mnemonic Hadoop Mapreduce test case to runall script

2017-02-14 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866992#comment-15866992
 ] 

ASF GitHub Bot commented on MNEMONIC-191:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/25


> Add Mnemonic Hadoop Mapreduce test case to runall script
> 
>
> Key: MNEMONIC-191
> URL: https://issues.apache.org/jira/browse/MNEMONIC-191
> Project: Mnemonic
>  Issue Type: Task
>  Components: Hadoop-Integration, Tools
>Affects Versions: 0.5.0-incubating
>Reporter: Wang, Gang
>Assignee: Peili SHEN
> Fix For: 0.5.0-incubating
>
>
> The project README.md has described the command to run the test, but it has 
> not yet been included in runall.sh.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (MNEMONIC-114) nvml-vmem-service compilation warnings

2016-09-26 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524183#comment-15524183
 ] 

ASF GitHub Bot commented on MNEMONIC-114:
-

Github user ssimons0814 closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/23


> nvml-vmem-service compilation warnings
> --
>
> Key: MNEMONIC-114
> URL: https://issues.apache.org/jira/browse/MNEMONIC-114
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Memory-Service
>Affects Versions: 0.3.0-incubating
>Reporter: Wang, Gang
>Assignee: Li Shen
> Fix For: 0.3.0-incubating
>
>
> There are some warnings while compiling the sub-module 
> mnemonic-nvml-vmem-service as follows
> -
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_nretrieveSize’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:116:
>  warning: assignment makes integer from pointer without a cast
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_ngetBaseAddress’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:194:
>  warning: implicit declaration of function ‘b_addr’
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_nhandlerCapacity’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:186:
>  warning: control reaches end of non-void function
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_ngetHandler’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:180:
>  warning: control reaches end of non-void function



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MNEMONIC-114) nvml-vmem-service compilation warnings

2016-09-26 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524045#comment-15524045
 ] 

ASF GitHub Bot commented on MNEMONIC-114:
-

GitHub user ssimons0814 opened a pull request:

https://github.com/apache/incubator-mnemonic/pull/23

MNEMONIC-114: nvml-vmem-service compilation warnings

There is still a warning for 
"Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_nretrieveSize"
 when I change null to 0L.  Will update the NewDirectByteBuffer to 
GetDirectBufferAddress.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ssimons0814/incubator-mnemonic master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-mnemonic/pull/23.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 #23


commit 39f8c457506339ff0ebbfd844fd5883f17f41cdf
Author: Li Shen 
Date:   2016-09-26T20:04:24Z

MNEMONIC-114: nvml-vmem-service compilation warnings




> nvml-vmem-service compilation warnings
> --
>
> Key: MNEMONIC-114
> URL: https://issues.apache.org/jira/browse/MNEMONIC-114
> Project: Mnemonic
>  Issue Type: Bug
>  Components: Memory-Service
>Affects Versions: 0.3.0-incubating
>Reporter: Wang, Gang
>Assignee: Li Shen
> Fix For: 0.3.0-incubating
>
>
> There are some warnings while compiling the sub-module 
> mnemonic-nvml-vmem-service as follows
> -
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_nretrieveSize’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:116:
>  warning: assignment makes integer from pointer without a cast
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_ngetBaseAddress’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:194:
>  warning: implicit declaration of function ‘b_addr’
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_nhandlerCapacity’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:186:
>  warning: control reaches end of non-void function
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:
>  In function 
> ‘Java_org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl_ngetHandler’:
> [exec] 
> /home/wg/workspace/incubator-mnemonic/mnemonic-memory-services/mnemonic-nvml-vmem-service/src/main/native/org_apache_mnemonic_service_memoryservice_internal_VMemServiceImpl.c:180:
>  warning: control reaches end of non-void function



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MNEMONIC-102) Rename allocatorservice to memoryservice

2016-09-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456715#comment-15456715
 ] 

ASF GitHub Bot commented on MNEMONIC-102:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-mnemonic/pull/20


> Rename allocatorservice to memoryservice
> 
>
> Key: MNEMONIC-102
> URL: https://issues.apache.org/jira/browse/MNEMONIC-102
> Project: Mnemonic
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 0.3.0-incubating
>Reporter: Wang, Gang
>Assignee: Chuan Yang
> Fix For: 0.3.0-incubating
>
>
> The name of allocatorservice is located in
> incubator-mnemonic/mnemonic-core/src/main/java/org/apache/mnemonic/service/allocatorservice
> It should be renamed to memoryservice.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MNEMONIC-60) Apply Transaction, Retrievable interfaces to class VolatileMemAllocator

2016-08-31 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


  1   2   >