[jira] [Commented] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413470#comment-16413470
 ] 

Nishadi Kirielle commented on GORA-535:
---

Hi [~carlosrmng] ,

That's great..!!! I will review it and send you a reply.

Regards,
Nishadi

> Add a data store for Apache Ignite 
> ---
>
> Key: GORA-535
> URL: https://issues.apache.org/jira/browse/GORA-535
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Nishadi Kirielle
>Priority: Major
>  Labels: gsoc2018
>
> Currently, Gora has support for persisting objects to various database models 
> such as Apache Hbase, Apache Cassandra and much more. [1] This project aims 
> to extend its capability to provide support for Apache Ignite database.
> Apache Ignite is a distributed database, caching and processing platform.[2] 
> [1]. [http://gora.apache.org/] 
> [2] . [https://ignite.apache.org/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394411#comment-16394411
 ] 

Nishadi Kirielle commented on GORA-535:
---

Hi [~carlosrmng], [~chanuka1031] ,

Welcome to Apache Gora project. 

This project aims to integrate the Apache Ignite with Gora. As Gora already has 
caching stores like [JCache 
store|https://github.com/apache/gora/tree/master/gora-jcache] and a [infinispan 
store|https://github.com/apache/gora/tree/master/gora-infinispan], the main 
objective we are looking for in this project is to use [native persistence of 
Apache Ignite|https://ignite.apache.org/arch/persistence.html]. Thus, in the 
implementation, we can go ahead with Ignite specific APIs. 

In getting started with the project, you can follow up the below resources;
 * [Apache Gora Tutorial |http://gora.apache.org/current/tutorial.html]
 * [Writing a new 
module|https://cwiki.apache.org/confluence/display/GORA/Writing+a+new+DataStore+for+Gora+HOW_TO]

Please feel free to ask any questions you have. Good luck...!!!

> Add a data store for Apache Ignite 
> ---
>
> Key: GORA-535
> URL: https://issues.apache.org/jira/browse/GORA-535
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Nishadi Kirielle
>Priority: Major
>  Labels: gsoc2018
>
> Currently, Gora has support for persisting objects to various database models 
> such as Apache Hbase, Apache Cassandra and much more. [1] This project aims 
> to extend its capability to provide support for Apache Ignite database.
> Apache Ignite is a distributed database, caching and processing platform.[2] 
> [1]. [http://gora.apache.org/] 
> [2] . [https://ignite.apache.org/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-535:
--
Description: 
Currently, Gora has support for persisting objects to various database models 
such as Apache Hbase, Apache Cassandra and much more. [1] This project aims to 
extend its capability to provide support for Apache Ignite database.

Apache Ignite is a distributed database, caching and processing platform.[2] 

[1]. [http://gora.apache.org/] 

[2] . [https://ignite.apache.org/]

 

  was:
Currently, Gora has support persisting objects to various database models such 
as Apache Hbase, Apache Cassandra and much more. [1] This project aims to 
extend its capability to provide support for Apache Ignite database.

Apache Ignite is a distributed database, caching and processing platform.[2] 

[1]. [http://gora.apache.org/] 

[2] . [https://ignite.apache.org/]

 


> Add a data store for Apache Ignite 
> ---
>
> Key: GORA-535
> URL: https://issues.apache.org/jira/browse/GORA-535
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Nishadi Kirielle
>Priority: Major
>  Labels: gsoc2018
>
> Currently, Gora has support for persisting objects to various database models 
> such as Apache Hbase, Apache Cassandra and much more. [1] This project aims 
> to extend its capability to provide support for Apache Ignite database.
> Apache Ignite is a distributed database, caching and processing platform.[2] 
> [1]. [http://gora.apache.org/] 
> [2] . [https://ignite.apache.org/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-535:
--
Description: 
Currently, Gora has support persisting objects to various database models such 
as Apache Hbase, Apache Cassandra and much more. [1] This project aims to 
extend its capability to provide support for Apache Ignite database.

Apache Ignite is a distributed database, caching and processing platform.[2] 

[1]. [http://gora.apache.org/] 

[2] . [https://ignite.apache.org/]

 

  was:
Currently, Gora has support persisting objects to various database models such 
as Apache Hbase, Apache Cassandra and a whole lot. [1] This project aims to 
extend its capability to provide support for Aerospike database

Apache Ignite is a distributed database, caching and processing platform.[1] It 
will be useful to integrate Apache Ignite to Gora as a new backend. 

[1]. 

[1] . [https://ignite.apache.org/]

 


> Add a data store for Apache Ignite 
> ---
>
> Key: GORA-535
> URL: https://issues.apache.org/jira/browse/GORA-535
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Nishadi Kirielle
>Priority: Major
>  Labels: gsoc2018
>
> Currently, Gora has support persisting objects to various database models 
> such as Apache Hbase, Apache Cassandra and much more. [1] This project aims 
> to extend its capability to provide support for Apache Ignite database.
> Apache Ignite is a distributed database, caching and processing platform.[2] 
> [1]. [http://gora.apache.org/] 
> [2] . [https://ignite.apache.org/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-535:
--
Description: 
Currently, Gora has support persisting objects to various database models such 
as Apache Hbase, Apache Cassandra and a whole lot. [1] This project aims to 
extend its capability to provide support for Aerospike database

Apache Ignite is a distributed database, caching and processing platform.[1] It 
will be useful to integrate Apache Ignite to Gora as a new backend. 

[1]. 

[1] . [https://ignite.apache.org/]

 

  was:
Apache Ignite is a distributed database, caching and processing platform.[1] It 
will be useful to integrate Apache Ignite to Gora as a new backend. 

 

[1] . [https://ignite.apache.org/]

 


> Add a data store for Apache Ignite 
> ---
>
> Key: GORA-535
> URL: https://issues.apache.org/jira/browse/GORA-535
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Nishadi Kirielle
>Priority: Major
>  Labels: gsoc2018
>
> Currently, Gora has support persisting objects to various database models 
> such as Apache Hbase, Apache Cassandra and a whole lot. [1] This project aims 
> to extend its capability to provide support for Aerospike database
> Apache Ignite is a distributed database, caching and processing platform.[1] 
> It will be useful to integrate Apache Ignite to Gora as a new backend. 
> [1]. 
> [1] . [https://ignite.apache.org/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-535) Add a data store for Apache Ignite

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-535:
-

 Summary: Add a data store for Apache Ignite 
 Key: GORA-535
 URL: https://issues.apache.org/jira/browse/GORA-535
 Project: Apache Gora
  Issue Type: New Feature
Reporter: Nishadi Kirielle


Apache Ignite is a distributed database, caching and processing platform.[1] It 
will be useful to integrate Apache Ignite to Gora as a new backend. 

 

[1] . [https://ignite.apache.org/]

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GORA-524) Add batch writes to Aerospike module

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-524:
--
Description: 
Aerospike currently does not support batch[1] writes. When it is available, we 
can introduce batch writes functionality to improve the performance.

[1].[ http://www.aerospike.com/docs/guide/batch.html]

  was:Aerospike currently does not support 
batch[http://www.aerospike.com/docs/guide/batch.html] writes. When it is 
available, we can introduce batch writes functionality to improve the 
performance.


> Add batch writes to Aerospike module
> 
>
> Key: GORA-524
> URL: https://issues.apache.org/jira/browse/GORA-524
> Project: Apache Gora
>  Issue Type: Improvement
>Reporter: Nishadi Kirielle
>
> Aerospike currently does not support batch[1] writes. When it is available, 
> we can introduce batch writes functionality to improve the performance.
> [1].[ http://www.aerospike.com/docs/guide/batch.html]



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

[jira] [Created] (GORA-524) Add batch writes to Aerospike module

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-524:
-

 Summary: Add batch writes to Aerospike module
 Key: GORA-524
 URL: https://issues.apache.org/jira/browse/GORA-524
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle


Aerospike currently does not support 
batch[http://www.aerospike.com/docs/guide/batch.html] writes. When it is 
available, we can introduce batch writes functionality to improve the 
performance.



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

[jira] [Created] (GORA-523) Add map reduce based test cases to aerospike module

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-523:
-

 Summary: Add map reduce based test cases to aerospike module
 Key: GORA-523
 URL: https://issues.apache.org/jira/browse/GORA-523
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle


Map reduce based test cases need to be added to the aerospike module. 



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

[jira] [Created] (GORA-522) Fix the issue in PUT method of Aerospike

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-522:
-

 Summary: Fix the issue in PUT method of Aerospike
 Key: GORA-522
 URL: https://issues.apache.org/jira/browse/GORA-522
 Project: Apache Gora
  Issue Type: Bug
Reporter: Nishadi Kirielle
Assignee: Nishadi Kirielle


Currently, in the put method if the record is already existing in the data 
store, it directly deletes the whole record and adds the new record. In this 
way if only a single filed is updated, the existing data is lost. So this needs 
to be corrected. 




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

[jira] [Updated] (GORA-516) Document Aerospike Datastore at Apache Gora site.

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-516:
--
Attachment: aerospike-doc.patch

This patch has the aerospike based documentation changes for the gora 
documentation. 

> Document Aerospike Datastore at Apache Gora site.
> -
>
> Key: GORA-516
> URL: https://issues.apache.org/jira/browse/GORA-516
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-aerospike
>Reporter: Kevin Ratnasekera
>Assignee: Nishadi Kirielle
> Fix For: 0.8
>
> Attachments: aerospike-doc.patch
>
>
> This is related to adding Aerospike datastore content to [1]
> [1] http://svn.apache.org/repos/asf/gora/site/trunk/content/current/



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

[jira] [Created] (GORA-520) Add support to get partitions in Aerospike module

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-520:
-

 Summary: Add support to get partitions in Aerospike module
 Key: GORA-520
 URL: https://issues.apache.org/jira/browse/GORA-520
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle
Assignee: Nishadi Kirielle


Currently gora-aerospike module does not support to get the partitions as the 
query key ranges are not supported. But until the query key ranges are fixed, 
we can provide a single partitions as given by the mongo db store.



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

[jira] [Created] (GORA-519) Add support to access authenticated servers in Aerospike

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-519:
-

 Summary: Add support to access authenticated servers in Aerospike
 Key: GORA-519
 URL: https://issues.apache.org/jira/browse/GORA-519
 Project: Apache Gora
  Issue Type: New Feature
Reporter: Nishadi Kirielle
Assignee: Nishadi Kirielle


Currently, if the Aerospike server has restricted access with authentication 
needed for access, gora-aerospike module has no support to provide the 
credentials for the server.



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

[jira] [Created] (GORA-518) Upgrade the supported policies to the new client in Aerospike Store

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-518:
-

 Summary: Upgrade the supported  policies to the new client in 
Aerospike Store
 Key: GORA-518
 URL: https://issues.apache.org/jira/browse/GORA-518
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle
Assignee: Nishadi Kirielle


Currently, the supported policies in the Aerospike store are outdated with the 
Upgrade in the Aerospike java client. Thus the supported policies needs to be 
upgraded as to be compatible with the new java client. 



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

[jira] [Created] (GORA-515) Update the Aerospike client

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-515:
-

 Summary: Update the Aerospike client
 Key: GORA-515
 URL: https://issues.apache.org/jira/browse/GORA-515
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle
Assignee: Nishadi Kirielle


The currently used Aerospike version needs to be updated to the latest. 



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

[jira] [Comment Edited] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042183#comment-16042183
 ] 

Nishadi Kirielle edited comment on GORA-512 at 6/8/17 4:35 AM:
---

Hi all,
Thank you for looking into the issue.

[~alfonso.nishikawa] +1 for the suggestion of loading a 
not-matching-keyclass-mapping.xml to the configuration. That would be the best 
approach to capture the scenario.
[~djkevincr] [~kamaci] Illegal State Exception being a run-time exception 
terminates the execution without going further down in the call stack. That is 
the reason I have logged before throwing the exception. 
As all of you have suggested, the Illegal State Exception is not much 
descriptive for the scenario. So +1 for moving on with  ConfigurationException 
which is meaningful and provides insight to what has happened. This exception 
is provided through a javax.naming library as well [1]. IMHO, it would be 
better to use that exception without going for a custom exception. In that 
case, as it is not a runtime exception, I will avoid logging as suggested so 
that it would be caught at [2] and thrown as IOException, and again caught at 
[3] and thrown as RuntimeException as explained by [~alfonso.nishikawa]. 
Another approach would be to throw after the try/catch as suggested by 
[~kamaci]. 

Your opinions would be great on selecting which approach to choose.

[1]. 
https://docs.oracle.com/javase/7/docs/api/javax/naming/ConfigurationException.html
 
[2]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L808
[3]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L135


was (Author: nishadi):
Hi all,
Thank you for looking into the issue.

[~alfonso.nishikawa] +1 for the suggestion of loading a 
not-matching-keyclass-mapping.xml to the configuration. That would be the best 
approach to capture the scenario.
[~djkevincr] [~kamaci] Illegal State Exception being a run-time exception 
terminates the execution without going further down in the call stack. That is 
the reason I have logged before throwing the exception. 
As all of you have suggested, the Illegal State Exception is not much 
descriptive for the scenario. So +1 for moving on with  ConfigurationException 
which is meaningful and provides insight to what has happened. This exception 
is provided through a javax.naming library as well [1]. IMHO, it would be 
better to use that exception without going for a custom exception. In that 
case, as it is not a runtime exception, I will avoid logging as suggested so 
that it would be caught at caught at [2] and thrown as IOException, and again 
at [3] and thrown as RuntimeException as explained by [~alfonso.nishikawa]. 
Another approach would be to throw after the try/catch as suggested by 
[~kamaci]. 

Your opinions would be great on selecting which approach to choose.

[1]. 
https://docs.oracle.com/javase/7/docs/api/javax/naming/ConfigurationException.html
 
[2]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L808
[3]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L135

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Nishadi Kirielle
>Assignee: Nishadi Kirielle
>Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



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

[jira] [Commented] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042183#comment-16042183
 ] 

Nishadi Kirielle commented on GORA-512:
---

Hi all,
Thank you for looking into the issue.

[~alfonso.nishikawa] +1 for the suggestion of loading a 
not-matching-keyclass-mapping.xml to the configuration. That would be the best 
approach to capture the scenario.
[~djkevincr] [~kamaci] Illegal State Exception being a run-time exception 
terminates the execution without going further down in the call stack. That is 
the reason I have logged before throwing the exception. 
As all of you have suggested, the Illegal State Exception is not much 
descriptive for the scenario. So +1 for moving on with  ConfigurationException 
which is meaningful and provides insight to what has happened. This exception 
is provided through a javax.naming library as well [1]. IMHO, it would be 
better to use that exception without going for a custom exception. In that 
case, as it is not a runtime exception, I will avoid logging as suggested so 
that it would be caught at caught at [2] and thrown as IOException, and again 
at [3] and thrown as RuntimeException as explained by [~alfonso.nishikawa]. 
Another approach would be to throw after the try/catch as suggested by 
[~kamaci]. 

Your opinions would be great on selecting which approach to choose.

[1]. 
https://docs.oracle.com/javase/7/docs/api/javax/naming/ConfigurationException.html
 
[2]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L808
[3]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L135

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Nishadi Kirielle
>Assignee: Nishadi Kirielle
>Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



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

[jira] [Commented] (GORA-255) Remove deprecated methods from DataStoreTestBase

[Nishadi Kirielle (JIRA)]

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

Nishadi Kirielle commented on GORA-255:
---

Thank you for the suggested approach. 
I will go ahead with implementing MemStoreTestDriver, remove the deprecated 
methods and will send the PR.

> Remove deprecated methods from DataStoreTestBase 
> -
>
> Key: GORA-255
> URL: https://issues.apache.org/jira/browse/GORA-255
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: testing
>Affects Versions: 0.4
>Reporter: Apostolos Giannakidis
>Assignee: Apostolos Giannakidis
>Priority: Minor
>  Labels: test
> Fix For: 0.8
>
>
> The abstract class DataStoreTestBase contains 2 deprecated methods:
> DataStore createEmployeeDataStore()
> DataStore createWebPageDataStore()
> These methods were useful in the past but they seem not to be useful now.
> I believe that they should be removed from the abstract class 
> DataStoreTestBase. Their concrete implementations from the subclasses that 
> extend the DataStoreTestBase should also be removed.



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

[jira] [Commented] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033430#comment-16033430
 ] 

Nishadi Kirielle commented on GORA-512:
---

Hi all,
The following fix is done to fail the execution if the gora-hbase-mapping file 
does not include keyClass and name defined in the data bean. [1]
I tried to create a test case to capture the erroneous scenario. In order to 
test this scenario, gora-hbase-mapping keyClass and name should be mismatched 
with the data bean. Currently TestHBaseStore's data beans and 
gora-hbase-mapping files are matching as to run the existing test cases. As we 
do not have the ability to load two separate gora-hbase-mapping files to 
support normal test execution and erroneous test execution, will that be 
possible to add this test case to the current existing test suite, 
TestHBaseStore ?


[1]. 
https://github.com/nishadi/gora/commit/45cca68b98fe8dc68d74d671e29341d469831f88 

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Nishadi Kirielle
>Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



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

[jira] [Commented] (GORA-255) Remove deprecated methods from DataStoreTestBase

[Nishadi Kirielle (JIRA)]

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

Nishadi Kirielle commented on GORA-255:
---

Hi, 
Thank you for the responses. 
If we are to remove those methods, we will need to create  MemStoreTestDriver 
to retain that functionality.
But will it be meaningful to create the test drive for MemStore just because we 
need to initialize the data stores of employee and web store DataStores. AFAIU, 
GoraTestDriver [1] is a helper class for managing third party tests, but 
MemStoreTest won't be having any third party tests.  
Your suggestions on this will be really helpful. 
Thank you!
[1]. 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-core/src/test/java/org/apache/gora/GoraTestDriver.java#L38

> Remove deprecated methods from DataStoreTestBase 
> -
>
> Key: GORA-255
> URL: https://issues.apache.org/jira/browse/GORA-255
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: testing
>Affects Versions: 0.4
>Reporter: Apostolos Giannakidis
>Assignee: Apostolos Giannakidis
>Priority: Minor
>  Labels: test
> Fix For: 0.8
>
>
> The abstract class DataStoreTestBase contains 2 deprecated methods:
> DataStore createEmployeeDataStore()
> DataStore createWebPageDataStore()
> These methods were useful in the past but they seem not to be useful now.
> I believe that they should be removed from the abstract class 
> DataStoreTestBase. Their concrete implementations from the subclasses that 
> extend the DataStoreTestBase should also be removed.



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

[jira] [Updated] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-512:
--
Component/s: gora-hbase

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Nishadi Kirielle
>Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



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

[jira] [Updated] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-512:
--
Description: 
In the current implementation, when reading the HBase mapping file, if the 
HBase mapping file does not have a matching key class and name to the data 
bean, it only logs that information.[1] It does not fail at the time of 
detecting it. It fails only at the time of building the mapper [2] when it 
detects the table name is null. It will be better if it can fail at the time of 
detecting that mapping file is missing the corresponding class. 

[1]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
[2]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815


  was:
In the current implementation, when reading the HBase mapping file, if the 
HBase mapping file does not have a matching key class and name to the data 
bean, it only logs that information.[1] It does not fails at the time of 
detecting it. It fails only at the time of building the mapper [2] when it 
detects the table name is null. 

[1]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
[2]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>Reporter: Nishadi Kirielle
>Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



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

[jira] [Created] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Nishadi Kirielle (JIRA)]

Nishadi Kirielle created GORA-512:
-

 Summary: Fail at the time of error logging if KeyClass in 
gora-hbase-mapping is not the same as the one in the data bean
 Key: GORA-512
 URL: https://issues.apache.org/jira/browse/GORA-512
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Nishadi Kirielle
Priority: Minor


In the current implementation, when reading the HBase mapping file, if the 
HBase mapping file does not have a matching key class and name to the data 
bean, it only logs that information.[1] It does not fails at the time of 
detecting it. It fails only at the time of building the mapper [2] when it 
detects the table name is null. 

[1]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
[2]. 
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815




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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953721#comment-15953721
 ] 

Nishadi Kirielle commented on GORA-502:
---

Yes I have updated the wiki

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950399#comment-15950399
 ] 

Nishadi Kirielle commented on GORA-502:
---

Hi [~lewismc],

My wiki user name is nishadi.k

Thank you

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949656#comment-15949656
 ] 

Nishadi Kirielle commented on GORA-502:
---

Hi, 
[~kamaci] and [~lewismc], I have implemented an initial basic prototype for the 
project [1] and
tested for its functionality with the log manager example's parsing
functionality. The prototype has the ability to connect with the Aerospike
server, execute the put method [2] and add records to the Aerospike
database. The database names and table names are hard coded as per the
moment as the support for the mapping file is not yet implemented. In
addition I have drafted the initial project proposal in the following
google doc [3] as I was unable to edit the provided wiki page.

I am grateful, if you can provide me with feedback on the proposal and the
prototype.

[1].
https://github.com/nishadi/gora/blob/gora-aerospike/gora-aerospike/src/main/java/org/apache/gora/aerospike/store/AerospikeStore.java
[2].
https://github.com/nishadi/gora/blob/gora-aerospike/gora-aerospike/src/main/java/org/apache/gora/aerospike/store/AerospikeStore.java#L94
[3].
https://docs.google.com/document/d/1FLRlG8h5M3GA4Wn1tsbWXkYSE0navl_WEmp-KDEKtfU/edit?usp=sharing

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906417#comment-15906417
 ] 

Nishadi Kirielle commented on GORA-502:
---

Hi, yes I have started working on it.

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895609#comment-15895609
 ] 

Nishadi Kirielle commented on GORA-502:
---

Hi,
I am Nishadi Kirielle, a final year undergraduate of Computer Science and 
Engineering department from University of Moratuwa. 
I am interested in contributing to the project as I am familiar with working 
with in-memory databases. As part of my final year project, I have created an 
extension to Apache spark SQL to incorporate bitmap compression for data 
manipulations. 
As per my understanding the requirement is to develop a new datastore adapter 
implementation of Aerospike which can be used if required by changing the 
configuration of Gora via gora.datastore.default property [1] 
It would be great if you can guide me with the required references and guide 
lines.
[1]. http://gora.apache.org/current/gora-conf.html

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Issue Comment Deleted] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishadi Kirielle updated GORA-502:
--
Comment: was deleted

(was: Hi,
I am Nishadi Kirielle, a final year undergraduate of Computer Science and 
Engineering department from University of Moratuwa. 
I am interested in contributing to the project as I am familiar with working 
with in-memory databases. As part of my final year project, I have created an 
extension to Apache spark SQL to incorporate bitmap compression for data 
manipulations. 
As per my understanding the requrement is to develop a new datastore adaptor 
implementation of Aerospike which can be used if required by changing the 
configuration of Gora via gora.datastore.default property [1] 
It would be great if you can guide me with the required references and guide 
lines.

[1]. http://gora.apache.org/current/gora-conf.html)

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Nishadi Kirielle (JIRA)]

[ 
https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895607#comment-15895607
 ] 

Nishadi Kirielle commented on GORA-502:
---

Hi,
I am Nishadi Kirielle, a final year undergraduate of Computer Science and 
Engineering department from University of Moratuwa. 
I am interested in contributing to the project as I am familiar with working 
with in-memory databases. As part of my final year project, I have created an 
extension to Apache spark SQL to incorporate bitmap compression for data 
manipulations. 
As per my understanding the requrement is to develop a new datastore adaptor 
implementation of Aerospike which can be used if required by changing the 
configuration of Gora via gora.datastore.default property [1] 
It would be great if you can guide me with the required references and guide 
lines.

[1]. http://gora.apache.org/current/gora-conf.html

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>  Labels: gsoc2017
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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