[GitHub] [gora] cuent commented on issue #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on issue #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186#issuecomment-553015303
 
 
   Hi, sorry, I haven't been with my laptop in almost the past month. I am just 
checking the status of the PR. Was it merged? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on issue #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on issue #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186#issuecomment-544896356
 
 
   There s updated PR available in https://github.com/apache/gora/pull/198 and 
merged. Hence closing the PR.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr closed pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr closed pull request #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr merged pull request #198: [GORA-527] Redis Datastore

[GitBox]

djkevincr merged pull request #198: [GORA-527] Redis Datastore
URL: https://github.com/apache/gora/pull/198
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr opened a new pull request #198: [GORA-527] Redis Datastore

[GitBox]

djkevincr opened a new pull request #198: [GORA-527] Redis Datastore
URL: https://github.com/apache/gora/pull/198
 
 
   Took over from https://github.com/apache/gora/pull/186 and resolved 
conflicts as well as test failures. Preserved commit history.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on issue #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on issue #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186#issuecomment-544815187
 
 
   @cuent Can you please resolve the conflicts?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on issue #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on issue #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186#issuecomment-531488717
 
 
   @cuent Can you please take up from master branch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on issue #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on issue #186: [GORA-527] Implement Redis datastore 
URL: https://github.com/apache/gora/pull/186#issuecomment-526448022
 
 
   @cuent Can you please take an update with current master? Your PR has 
conflicts.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on a change in pull request #186: [GORA-527] Implement 
Redis datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r317904794
 
 

 ##
 File path: pom.xml
 ##
 @@ -845,7 +848,7 @@
 2.8.1
 1.4
 0.8
-3.1.1
+2.5.4
 
 Review comment:
   This is not yet addressed in your PR.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] djkevincr commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

djkevincr commented on a change in pull request #186: [GORA-527] Implement 
Redis datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r317904954
 
 

 ##
 File path: pom.xml
 ##
 @@ -382,7 +382,7 @@
 
   
   
-posix
+gnu
 
 Review comment:
   This is not yet addressed.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] cuent commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on a change in pull request #186: [GORA-527] Implement Redis 
datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r316762082
 
 

 ##
 File path: 
gora-redis/src/main/java/org/apache/gora/redis/query/RedisResult.java
 ##
 @@ -0,0 +1,111 @@
+/**
+ * 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.gora.redis.query;
+
+import java.io.IOException;
+import java.util.Collection;
+import java.util.Iterator;
+import org.apache.gora.persistency.impl.PersistentBase;
+import org.apache.gora.query.Query;
+import org.apache.gora.query.impl.ResultBase;
+import org.apache.gora.redis.store.RedisStore;
+import org.apache.gora.store.DataStore;
+
+/**
+ * Redis specific implementation of the {@link org.apache.gora.query.Result}
+ * interface.
+ */
+public class RedisResult extends ResultBase 
{
+
+  private Iterator range;
+  private final int size;
+
+  /**
+   * Gets the data store used
+   *
+   * @return
+   */
+  @Override
+  public RedisStore getDataStore() {
+return (RedisStore) super.getDataStore();
+  }
+
+  /**
+   * @param dataStore
+   * @param query
+   * @param rg
+   */
+  public RedisResult(DataStore dataStore, Query query, 
Collection rg) {//, Scanner scanner) {
+super(dataStore, query);
+this.size = rg.size();
+this.range = rg.iterator();
+  }
+
+  /**
+   * Gets the items reading progress
+   *
+   * @return
+   * @throws java.io.IOException
+   */
+  @Override
+  public float getProgress() throws IOException {
+if (this.limit != -1) {
+  return (float) this.offset / (float) this.limit;
+} else {
+  return 0;
+}
+  }
+
+  @Override
+  public void close() throws IOException {
+  }
+
+  /**
+   * Gets the next item
+   *
+   * @return
+   * @throws java.io.IOException
+   */
+  @Override
+  protected boolean nextInner() throws IOException {
+if (range == null) {
+  return false;
+}
+boolean next = range.hasNext();
+if (next) {
+  String nextkey = range.next();
+  key = (K) nextkey;
 
 Review comment:
   Support for the new index (ScoredSortedList) is part of the last commit
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] cuent commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on a change in pull request #186: [GORA-527] Implement Redis 
datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r316688662
 
 

 ##
 File path: pom.xml
 ##
 @@ -1061,7 +1064,37 @@
 ${flink.version}
 compile
   
-
+  
+  
+  
+org.apache.gora
+gora-redis
+${project.version}
+  
+  
+org.apache.gora
+gora-redis
+${project.version}
+test-jar
+  
+  
+org.redisson
+redisson-all
+${redisson.version}
+
+  
+org.apache.spark
+spark-core_2.11
 
 Review comment:
   yeah, maybe I duplicated by accident while I was trying to fix the issues 
with the hashes and rebase. I just remove it


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] cuent commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on a change in pull request #186: [GORA-527] Implement Redis 
datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r316685760
 
 

 ##
 File path: pom.xml
 ##
 @@ -382,7 +382,7 @@
 
   
   
-posix
+gnu
 
 Review comment:
   up to date with master 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] cuent commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on a change in pull request #186: [GORA-527] Implement Redis 
datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r316684886
 
 

 ##
 File path: pom.xml
 ##
 @@ -382,7 +382,7 @@
 
   
   
-posix
+gnu
 
 Review comment:
   up to date with master


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [gora] cuent commented on a change in pull request #186: [GORA-527] Implement Redis datastore

[GitBox]

cuent commented on a change in pull request #186: [GORA-527] Implement Redis 
datastore 
URL: https://github.com/apache/gora/pull/186#discussion_r316684736
 
 

 ##
 File path: pom.xml
 ##
 @@ -845,7 +848,7 @@
 2.8.1
 1.4
 0.8
-3.1.1
+2.5.4
 
 Review comment:
   Yes, I miss this one. Up to date with master now! :smile: 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Thanks Carlos.

I will look into aerospike and update the question to the report.

Best,
Xavier.



On Mon, Jun 17, 2019, 11:26 PM carlos muñoz,  wrote:

> Hi Xavier,
>
> IMHO, it would be okay to ignore these methods, this case is similar to
> Aerospike, give a look to [1]. Also, you may have to ignore the schema
> related tests[2].
>
> [1]
>
> https://github.com/apache/gora/blob/master/gora-aerospike/src/main/java/org/apache/gora/aerospike/store/AerospikeStore.java#L130
>
> [2]
>
> https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/store/TestAerospikeStore.java#L117
>
>
> My two cents,
>
> Cheers,
> Carlos
>
> El dom., 16 jun. 2019 a las 23:29, FRANCISCO XAVIER SUMBA TORAL
> () escribió:
>
> > Hello Madhawa,
> >
> > Thanks for your comment. Yeah, I will address that this week. And I have
> a
> > question:
> >
> > Redis doesn't have a schema as other data stores, so is it okay to leave
> > functions such as createSchema, deleteSchema y schemaExists with no
> > implementation?
> >
> > Best,
> > Xavier.
> >
> > > On Jun 15, 2019, at 16:03, Madhawa Kasun Gunasekara <
> madhaw...@gmail.com>
> > wrote:
> > >
> > > Hi Xavier,
> > >
> > > You should consider other data types also, not only Hashes. [1]
> Sometimes
> > > users like to store data in String data type as well. Please check on
> > that
> > > as well
> > >
> > > [1] https://redis.io/topics/data-types
> > >
> > > Thanks,
> > > Madhawa
> > >
> > >
> > > On Sat, Jun 15, 2019 at 8:20 PM FRANCISCO XAVIER SUMBA TORAL
> > >  wrote:
> > >
> > >> Hello,
> > >>
> > >> My weekly report is updated on the wiki. Also, I moved all the code
> from
> > >> master the branch GORA-527. And did the following tasks.
> > >>
> > >> Port to test containers (Docker redis)
> > >> Add connections mode configuration (cluster, replicated, …)
> > >> Implement put, exists, get, delete
> > >> Fix Alfonso comments (reading configuration file as in HBase)
> > >>
> > >> Best,
> > >> Xavier.
> > >>
> > >>> On Jun 10, 2019, at 22:53, FRANCISCO XAVIER SUMBA TORAL <
> > >> xavier.sumb...@ucuenca.edu.ec> wrote:
> > >>>
> > >>> Thanks Alonso for your comments.
> > >>>
> > >>> I will analyze the code from HBase. Thanks for your suggestion…
> > >>>
> > >>> Also, my code is in master, but I will move to the branch 527, it
> will
> > >> be easier to trace changes.
> > >>>
> > >>>
> > >>> Best,
> > >>> Xavier.
> > >>>
> >  On Jun 10, 2019, at 18:20, Alfonso Nishikawa <
> > >> alfonso.nishik...@gmail.com> wrote:
> > 
> >  Hi, Xavier.
> > 
> >  I don't see your branch GORA-527 told in your report.
> >  What I would want to ask for is to add the same functionality to
> load
> > >> the
> >  mapping from configuration in you RedisStore [1] as in HBase's store
> > >> [2].
> >  This will have implications on your readMapping that in HBase was
> done
> > >> by
> >  passing an InputStream instead of a file name.
> > 
> >  [1] -
> > 
> > >>
> >
> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
> >  [2] -
> > 
> > >>
> >
> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
> > 
> >  Regards,
> > 
> >  Alfonso Nishikawa
> > 
> >  El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
> >  () escribió:
> > 
> > > Thanks for your comments.
> > >
> > > I pushed my commits and updated the report.
> > >
> > > During this week I want to decide what redisson codec works best
> for
> > > gora’s use case and I will also solve the comments of the libraries
> > > comparison.  I will keep updating you guys during the week any
> > blocker
> > >> or
> > > new tasks that come along.
> > >
> > >
> > > Best,
> > > Xavier.
> > >
> > >
> > >> On Jun 9, 2019, at 23:43, carlos muñoz 
> > wrote:
> > >>
> > >> Hi Xavier
> > >>
> > >> The document looks great. I have left a few comments. I would like
> > to
> > > read
> > >> other valorations .
> > >> Also, please make sure to publish your weekly process on the Wiki
> > >> space.
> > >>
> > >> Regards,
> > >> Carlos
> > >>
> > >> El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
> > >> () escribió:
> > >>
> > >>> Sorry, try again. Anybody should be able to access? I set for
> > >> everyone.
> > >>>
> > >>>
> > >>>
> > >
> > >>
> >
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
> > >>>
> > >>>
> > >>> Best,
> > >>> Xavier
> >  On Jun 7, 2019, at 23:59, Kevin Ratnasekera <
> > >> djkevincr1...@gmail.com>
> > >>> wrote:
> > 
> >  Hi Xavier,
> > 
> >  I requested access to the docs. Can you please give permissions?
> > 
> >  Regards
> > 

Re: Redis datastore

[carlos muñoz]

Hi Xavier,

IMHO, it would be okay to ignore these methods, this case is similar to
Aerospike, give a look to [1]. Also, you may have to ignore the schema
related tests[2].

[1]
https://github.com/apache/gora/blob/master/gora-aerospike/src/main/java/org/apache/gora/aerospike/store/AerospikeStore.java#L130

[2]
https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/store/TestAerospikeStore.java#L117


My two cents,

Cheers,
Carlos

El dom., 16 jun. 2019 a las 23:29, FRANCISCO XAVIER SUMBA TORAL
() escribió:

> Hello Madhawa,
>
> Thanks for your comment. Yeah, I will address that this week. And I have a
> question:
>
> Redis doesn't have a schema as other data stores, so is it okay to leave
> functions such as createSchema, deleteSchema y schemaExists with no
> implementation?
>
> Best,
> Xavier.
>
> > On Jun 15, 2019, at 16:03, Madhawa Kasun Gunasekara 
> wrote:
> >
> > Hi Xavier,
> >
> > You should consider other data types also, not only Hashes. [1] Sometimes
> > users like to store data in String data type as well. Please check on
> that
> > as well
> >
> > [1] https://redis.io/topics/data-types
> >
> > Thanks,
> > Madhawa
> >
> >
> > On Sat, Jun 15, 2019 at 8:20 PM FRANCISCO XAVIER SUMBA TORAL
> >  wrote:
> >
> >> Hello,
> >>
> >> My weekly report is updated on the wiki. Also, I moved all the code from
> >> master the branch GORA-527. And did the following tasks.
> >>
> >> Port to test containers (Docker redis)
> >> Add connections mode configuration (cluster, replicated, …)
> >> Implement put, exists, get, delete
> >> Fix Alfonso comments (reading configuration file as in HBase)
> >>
> >> Best,
> >> Xavier.
> >>
> >>> On Jun 10, 2019, at 22:53, FRANCISCO XAVIER SUMBA TORAL <
> >> xavier.sumb...@ucuenca.edu.ec> wrote:
> >>>
> >>> Thanks Alonso for your comments.
> >>>
> >>> I will analyze the code from HBase. Thanks for your suggestion…
> >>>
> >>> Also, my code is in master, but I will move to the branch 527, it will
> >> be easier to trace changes.
> >>>
> >>>
> >>> Best,
> >>> Xavier.
> >>>
>  On Jun 10, 2019, at 18:20, Alfonso Nishikawa <
> >> alfonso.nishik...@gmail.com> wrote:
> 
>  Hi, Xavier.
> 
>  I don't see your branch GORA-527 told in your report.
>  What I would want to ask for is to add the same functionality to load
> >> the
>  mapping from configuration in you RedisStore [1] as in HBase's store
> >> [2].
>  This will have implications on your readMapping that in HBase was done
> >> by
>  passing an InputStream instead of a file name.
> 
>  [1] -
> 
> >>
> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
>  [2] -
> 
> >>
> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
> 
>  Regards,
> 
>  Alfonso Nishikawa
> 
>  El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
>  () escribió:
> 
> > Thanks for your comments.
> >
> > I pushed my commits and updated the report.
> >
> > During this week I want to decide what redisson codec works best for
> > gora’s use case and I will also solve the comments of the libraries
> > comparison.  I will keep updating you guys during the week any
> blocker
> >> or
> > new tasks that come along.
> >
> >
> > Best,
> > Xavier.
> >
> >
> >> On Jun 9, 2019, at 23:43, carlos muñoz 
> wrote:
> >>
> >> Hi Xavier
> >>
> >> The document looks great. I have left a few comments. I would like
> to
> > read
> >> other valorations .
> >> Also, please make sure to publish your weekly process on the Wiki
> >> space.
> >>
> >> Regards,
> >> Carlos
> >>
> >> El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
> >> () escribió:
> >>
> >>> Sorry, try again. Anybody should be able to access? I set for
> >> everyone.
> >>>
> >>>
> >>>
> >
> >>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
> >>>
> >>>
> >>> Best,
> >>> Xavier
>  On Jun 7, 2019, at 23:59, Kevin Ratnasekera <
> >> djkevincr1...@gmail.com>
> >>> wrote:
> 
>  Hi Xavier,
> 
>  I requested access to the docs. Can you please give permissions?
> 
>  Regards
>  Kevin
> 
>  On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
>   wrote:
> 
> > Hello
> >
> > I think that redisson is the option to support redis in gora.
> >
> > There is an analysis here [1]. What do you think? After some
> >>> suggestions I
> > can add those results to the wiki.
> >
> > Best
> > Xavier
> >
> > [1]
> >
> >
> >>>
> >
> >>
> 

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Hello Madhawa,

Thanks for your comment. Yeah, I will address that this week. And I have a 
question:

Redis doesn't have a schema as other data stores, so is it okay to leave 
functions such as createSchema, deleteSchema y schemaExists with no 
implementation?

Best,
Xavier.

> On Jun 15, 2019, at 16:03, Madhawa Kasun Gunasekara  
> wrote:
> 
> Hi Xavier,
> 
> You should consider other data types also, not only Hashes. [1] Sometimes
> users like to store data in String data type as well. Please check on that
> as well
> 
> [1] https://redis.io/topics/data-types
> 
> Thanks,
> Madhawa
> 
> 
> On Sat, Jun 15, 2019 at 8:20 PM FRANCISCO XAVIER SUMBA TORAL
>  wrote:
> 
>> Hello,
>> 
>> My weekly report is updated on the wiki. Also, I moved all the code from
>> master the branch GORA-527. And did the following tasks.
>> 
>> Port to test containers (Docker redis)
>> Add connections mode configuration (cluster, replicated, …)
>> Implement put, exists, get, delete
>> Fix Alfonso comments (reading configuration file as in HBase)
>> 
>> Best,
>> Xavier.
>> 
>>> On Jun 10, 2019, at 22:53, FRANCISCO XAVIER SUMBA TORAL <
>> xavier.sumb...@ucuenca.edu.ec> wrote:
>>> 
>>> Thanks Alonso for your comments.
>>> 
>>> I will analyze the code from HBase. Thanks for your suggestion…
>>> 
>>> Also, my code is in master, but I will move to the branch 527, it will
>> be easier to trace changes.
>>> 
>>> 
>>> Best,
>>> Xavier.
>>> 
 On Jun 10, 2019, at 18:20, Alfonso Nishikawa <
>> alfonso.nishik...@gmail.com> wrote:
 
 Hi, Xavier.
 
 I don't see your branch GORA-527 told in your report.
 What I would want to ask for is to add the same functionality to load
>> the
 mapping from configuration in you RedisStore [1] as in HBase's store
>> [2].
 This will have implications on your readMapping that in HBase was done
>> by
 passing an InputStream instead of a file name.
 
 [1] -
 
>> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
 [2] -
 
>> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
 
 Regards,
 
 Alfonso Nishikawa
 
 El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
 () escribió:
 
> Thanks for your comments.
> 
> I pushed my commits and updated the report.
> 
> During this week I want to decide what redisson codec works best for
> gora’s use case and I will also solve the comments of the libraries
> comparison.  I will keep updating you guys during the week any blocker
>> or
> new tasks that come along.
> 
> 
> Best,
> Xavier.
> 
> 
>> On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
>> 
>> Hi Xavier
>> 
>> The document looks great. I have left a few comments. I would like to
> read
>> other valorations .
>> Also, please make sure to publish your weekly process on the Wiki
>> space.
>> 
>> Regards,
>> Carlos
>> 
>> El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
>> () escribió:
>> 
>>> Sorry, try again. Anybody should be able to access? I set for
>> everyone.
>>> 
>>> 
>>> 
> 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
>>> 
>>> 
>>> Best,
>>> Xavier
 On Jun 7, 2019, at 23:59, Kevin Ratnasekera <
>> djkevincr1...@gmail.com>
>>> wrote:
 
 Hi Xavier,
 
 I requested access to the docs. Can you please give permissions?
 
 Regards
 Kevin
 
 On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
  wrote:
 
> Hello
> 
> I think that redisson is the option to support redis in gora.
> 
> There is an analysis here [1]. What do you think? After some
>>> suggestions I
> can add those results to the wiki.
> 
> Best
> Xavier
> 
> [1]
> 
> 
>>> 
> 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
> 
> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
> xavier.sumb...@ucuenca.edu.ec> wrote:
> 
>> 
>> 
>> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
>>> djkevincr1...@gmail.com
>> 
>> wrote:
>> 
>>> Hi Xavier,
>>> 
>>> Thank you for the update. Take your time on the research for
> selecting
> the
>>> Redis client library, you dont need to compare all Redis clients,
>>> take a
>>> subset/few looks most promising ( by comparing community,
>>> functionality
>>> etc
>>> ). There are only very few recommended from redis.io. [1] (
>> Jedis,
>>> 

Re: Redis datastore

[Madhawa Kasun Gunasekara]

Hi Xavier,

You should consider other data types also, not only Hashes. [1] Sometimes
users like to store data in String data type as well. Please check on that
as well

[1] https://redis.io/topics/data-types

Thanks,
Madhawa


On Sat, Jun 15, 2019 at 8:20 PM FRANCISCO XAVIER SUMBA TORAL
 wrote:

> Hello,
>
> My weekly report is updated on the wiki. Also, I moved all the code from
> master the branch GORA-527. And did the following tasks.
>
> Port to test containers (Docker redis)
> Add connections mode configuration (cluster, replicated, …)
> Implement put, exists, get, delete
> Fix Alfonso comments (reading configuration file as in HBase)
>
> Best,
> Xavier.
>
> > On Jun 10, 2019, at 22:53, FRANCISCO XAVIER SUMBA TORAL <
> xavier.sumb...@ucuenca.edu.ec> wrote:
> >
> > Thanks Alonso for your comments.
> >
> > I will analyze the code from HBase. Thanks for your suggestion…
> >
> > Also, my code is in master, but I will move to the branch 527, it will
> be easier to trace changes.
> >
> >
> > Best,
> > Xavier.
> >
> >> On Jun 10, 2019, at 18:20, Alfonso Nishikawa <
> alfonso.nishik...@gmail.com> wrote:
> >>
> >> Hi, Xavier.
> >>
> >> I don't see your branch GORA-527 told in your report.
> >> What I would want to ask for is to add the same functionality to load
> the
> >> mapping from configuration in you RedisStore [1] as in HBase's store
> [2].
> >> This will have implications on your readMapping that in HBase was done
> by
> >> passing an InputStream instead of a file name.
> >>
> >> [1] -
> >>
> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
> >> [2] -
> >>
> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
> >>
> >> Regards,
> >>
> >> Alfonso Nishikawa
> >>
> >> El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
> >> () escribió:
> >>
> >>> Thanks for your comments.
> >>>
> >>> I pushed my commits and updated the report.
> >>>
> >>> During this week I want to decide what redisson codec works best for
> >>> gora’s use case and I will also solve the comments of the libraries
> >>> comparison.  I will keep updating you guys during the week any blocker
> or
> >>> new tasks that come along.
> >>>
> >>>
> >>> Best,
> >>> Xavier.
> >>>
> >>>
>  On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
> 
>  Hi Xavier
> 
>  The document looks great. I have left a few comments. I would like to
> >>> read
>  other valorations .
>  Also, please make sure to publish your weekly process on the Wiki
> space.
> 
>  Regards,
>  Carlos
> 
>  El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
>  () escribió:
> 
> > Sorry, try again. Anybody should be able to access? I set for
> everyone.
> >
> >
> >
> >>>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
> >
> >
> > Best,
> > Xavier
> >> On Jun 7, 2019, at 23:59, Kevin Ratnasekera <
> djkevincr1...@gmail.com>
> > wrote:
> >>
> >> Hi Xavier,
> >>
> >> I requested access to the docs. Can you please give permissions?
> >>
> >> Regards
> >> Kevin
> >>
> >> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
> >>  wrote:
> >>
> >>> Hello
> >>>
> >>> I think that redisson is the option to support redis in gora.
> >>>
> >>> There is an analysis here [1]. What do you think? After some
> > suggestions I
> >>> can add those results to the wiki.
> >>>
> >>> Best
> >>> Xavier
> >>>
> >>> [1]
> >>>
> >>>
> >
> >>>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
> >>>
> >>> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
> >>> xavier.sumb...@ucuenca.edu.ec> wrote:
> >>>
> 
> 
>  On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
> > djkevincr1...@gmail.com
> 
>  wrote:
> 
> > Hi Xavier,
> >
> > Thank you for the update. Take your time on the research for
> >>> selecting
> >>> the
> > Redis client library, you dont need to compare all Redis clients,
> > take a
> > subset/few looks most promising ( by comparing community,
> > functionality
> > etc
> > ). There are only very few recommended from redis.io. [1] (
> Jedis,
> > Lettuce
> > and Redisson ) Let's focus on these 3, about high lever data
> > structures
> > etc. Let s do a comparison once you complete that research work.
> >
> 
>  Okay, I will work on that comparison.
> 
> 
> 
> 
> > As Carlos mentioned, If you do have troubles setting up embedded
> > server,
> > you could always use [1] to spin up Redis server instance from
> >>> 

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Hello,

My weekly report is updated on the wiki. Also, I moved all the code from master 
the branch GORA-527. And did the following tasks.

Port to test containers (Docker redis) 
Add connections mode configuration (cluster, replicated, …) 
Implement put, exists, get, delete 
Fix Alfonso comments (reading configuration file as in HBase)

Best,
Xavier.

> On Jun 10, 2019, at 22:53, FRANCISCO XAVIER SUMBA TORAL 
>  wrote:
> 
> Thanks Alonso for your comments. 
> 
> I will analyze the code from HBase. Thanks for your suggestion… 
> 
> Also, my code is in master, but I will move to the branch 527, it will be 
> easier to trace changes. 
> 
> 
> Best,
> Xavier.
> 
>> On Jun 10, 2019, at 18:20, Alfonso Nishikawa  
>> wrote:
>> 
>> Hi, Xavier.
>> 
>> I don't see your branch GORA-527 told in your report.
>> What I would want to ask for is to add the same functionality to load the
>> mapping from configuration in you RedisStore [1] as in HBase's store [2].
>> This will have implications on your readMapping that in HBase was done by
>> passing an InputStream instead of a file name.
>> 
>> [1] -
>> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
>> [2] -
>> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
>> 
>> Regards,
>> 
>> Alfonso Nishikawa
>> 
>> El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
>> () escribió:
>> 
>>> Thanks for your comments.
>>> 
>>> I pushed my commits and updated the report.
>>> 
>>> During this week I want to decide what redisson codec works best for
>>> gora’s use case and I will also solve the comments of the libraries
>>> comparison.  I will keep updating you guys during the week any blocker or
>>> new tasks that come along.
>>> 
>>> 
>>> Best,
>>> Xavier.
>>> 
>>> 
 On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
 
 Hi Xavier
 
 The document looks great. I have left a few comments. I would like to
>>> read
 other valorations .
 Also, please make sure to publish your weekly process on the Wiki space.
 
 Regards,
 Carlos
 
 El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
 () escribió:
 
> Sorry, try again. Anybody should be able to access? I set for everyone.
> 
> 
> 
>>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
> 
> 
> Best,
> Xavier
>> On Jun 7, 2019, at 23:59, Kevin Ratnasekera 
> wrote:
>> 
>> Hi Xavier,
>> 
>> I requested access to the docs. Can you please give permissions?
>> 
>> Regards
>> Kevin
>> 
>> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
>>  wrote:
>> 
>>> Hello
>>> 
>>> I think that redisson is the option to support redis in gora.
>>> 
>>> There is an analysis here [1]. What do you think? After some
> suggestions I
>>> can add those results to the wiki.
>>> 
>>> Best
>>> Xavier
>>> 
>>> [1]
>>> 
>>> 
> 
>>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
>>> 
>>> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
>>> xavier.sumb...@ucuenca.edu.ec> wrote:
>>> 
 
 
 On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
> djkevincr1...@gmail.com
 
 wrote:
 
> Hi Xavier,
> 
> Thank you for the update. Take your time on the research for
>>> selecting
>>> the
> Redis client library, you dont need to compare all Redis clients,
> take a
> subset/few looks most promising ( by comparing community,
> functionality
> etc
> ). There are only very few recommended from redis.io. [1] ( Jedis,
> Lettuce
> and Redisson ) Let's focus on these 3, about high lever data
> structures
> etc. Let s do a comparison once you complete that research work.
> 
 
 Okay, I will work on that comparison.
 
 
 
 
> As Carlos mentioned, If you do have troubles setting up embedded
> server,
> you could always use [1] to spin up Redis server instance from
>>> docker
> image. This is the same approach we have taken on Aerospike and
> CouchDB
> datastore tests. That way you can spin up a real instance of Redis
>>> server,
> you wont be having any limitations compared to these mock servers.
> 
 
 Thanks I am looking into aerospike implementation.
 
 
 
> 
> [1] https://redis.io/clients#java
> [2] https://www.testcontainers.org/
> 
> Regards
> 
> 
> Best ,
 
 Xavier
 
>>> 
>>> --
>>> Advertencia legal:
>>> Este 

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Thanks Alonso for your comments. 

I will analyze the code from HBase. Thanks for your suggestion… 

Also, my code is in master, but I will move to the branch 527, it will be 
easier to trace changes. 


Best,
Xavier.

> On Jun 10, 2019, at 18:20, Alfonso Nishikawa  
> wrote:
> 
> Hi, Xavier.
> 
> I don't see your branch GORA-527 told in your report.
> What I would want to ask for is to add the same functionality to load the
> mapping from configuration in you RedisStore [1] as in HBase's store [2].
> This will have implications on your readMapping that in HBase was done by
> passing an InputStream instead of a file name.
> 
> [1] -
> https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
> [2] -
> https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92
> 
> Regards,
> 
> Alfonso Nishikawa
> 
> El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
> () escribió:
> 
>> Thanks for your comments.
>> 
>> I pushed my commits and updated the report.
>> 
>> During this week I want to decide what redisson codec works best for
>> gora’s use case and I will also solve the comments of the libraries
>> comparison.  I will keep updating you guys during the week any blocker or
>> new tasks that come along.
>> 
>> 
>> Best,
>> Xavier.
>> 
>> 
>>> On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
>>> 
>>> Hi Xavier
>>> 
>>> The document looks great. I have left a few comments. I would like to
>> read
>>> other valorations .
>>> Also, please make sure to publish your weekly process on the Wiki space.
>>> 
>>> Regards,
>>> Carlos
>>> 
>>> El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
>>> () escribió:
>>> 
 Sorry, try again. Anybody should be able to access? I set for everyone.
 
 
 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
 
 
 Best,
 Xavier
> On Jun 7, 2019, at 23:59, Kevin Ratnasekera 
 wrote:
> 
> Hi Xavier,
> 
> I requested access to the docs. Can you please give permissions?
> 
> Regards
> Kevin
> 
> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
>  wrote:
> 
>> Hello
>> 
>> I think that redisson is the option to support redis in gora.
>> 
>> There is an analysis here [1]. What do you think? After some
 suggestions I
>> can add those results to the wiki.
>> 
>> Best
>> Xavier
>> 
>> [1]
>> 
>> 
 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
>> 
>> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
>> xavier.sumb...@ucuenca.edu.ec> wrote:
>> 
>>> 
>>> 
>>> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
 djkevincr1...@gmail.com
>>> 
>>> wrote:
>>> 
 Hi Xavier,
 
 Thank you for the update. Take your time on the research for
>> selecting
>> the
 Redis client library, you dont need to compare all Redis clients,
 take a
 subset/few looks most promising ( by comparing community,
 functionality
 etc
 ). There are only very few recommended from redis.io. [1] ( Jedis,
 Lettuce
 and Redisson ) Let's focus on these 3, about high lever data
 structures
 etc. Let s do a comparison once you complete that research work.
 
>>> 
>>> Okay, I will work on that comparison.
>>> 
>>> 
>>> 
>>> 
 As Carlos mentioned, If you do have troubles setting up embedded
 server,
 you could always use [1] to spin up Redis server instance from
>> docker
 image. This is the same approach we have taken on Aerospike and
 CouchDB
 datastore tests. That way you can spin up a real instance of Redis
>> server,
 you wont be having any limitations compared to these mock servers.
 
>>> 
>>> Thanks I am looking into aerospike implementation.
>>> 
>>> 
>>> 
 
 [1] https://redis.io/clients#java
 [2] https://www.testcontainers.org/
 
 Regards
 
 
 Best ,
>>> 
>>> Xavier
>>> 
>> 
>> --
>> Advertencia legal:
>> Este mensaje y, en su caso, los archivos anexos son
>> confidenciales, especialmente en lo que respecta a los datos
 personales, y
>> se dirigen exclusivamente al destinatario referenciado. Si usted no lo
 es
>> y
>> lo ha recibido por error o tiene conocimiento del mismo por cualquier
>> motivo, le rogamos que nos lo comunique por este medio y proceda a
>> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>> reproducir, alterar, archivar o comunicar a terceros el presente
 mensaje y
>> ficheros anexos, todo ello bajo pena de incurrir en 

Re: Redis datastore

[Alfonso Nishikawa]

Hi, Xavier.

I don't see your branch GORA-527 told in your report.
What I would want to ask for is to add the same functionality to load the
mapping from configuration in you RedisStore [1] as in HBase's store [2].
This will have implications on your readMapping that in HBase was done by
passing an InputStream instead of a file name.

[1] -
https://github.com/cuent/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L78
[2] -
https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92

Regards,

Alfonso Nishikawa

El lun., 10 jun. 2019 a las 4:16, FRANCISCO XAVIER SUMBA TORAL
() escribió:

> Thanks for your comments.
>
> I pushed my commits and updated the report.
>
> During this week I want to decide what redisson codec works best for
> gora’s use case and I will also solve the comments of the libraries
> comparison.  I will keep updating you guys during the week any blocker or
> new tasks that come along.
>
>
> Best,
> Xavier.
>
>
> > On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
> >
> > Hi Xavier
> >
> > The document looks great. I have left a few comments. I would like to
> read
> > other valorations .
> > Also, please make sure to publish your weekly process on the Wiki space.
> >
> > Regards,
> > Carlos
> >
> > El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
> > () escribió:
> >
> >> Sorry, try again. Anybody should be able to access? I set for everyone.
> >>
> >>
> >>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
> >>
> >>
> >> Best,
> >> Xavier
> >>> On Jun 7, 2019, at 23:59, Kevin Ratnasekera 
> >> wrote:
> >>>
> >>> Hi Xavier,
> >>>
> >>> I requested access to the docs. Can you please give permissions?
> >>>
> >>> Regards
> >>> Kevin
> >>>
> >>> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
> >>>  wrote:
> >>>
>  Hello
> 
>  I think that redisson is the option to support redis in gora.
> 
>  There is an analysis here [1]. What do you think? After some
> >> suggestions I
>  can add those results to the wiki.
> 
>  Best
>  Xavier
> 
>  [1]
> 
> 
> >>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
> 
>  On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
>  xavier.sumb...@ucuenca.edu.ec> wrote:
> 
> >
> >
> > On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
> >> djkevincr1...@gmail.com
> >
> > wrote:
> >
> >> Hi Xavier,
> >>
> >> Thank you for the update. Take your time on the research for
> selecting
>  the
> >> Redis client library, you dont need to compare all Redis clients,
> >> take a
> >> subset/few looks most promising ( by comparing community,
> >> functionality
> >> etc
> >> ). There are only very few recommended from redis.io. [1] ( Jedis,
> >> Lettuce
> >> and Redisson ) Let's focus on these 3, about high lever data
> >> structures
> >> etc. Let s do a comparison once you complete that research work.
> >>
> >
> > Okay, I will work on that comparison.
> >
> >
> >
> >
> >> As Carlos mentioned, If you do have troubles setting up embedded
> >> server,
> >> you could always use [1] to spin up Redis server instance from
> docker
> >> image. This is the same approach we have taken on Aerospike and
> >> CouchDB
> >> datastore tests. That way you can spin up a real instance of Redis
>  server,
> >> you wont be having any limitations compared to these mock servers.
> >>
> >
> > Thanks I am looking into aerospike implementation.
> >
> >
> >
> >>
> >> [1] https://redis.io/clients#java
> >> [2] https://www.testcontainers.org/
> >>
> >> Regards
> >>
> >>
> >> Best ,
> >
> > Xavier
> >
> 
>  --
>  Advertencia legal:
>  Este mensaje y, en su caso, los archivos anexos son
>  confidenciales, especialmente en lo que respecta a los datos
> >> personales, y
>  se dirigen exclusivamente al destinatario referenciado. Si usted no lo
> >> es
>  y
>  lo ha recibido por error o tiene conocimiento del mismo por cualquier
>  motivo, le rogamos que nos lo comunique por este medio y proceda a
>  destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>  reproducir, alterar, archivar o comunicar a terceros el presente
> >> mensaje y
>  ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
>  legales. Las opiniones contenidas en este mensaje y en los archivos
>  adjuntos, pertenecen exclusivamente a su remitente y no representan la
>  opinión de la Universidad de Cuenca salvo que se diga expresamente y
> el
>  remitente esté autorizado para ello. El emisor no garantiza la
> >> integridad,
>  rapidez o seguridad del presente correo, ni se 

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Thanks for your comments.

I pushed my commits and updated the report. 

During this week I want to decide what redisson codec works best for gora’s use 
case and I will also solve the comments of the libraries comparison.  I will 
keep updating you guys during the week any blocker or new tasks that come along.


Best,
Xavier.


> On Jun 9, 2019, at 23:43, carlos muñoz  wrote:
> 
> Hi Xavier
> 
> The document looks great. I have left a few comments. I would like to read
> other valorations .
> Also, please make sure to publish your weekly process on the Wiki space.
> 
> Regards,
> Carlos
> 
> El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
> () escribió:
> 
>> Sorry, try again. Anybody should be able to access? I set for everyone.
>> 
>> 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
>> 
>> 
>> Best,
>> Xavier
>>> On Jun 7, 2019, at 23:59, Kevin Ratnasekera 
>> wrote:
>>> 
>>> Hi Xavier,
>>> 
>>> I requested access to the docs. Can you please give permissions?
>>> 
>>> Regards
>>> Kevin
>>> 
>>> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
>>>  wrote:
>>> 
 Hello
 
 I think that redisson is the option to support redis in gora.
 
 There is an analysis here [1]. What do you think? After some
>> suggestions I
 can add those results to the wiki.
 
 Best
 Xavier
 
 [1]
 
 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
 
 On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
 xavier.sumb...@ucuenca.edu.ec> wrote:
 
> 
> 
> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
>> djkevincr1...@gmail.com
> 
> wrote:
> 
>> Hi Xavier,
>> 
>> Thank you for the update. Take your time on the research for selecting
 the
>> Redis client library, you dont need to compare all Redis clients,
>> take a
>> subset/few looks most promising ( by comparing community,
>> functionality
>> etc
>> ). There are only very few recommended from redis.io. [1] ( Jedis,
>> Lettuce
>> and Redisson ) Let's focus on these 3, about high lever data
>> structures
>> etc. Let s do a comparison once you complete that research work.
>> 
> 
> Okay, I will work on that comparison.
> 
> 
> 
> 
>> As Carlos mentioned, If you do have troubles setting up embedded
>> server,
>> you could always use [1] to spin up Redis server instance from docker
>> image. This is the same approach we have taken on Aerospike and
>> CouchDB
>> datastore tests. That way you can spin up a real instance of Redis
 server,
>> you wont be having any limitations compared to these mock servers.
>> 
> 
> Thanks I am looking into aerospike implementation.
> 
> 
> 
>> 
>> [1] https://redis.io/clients#java
>> [2] https://www.testcontainers.org/
>> 
>> Regards
>> 
>> 
>> Best ,
> 
> Xavier
> 
 
 --
 Advertencia legal:
 Este mensaje y, en su caso, los archivos anexos son
 confidenciales, especialmente en lo que respecta a los datos
>> personales, y
 se dirigen exclusivamente al destinatario referenciado. Si usted no lo
>> es
 y
 lo ha recibido por error o tiene conocimiento del mismo por cualquier
 motivo, le rogamos que nos lo comunique por este medio y proceda a
 destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
 reproducir, alterar, archivar o comunicar a terceros el presente
>> mensaje y
 ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
 legales. Las opiniones contenidas en este mensaje y en los archivos
 adjuntos, pertenecen exclusivamente a su remitente y no representan la
 opinión de la Universidad de Cuenca salvo que se diga expresamente y el
 remitente esté autorizado para ello. El emisor no garantiza la
>> integridad,
 rapidez o seguridad del presente correo, ni se responsabiliza de
>> posibles
 perjuicios derivados de la captura, incorporaciones de virus o
 cualesquiera
 otras manipulaciones efectuadas por terceros.
 
>> 
>> 
>> --
>> Advertencia legal:
>> Este mensaje y, en su caso, los archivos anexos son
>> confidenciales, especialmente en lo que respecta a los datos personales, y
>> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
>> y
>> lo ha recibido por error o tiene conocimiento del mismo por cualquier
>> motivo, le rogamos que nos lo comunique por este medio y proceda a
>> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
>> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
>> legales. Las opiniones contenidas en este mensaje y en los archivos
>> adjuntos, pertenecen exclusivamente a su remitente y no representan la
>> 

Re: Redis datastore

[carlos muñoz]

Hi Xavier

The document looks great. I have left a few comments. I would like to read
other valorations .
Also, please make sure to publish your weekly process on the Wiki space.

Regards,
Carlos

El vie., 7 jun. 2019 a las 23:01, FRANCISCO XAVIER SUMBA TORAL
() escribió:

> Sorry, try again. Anybody should be able to access? I set for everyone.
>
>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing
>
>
> Best,
> Xavier
> > On Jun 7, 2019, at 23:59, Kevin Ratnasekera 
> wrote:
> >
> > Hi Xavier,
> >
> > I requested access to the docs. Can you please give permissions?
> >
> > Regards
> > Kevin
> >
> > On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
> >  wrote:
> >
> >> Hello
> >>
> >> I think that redisson is the option to support redis in gora.
> >>
> >> There is an analysis here [1]. What do you think? After some
> suggestions I
> >> can add those results to the wiki.
> >>
> >> Best
> >> Xavier
> >>
> >> [1]
> >>
> >>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
> >>
> >> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
> >> xavier.sumb...@ucuenca.edu.ec> wrote:
> >>
> >>>
> >>>
> >>> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, <
> djkevincr1...@gmail.com
> >>>
> >>> wrote:
> >>>
>  Hi Xavier,
> 
>  Thank you for the update. Take your time on the research for selecting
> >> the
>  Redis client library, you dont need to compare all Redis clients,
> take a
>  subset/few looks most promising ( by comparing community,
> functionality
>  etc
>  ). There are only very few recommended from redis.io. [1] ( Jedis,
>  Lettuce
>  and Redisson ) Let's focus on these 3, about high lever data
> structures
>  etc. Let s do a comparison once you complete that research work.
> 
> >>>
> >>> Okay, I will work on that comparison.
> >>>
> >>>
> >>>
> >>>
>  As Carlos mentioned, If you do have troubles setting up embedded
> server,
>  you could always use [1] to spin up Redis server instance from docker
>  image. This is the same approach we have taken on Aerospike and
> CouchDB
>  datastore tests. That way you can spin up a real instance of Redis
> >> server,
>  you wont be having any limitations compared to these mock servers.
> 
> >>>
> >>> Thanks I am looking into aerospike implementation.
> >>>
> >>>
> >>>
> 
>  [1] https://redis.io/clients#java
>  [2] https://www.testcontainers.org/
> 
>  Regards
> 
> 
>  Best ,
> >>>
> >>> Xavier
> >>>
> >>
> >> --
> >> Advertencia legal:
> >> Este mensaje y, en su caso, los archivos anexos son
> >> confidenciales, especialmente en lo que respecta a los datos
> personales, y
> >> se dirigen exclusivamente al destinatario referenciado. Si usted no lo
> es
> >> y
> >> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> >> motivo, le rogamos que nos lo comunique por este medio y proceda a
> >> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> >> reproducir, alterar, archivar o comunicar a terceros el presente
> mensaje y
> >> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> >> legales. Las opiniones contenidas en este mensaje y en los archivos
> >> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> >> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> >> remitente esté autorizado para ello. El emisor no garantiza la
> integridad,
> >> rapidez o seguridad del presente correo, ni se responsabiliza de
> posibles
> >> perjuicios derivados de la captura, incorporaciones de virus o
> >> cualesquiera
> >> otras manipulaciones efectuadas por terceros.
> >>
>
>
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> remitente esté autorizado para ello. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
>

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Sorry, try again. Anybody should be able to access? I set for everyone. 

https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=sharing


Best,
Xavier
> On Jun 7, 2019, at 23:59, Kevin Ratnasekera  wrote:
> 
> Hi Xavier,
> 
> I requested access to the docs. Can you please give permissions?
> 
> Regards
> Kevin
> 
> On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
>  wrote:
> 
>> Hello
>> 
>> I think that redisson is the option to support redis in gora.
>> 
>> There is an analysis here [1]. What do you think? After some suggestions I
>> can add those results to the wiki.
>> 
>> Best
>> Xavier
>> 
>> [1]
>> 
>> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
>> 
>> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
>> xavier.sumb...@ucuenca.edu.ec> wrote:
>> 
>>> 
>>> 
>>> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, >> 
>>> wrote:
>>> 
 Hi Xavier,
 
 Thank you for the update. Take your time on the research for selecting
>> the
 Redis client library, you dont need to compare all Redis clients, take a
 subset/few looks most promising ( by comparing community, functionality
 etc
 ). There are only very few recommended from redis.io. [1] ( Jedis,
 Lettuce
 and Redisson ) Let's focus on these 3, about high lever data structures
 etc. Let s do a comparison once you complete that research work.
 
>>> 
>>> Okay, I will work on that comparison.
>>> 
>>> 
>>> 
>>> 
 As Carlos mentioned, If you do have troubles setting up embedded server,
 you could always use [1] to spin up Redis server instance from docker
 image. This is the same approach we have taken on Aerospike and CouchDB
 datastore tests. That way you can spin up a real instance of Redis
>> server,
 you wont be having any limitations compared to these mock servers.
 
>>> 
>>> Thanks I am looking into aerospike implementation.
>>> 
>>> 
>>> 
 
 [1] https://redis.io/clients#java
 [2] https://www.testcontainers.org/
 
 Regards
 
 
 Best ,
>>> 
>>> Xavier
>>> 
>> 
>> --
>> Advertencia legal:
>> Este mensaje y, en su caso, los archivos anexos son
>> confidenciales, especialmente en lo que respecta a los datos personales, y
>> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
>> y
>> lo ha recibido por error o tiene conocimiento del mismo por cualquier
>> motivo, le rogamos que nos lo comunique por este medio y proceda a
>> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
>> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
>> legales. Las opiniones contenidas en este mensaje y en los archivos
>> adjuntos, pertenecen exclusivamente a su remitente y no representan la
>> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
>> remitente esté autorizado para ello. El emisor no garantiza la integridad,
>> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
>> perjuicios derivados de la captura, incorporaciones de virus o
>> cualesquiera
>> otras manipulaciones efectuadas por terceros.
>> 


-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 
reproducir, alterar, archivar o comunicar a terceros el presente mensaje y 
ficheros anexos, todo ello bajo pena de incurrir en responsabilidades 
legales. Las opiniones contenidas en este mensaje y en los archivos 
adjuntos, pertenecen exclusivamente a su remitente y no representan la 
opinión de la Universidad de Cuenca salvo que se diga expresamente y el 
remitente esté autorizado para ello. El emisor no garantiza la integridad, 
rapidez o seguridad del presente correo, ni se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualesquiera 
otras manipulaciones efectuadas por terceros.

Re: Redis datastore

[Kevin Ratnasekera]

Hi Xavier,

I requested access to the docs. Can you please give permissions?

Regards
Kevin

On Sat, Jun 8, 2019 at 9:23 AM FRANCISCO XAVIER SUMBA TORAL
 wrote:

> Hello
>
> I think that redisson is the option to support redis in gora.
>
> There is an analysis here [1]. What do you think? After some suggestions I
> can add those results to the wiki.
>
> Best
> Xavier
>
> [1]
>
> https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk
>
> On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
> xavier.sumb...@ucuenca.edu.ec> wrote:
>
> >
> >
> > On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera,  >
> > wrote:
> >
> >> Hi Xavier,
> >>
> >> Thank you for the update. Take your time on the research for selecting
> the
> >> Redis client library, you dont need to compare all Redis clients, take a
> >> subset/few looks most promising ( by comparing community, functionality
> >> etc
> >> ). There are only very few recommended from redis.io. [1] ( Jedis,
> >> Lettuce
> >> and Redisson ) Let's focus on these 3, about high lever data structures
> >> etc. Let s do a comparison once you complete that research work.
> >>
> >
> > Okay, I will work on that comparison.
> >
> >
> >
> >
> >> As Carlos mentioned, If you do have troubles setting up embedded server,
> >> you could always use [1] to spin up Redis server instance from docker
> >> image. This is the same approach we have taken on Aerospike and CouchDB
> >> datastore tests. That way you can spin up a real instance of Redis
> server,
> >> you wont be having any limitations compared to these mock servers.
> >>
> >
> > Thanks I am looking into aerospike implementation.
> >
> >
> >
> >>
> >> [1] https://redis.io/clients#java
> >> [2] https://www.testcontainers.org/
> >>
> >> Regards
> >>
> >>
> >> Best ,
> >
> > Xavier
> >
>
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> remitente esté autorizado para ello. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
>

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Hello

I think that redisson is the option to support redis in gora.

There is an analysis here [1]. What do you think? After some suggestions I
can add those results to the wiki.

Best
Xavier

[1]
https://docs.google.com/document/d/17RlGIu_SaPo7O2J7k_htg1UDDO9ah41u8cCYUURC7BM/edit?usp=drivesdk

On Wed, Jun 5, 2019, 9:16 AM FRANCISCO XAVIER SUMBA TORAL, <
xavier.sumb...@ucuenca.edu.ec> wrote:

>
>
> On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, 
> wrote:
>
>> Hi Xavier,
>>
>> Thank you for the update. Take your time on the research for selecting the
>> Redis client library, you dont need to compare all Redis clients, take a
>> subset/few looks most promising ( by comparing community, functionality
>> etc
>> ). There are only very few recommended from redis.io. [1] ( Jedis,
>> Lettuce
>> and Redisson ) Let's focus on these 3, about high lever data structures
>> etc. Let s do a comparison once you complete that research work.
>>
>
> Okay, I will work on that comparison.
>
>
>
>
>> As Carlos mentioned, If you do have troubles setting up embedded server,
>> you could always use [1] to spin up Redis server instance from docker
>> image. This is the same approach we have taken on Aerospike and CouchDB
>> datastore tests. That way you can spin up a real instance of Redis server,
>> you wont be having any limitations compared to these mock servers.
>>
>
> Thanks I am looking into aerospike implementation.
>
>
>
>>
>> [1] https://redis.io/clients#java
>> [2] https://www.testcontainers.org/
>>
>> Regards
>>
>>
>> Best ,
>
> Xavier
>

-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 
reproducir, alterar, archivar o comunicar a terceros el presente mensaje y 
ficheros anexos, todo ello bajo pena de incurrir en responsabilidades 
legales. Las opiniones contenidas en este mensaje y en los archivos 
adjuntos, pertenecen exclusivamente a su remitente y no representan la 
opinión de la Universidad de Cuenca salvo que se diga expresamente y el 
remitente esté autorizado para ello. El emisor no garantiza la integridad, 
rapidez o seguridad del presente correo, ni se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualesquiera 
otras manipulaciones efectuadas por terceros.

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

On Wed, Jun 5, 2019, 1:31 AM Kevin Ratnasekera, 
wrote:

> Hi Xavier,
>
> Thank you for the update. Take your time on the research for selecting the
> Redis client library, you dont need to compare all Redis clients, take a
> subset/few looks most promising ( by comparing community, functionality etc
> ). There are only very few recommended from redis.io. [1] ( Jedis, Lettuce
> and Redisson ) Let's focus on these 3, about high lever data structures
> etc. Let s do a comparison once you complete that research work.
>

Okay, I will work on that comparison.




> As Carlos mentioned, If you do have troubles setting up embedded server,
> you could always use [1] to spin up Redis server instance from docker
> image. This is the same approach we have taken on Aerospike and CouchDB
> datastore tests. That way you can spin up a real instance of Redis server,
> you wont be having any limitations compared to these mock servers.
>

Thanks I am looking into aerospike implementation.



>
> [1] https://redis.io/clients#java
> [2] https://www.testcontainers.org/
>
> Regards
>
>
> Best ,

Xavier

-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 
reproducir, alterar, archivar o comunicar a terceros el presente mensaje y 
ficheros anexos, todo ello bajo pena de incurrir en responsabilidades 
legales. Las opiniones contenidas en este mensaje y en los archivos 
adjuntos, pertenecen exclusivamente a su remitente y no representan la 
opinión de la Universidad de Cuenca salvo que se diga expresamente y el 
remitente esté autorizado para ello. El emisor no garantiza la integridad, 
rapidez o seguridad del presente correo, ni se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualesquiera 
otras manipulaciones efectuadas por terceros.

Re: Redis datastore

[Kevin Ratnasekera]

Hi Xavier,

Thank you for the update. Take your time on the research for selecting the
Redis client library, you dont need to compare all Redis clients, take a
subset/few looks most promising ( by comparing community, functionality etc
). There are only very few recommended from redis.io. [1] ( Jedis, Lettuce
and Redisson ) Let's focus on these 3, about high lever data structures
etc. Let s do a comparison once you complete that research work.

As Carlos mentioned, If you do have troubles setting up embedded server,
you could always use [1] to spin up Redis server instance from docker
image. This is the same approach we have taken on Aerospike and CouchDB
datastore tests. That way you can spin up a real instance of Redis server,
you wont be having any limitations compared to these mock servers.

[1] https://redis.io/clients#java
[2] https://www.testcontainers.org/

Regards
Kevin

On Wed, Jun 5, 2019 at 10:20 AM FRANCISCO XAVIER SUMBA TORAL
 wrote:

> Hello,
>
> About trying other libraries, it is a broad task. There are a lot and each
> of them has its own advantage/disadvantage. Redisson, looks promising and
> think we can use that one instead of Jedis, but I am still comparing with
> other libraries. I will get back with this comparison soon.
>
> After looking into Gora’s source code, the datastores have a different
> paradigm than Redis for storing data. So, I am still finding a way to map
> gore’s fields with avro and key registers from redis. This goes hand in
> hand with the selection of the library.
>
>
> About testings basic operations and a single node is necessary. There is a
> comment of Kevin below, but I will look into Aerospike to analyze if there
> a more suitable option.
>
> I will work in the mapping from gora <-> redis.
>
> Best,
> Xavier
>
> > On Jun 4, 2019, at 17:04, carlos muñoz  wrote:
> >
> >
> > Hi Xavier.
> >
> > Please note that redis-mock has some limitations.
> > Alternatively, If you realize that you need unsupported operations you
> can use docker, give a look to the Aerospike tests [2].
> >
> > my two cents,
> >
> > [1] https://github.com/fppt/jedis-mock#supported-operations <
> https://github.com/fppt/jedis-mock#supported-operations>
> > [2]
> https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/GoraAerospikeTestDriver.java
> <
> https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/GoraAerospikeTestDriver.java
> >
> >
> > Best regards.
> > Carlos
> >
> > El lun., 3 jun. 2019 a las 4:08, Madhawa Kasun Gunasekara (<
> madhaw...@gmail.com >) escribió:
> > Hi Xavier,
> >
> > It's better to do an analysis of Redis clients. then based on the
> results,
> > we can choose what is the appropriate library for the implementation.
> > Please update this mail thread weekly about your project progress. Mainly
> > you can update what you have done for the week and what you are hoping to
> > do in the upcoming week, the problems you face., etc.
> >
> > However, I checked your weekly report in the wiki, In that one also,
> Please
> > add a section for Next week plan as well. and Please replace "semana"
> > Spanish word with the appropriate English word.
> > Please try to update this email thread at least twice a week. Let us know
> > If you have any questions on the project.
> >
> > Thanks,
> > Madhawa
> >
> >
> > On Mon, May 27, 2019 at 9:17 AM Kevin Ratnasekera <
> djkevincr1...@gmail.com >
> > wrote:
> >
> > > Hi Xavier,
> > >
> > > Please find my answers inline.
> > >
> > > On Mon, May 27, 2019 at 10:33 AM FRANCISCO XAVIER SUMBA TORAL
> > >  > > .ec.invalid>
> wrote:
> > >
> > > > Hello,
> > > >
> > > > I am using Jedis Mock [1] to embed Redis for tests. However, I am
> > > > wondering since redis accepts master/slave cluster / replication / no
> > > > replication / single instance. Are all those modes necessary? If so,
> I
> > > > propose to include them in the gore.properties, but what is the
> priority
> > > > given?
> > > >
> > > For testing purposes ( mainly in unit tests ), I think it s sufficient
> to
> > > run single node cluster. 'gore.properties' should only involve
> > > configurations that you do when you create a Redis client instance and
> > > operations you do on top of this client. 'gore.properties' should not
> > > involve any server side configurations or cluster modes on Server Side.
> > > However if the Redis client has configurations which directly effects
> > > cluster modes etc, then you should add them to 'gore.properties'.
> Basically
> > > the argument is client you create in datastore should be able to talk
> to
> > > server running in both standalone or distributed mode as specified in
> > > 'gore.properties'. ( You should not hardcode these in client side ) It
> s
> > > sufficient run all the tests in standalone mode. By default you may
> set it
> > > to standalone mode, if a 

Re: Redis datastore

[FRANCISCO XAVIER SUMBA TORAL]

Hello,

About trying other libraries, it is a broad task. There are a lot and each of 
them has its own advantage/disadvantage. Redisson, looks promising and think we 
can use that one instead of Jedis, but I am still comparing with other 
libraries. I will get back with this comparison soon. 

After looking into Gora’s source code, the datastores have a different paradigm 
than Redis for storing data. So, I am still finding a way to map gore’s fields 
with avro and key registers from redis. This goes hand in hand with the 
selection of the library.


About testings basic operations and a single node is necessary. There is a 
comment of Kevin below, but I will look into Aerospike to analyze if there a 
more suitable option.

I will work in the mapping from gora <-> redis. 

Best,
Xavier

> On Jun 4, 2019, at 17:04, carlos muñoz  wrote:
> 
> 
> Hi Xavier.
> 
> Please note that redis-mock has some limitations. 
> Alternatively, If you realize that you need unsupported operations you can 
> use docker, give a look to the Aerospike tests [2].
> 
> my two cents,
> 
> [1] https://github.com/fppt/jedis-mock#supported-operations 
> 
> [2] 
> https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/GoraAerospikeTestDriver.java
>  
> 
> 
> Best regards.
> Carlos
> 
> El lun., 3 jun. 2019 a las 4:08, Madhawa Kasun Gunasekara 
> (mailto:madhaw...@gmail.com>>) escribió:
> Hi Xavier,
> 
> It's better to do an analysis of Redis clients. then based on the results,
> we can choose what is the appropriate library for the implementation.
> Please update this mail thread weekly about your project progress. Mainly
> you can update what you have done for the week and what you are hoping to
> do in the upcoming week, the problems you face., etc.
> 
> However, I checked your weekly report in the wiki, In that one also, Please
> add a section for Next week plan as well. and Please replace "semana"
> Spanish word with the appropriate English word.
> Please try to update this email thread at least twice a week. Let us know
> If you have any questions on the project.
> 
> Thanks,
> Madhawa
> 
> 
> On Mon, May 27, 2019 at 9:17 AM Kevin Ratnasekera  >
> wrote:
> 
> > Hi Xavier,
> >
> > Please find my answers inline.
> >
> > On Mon, May 27, 2019 at 10:33 AM FRANCISCO XAVIER SUMBA TORAL
> > mailto:xavier.sumb...@ucuenca.edu>.ec.invalid> 
> > wrote:
> >
> > > Hello,
> > >
> > > I am using Jedis Mock [1] to embed Redis for tests. However, I am
> > > wondering since redis accepts master/slave cluster / replication / no
> > > replication / single instance. Are all those modes necessary? If so, I
> > > propose to include them in the gore.properties, but what is the priority
> > > given?
> > >
> > For testing purposes ( mainly in unit tests ), I think it s sufficient to
> > run single node cluster. 'gore.properties' should only involve
> > configurations that you do when you create a Redis client instance and
> > operations you do on top of this client. 'gore.properties' should not
> > involve any server side configurations or cluster modes on Server Side.
> > However if the Redis client has configurations which directly effects
> > cluster modes etc, then you should add them to 'gore.properties'. Basically
> > the argument is client you create in datastore should be able to talk to
> > server running in both standalone or distributed mode as specified in
> > 'gore.properties'. ( You should not hardcode these in client side ) It s
> > sufficient run all the tests in standalone mode. By default you may set it
> > to standalone mode, if a user required he may have the option to change.
> >
> > >
> > > Additionally, redis support complex datatypes such as lists or sets.
> > > However, I think all those datatypes can be handled as Strings, but I
> > > wanted to consult what others think.
> > >
> > As I have mentioned to you earlier with primitive Redis data types, Please
> > check whether there are high level libraries available as extensions to
> > these Redis types. AVRO has other complex types Eg:- Map, Array, Union,
> > Enum etc. See how you can map from/to AVRO from/to Redis. This is part of
> > your research.  I am also suggesting you to have look on Redisson [1] [2]
> > which has AVRO integration. See whether you find anything usable in
> > implementation. This also comes as Apache Licensed. Please do a comparison
> > of all Redis java client libraries [3] see which suits our needs the most.
> >
> > [1] https://github.com/redisson/redisson 
> > 
> > [2] https://redisson.org/ 
> > [3] https://redis.io/clients#java 
> >
> > Regards
> > Kevin
> >
> > >
> > > Best,
> > > Xavier.
> > >
> > >
> > >
> > 

Re: Redis datastore

[carlos muñoz]

Hi Xavier.

Please note that redis-mock has some limitations.
Alternatively, If you realize that you need unsupported operations you can
use docker, give a look to the Aerospike tests [2].

my two cents,

[1] https://github.com/fppt/jedis-mock#supported-operations
[2]
https://github.com/apache/gora/blob/master/gora-aerospike/src/test/java/org/apache/gora/aerospike/GoraAerospikeTestDriver.java

Best regards.
Carlos

El lun., 3 jun. 2019 a las 4:08, Madhawa Kasun Gunasekara (<
madhaw...@gmail.com>) escribió:

> Hi Xavier,
>
> It's better to do an analysis of Redis clients. then based on the results,
> we can choose what is the appropriate library for the implementation.
> Please update this mail thread weekly about your project progress. Mainly
> you can update what you have done for the week and what you are hoping to
> do in the upcoming week, the problems you face., etc.
>
> However, I checked your weekly report in the wiki, In that one also, Please
> add a section for Next week plan as well. and Please replace "semana"
> Spanish word with the appropriate English word.
> Please try to update this email thread at least twice a week. Let us know
> If you have any questions on the project.
>
> Thanks,
> Madhawa
>
>
> On Mon, May 27, 2019 at 9:17 AM Kevin Ratnasekera  >
> wrote:
>
> > Hi Xavier,
> >
> > Please find my answers inline.
> >
> > On Mon, May 27, 2019 at 10:33 AM FRANCISCO XAVIER SUMBA TORAL
> >  wrote:
> >
> > > Hello,
> > >
> > > I am using Jedis Mock [1] to embed Redis for tests. However, I am
> > > wondering since redis accepts master/slave cluster / replication / no
> > > replication / single instance. Are all those modes necessary? If so, I
> > > propose to include them in the gore.properties, but what is the
> priority
> > > given?
> > >
> > For testing purposes ( mainly in unit tests ), I think it s sufficient to
> > run single node cluster. 'gore.properties' should only involve
> > configurations that you do when you create a Redis client instance and
> > operations you do on top of this client. 'gore.properties' should not
> > involve any server side configurations or cluster modes on Server Side.
> > However if the Redis client has configurations which directly effects
> > cluster modes etc, then you should add them to 'gore.properties'.
> Basically
> > the argument is client you create in datastore should be able to talk to
> > server running in both standalone or distributed mode as specified in
> > 'gore.properties'. ( You should not hardcode these in client side ) It s
> > sufficient run all the tests in standalone mode. By default you may set
> it
> > to standalone mode, if a user required he may have the option to change.
> >
> > >
> > > Additionally, redis support complex datatypes such as lists or sets.
> > > However, I think all those datatypes can be handled as Strings, but I
> > > wanted to consult what others think.
> > >
> > As I have mentioned to you earlier with primitive Redis data types,
> Please
> > check whether there are high level libraries available as extensions to
> > these Redis types. AVRO has other complex types Eg:- Map, Array, Union,
> > Enum etc. See how you can map from/to AVRO from/to Redis. This is part of
> > your research.  I am also suggesting you to have look on Redisson [1] [2]
> > which has AVRO integration. See whether you find anything usable in
> > implementation. This also comes as Apache Licensed. Please do a
> comparison
> > of all Redis java client libraries [3] see which suits our needs the
> most.
> >
> > [1] https://github.com/redisson/redisson
> > [2] https://redisson.org/
> > [3] https://redis.io/clients#java
> >
> > Regards
> > Kevin
> >
> > >
> > > Best,
> > > Xavier.
> > >
> > >
> > >
> > > [1] https://github.com/fppt/jedis-mock <
> > https://github.com/fppt/jedis-mock
> > > >
> > > --
> > > Advertencia legal:
> > > Este mensaje y, en su caso, los archivos anexos son
> > > confidenciales, especialmente en lo que respecta a los datos
> personales,
> > y
> > > se dirigen exclusivamente al destinatario referenciado. Si usted no lo
> es
> > > y
> > > lo ha recibido por error o tiene conocimiento del mismo por cualquier
> > > motivo, le rogamos que nos lo comunique por este medio y proceda a
> > > destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> > > reproducir, alterar, archivar o comunicar a terceros el presente
> mensaje
> > y
> > > ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> > > legales. Las opiniones contenidas en este mensaje y en los archivos
> > > adjuntos, pertenecen exclusivamente a su remitente y no representan la
> > > opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> > > remitente esté autorizado para ello. El emisor no garantiza la
> > integridad,
> > > rapidez o seguridad del presente correo, ni se responsabiliza de
> posibles
> > > perjuicios derivados de la captura, incorporaciones de virus o
> > > cualesquiera
> > > otras manipulaciones efectuadas por 

Re: Redis datastore

[Madhawa Kasun Gunasekara]

Hi Xavier,

It's better to do an analysis of Redis clients. then based on the results,
we can choose what is the appropriate library for the implementation.
Please update this mail thread weekly about your project progress. Mainly
you can update what you have done for the week and what you are hoping to
do in the upcoming week, the problems you face., etc.

However, I checked your weekly report in the wiki, In that one also, Please
add a section for Next week plan as well. and Please replace "semana"
Spanish word with the appropriate English word.
Please try to update this email thread at least twice a week. Let us know
If you have any questions on the project.

Thanks,
Madhawa


On Mon, May 27, 2019 at 9:17 AM Kevin Ratnasekera 
wrote:

> Hi Xavier,
>
> Please find my answers inline.
>
> On Mon, May 27, 2019 at 10:33 AM FRANCISCO XAVIER SUMBA TORAL
>  wrote:
>
> > Hello,
> >
> > I am using Jedis Mock [1] to embed Redis for tests. However, I am
> > wondering since redis accepts master/slave cluster / replication / no
> > replication / single instance. Are all those modes necessary? If so, I
> > propose to include them in the gore.properties, but what is the priority
> > given?
> >
> For testing purposes ( mainly in unit tests ), I think it s sufficient to
> run single node cluster. 'gore.properties' should only involve
> configurations that you do when you create a Redis client instance and
> operations you do on top of this client. 'gore.properties' should not
> involve any server side configurations or cluster modes on Server Side.
> However if the Redis client has configurations which directly effects
> cluster modes etc, then you should add them to 'gore.properties'. Basically
> the argument is client you create in datastore should be able to talk to
> server running in both standalone or distributed mode as specified in
> 'gore.properties'. ( You should not hardcode these in client side ) It s
> sufficient run all the tests in standalone mode. By default you may set it
> to standalone mode, if a user required he may have the option to change.
>
> >
> > Additionally, redis support complex datatypes such as lists or sets.
> > However, I think all those datatypes can be handled as Strings, but I
> > wanted to consult what others think.
> >
> As I have mentioned to you earlier with primitive Redis data types, Please
> check whether there are high level libraries available as extensions to
> these Redis types. AVRO has other complex types Eg:- Map, Array, Union,
> Enum etc. See how you can map from/to AVRO from/to Redis. This is part of
> your research.  I am also suggesting you to have look on Redisson [1] [2]
> which has AVRO integration. See whether you find anything usable in
> implementation. This also comes as Apache Licensed. Please do a comparison
> of all Redis java client libraries [3] see which suits our needs the most.
>
> [1] https://github.com/redisson/redisson
> [2] https://redisson.org/
> [3] https://redis.io/clients#java
>
> Regards
> Kevin
>
> >
> > Best,
> > Xavier.
> >
> >
> >
> > [1] https://github.com/fppt/jedis-mock <
> https://github.com/fppt/jedis-mock
> > >
> > --
> > Advertencia legal:
> > Este mensaje y, en su caso, los archivos anexos son
> > confidenciales, especialmente en lo que respecta a los datos personales,
> y
> > se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> > y
> > lo ha recibido por error o tiene conocimiento del mismo por cualquier
> > motivo, le rogamos que nos lo comunique por este medio y proceda a
> > destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> > reproducir, alterar, archivar o comunicar a terceros el presente mensaje
> y
> > ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> > legales. Las opiniones contenidas en este mensaje y en los archivos
> > adjuntos, pertenecen exclusivamente a su remitente y no representan la
> > opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> > remitente esté autorizado para ello. El emisor no garantiza la
> integridad,
> > rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> > perjuicios derivados de la captura, incorporaciones de virus o
> > cualesquiera
> > otras manipulaciones efectuadas por terceros.
> >
>

Re: Redis datastore

[Kevin Ratnasekera]

Hi Xavier,

Please find my answers inline.

On Mon, May 27, 2019 at 10:33 AM FRANCISCO XAVIER SUMBA TORAL
 wrote:

> Hello,
>
> I am using Jedis Mock [1] to embed Redis for tests. However, I am
> wondering since redis accepts master/slave cluster / replication / no
> replication / single instance. Are all those modes necessary? If so, I
> propose to include them in the gore.properties, but what is the priority
> given?
>
For testing purposes ( mainly in unit tests ), I think it s sufficient to
run single node cluster. 'gore.properties' should only involve
configurations that you do when you create a Redis client instance and
operations you do on top of this client. 'gore.properties' should not
involve any server side configurations or cluster modes on Server Side.
However if the Redis client has configurations which directly effects
cluster modes etc, then you should add them to 'gore.properties'. Basically
the argument is client you create in datastore should be able to talk to
server running in both standalone or distributed mode as specified in
'gore.properties'. ( You should not hardcode these in client side ) It s
sufficient run all the tests in standalone mode. By default you may set it
to standalone mode, if a user required he may have the option to change.

>
> Additionally, redis support complex datatypes such as lists or sets.
> However, I think all those datatypes can be handled as Strings, but I
> wanted to consult what others think.
>
As I have mentioned to you earlier with primitive Redis data types, Please
check whether there are high level libraries available as extensions to
these Redis types. AVRO has other complex types Eg:- Map, Array, Union,
Enum etc. See how you can map from/to AVRO from/to Redis. This is part of
your research.  I am also suggesting you to have look on Redisson [1] [2]
which has AVRO integration. See whether you find anything usable in
implementation. This also comes as Apache Licensed. Please do a comparison
of all Redis java client libraries [3] see which suits our needs the most.

[1] https://github.com/redisson/redisson
[2] https://redisson.org/
[3] https://redis.io/clients#java

Regards
Kevin

>
> Best,
> Xavier.
>
>
>
> [1] https://github.com/fppt/jedis-mock  >
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> remitente esté autorizado para ello. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
>

Re: GSoC proposal for Redis Datastore

[Xavier Sumba]

Hi Kevin and Madhawa,

Thanks so much for your comments. I will address them today and make the final 
submission. 

Thanks all of your for your help guys! 

Best,
Xavier.

> On Apr 8, 2019, at 12:26, Kevin Ratnasekera  wrote:
> 
> Hi Xavier,
> 
> The proposal you come up with looks very good. Added some comment on the
> proposal. Please address before the final submission. Good luck with your
> submission.
> 
> Regards
> Kevin
> 
> On Mon, Apr 8, 2019 at 9:44 PM Madhawa Kasun Gunasekara 
> wrote:
> 
>> Hi Xavier.
>> 
>> Overall, The proposal looks good. I added some comments.
>> Good Luck.
>> 
>> Madhawa
>> 
>> 
>> On Sat, Apr 6, 2019 at 10:09 PM Xavier Sumba
>>  wrote:
>> 
>>> Hi Carlos,
>>> 
>>> Thanks so much for your suggestions. I already made the changes.
>>> 
>>> Best,
>>> Xavier.
>>> 
 On Apr 6, 2019, at 15:19, carlos muñoz  wrote:
 
 Hi Xavier.
 
 The proposal is looking really good. I added some minor comments.
 
 Good Luck.
 
 Regards,
 Carlos
 
 El sáb., 6 abr. 2019 a las 12:43, Xavier Sumba
 () escribió:
 
> Hello,
> 
> As discussed in Jira, I would like to participate in GSoC 2019. I have
> been through a lot with finals and projects but I managed to write my
> proposal and work in a small issue. Specifically, I want to work in
>> the
> support of Redis DB to Gora [1]. I also worked in the range queries
>> for
> Lucene and solved another issue with the conversion of datatypes, a
>> pull
> request can be found in [2]. I hope this issue can be merged by this
> weekend :D
> 
> Finally, I share my proposal for some feedback before submitting to
>>> GSoC (
> 
>>> 
>> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> <
> 
>>> 
>> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
 ).
> 
> 
> Best regards,
> Xavier.
> 
> [1] https://issues.apache.org/jira/browse/GORA-527 <
> https://issues.apache.org/jira/browse/GORA-527>
> [2] https://github.com/apache/gora/pull/158 <
> https://github.com/apache/gora/pull/158>
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos
>>> personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo
>>> es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente
>>> mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y
>> el
> remitente esté autorizado para ello. El emisor no garantiza la
>>> integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de
>>> posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
> 
>>> 
>>> 
>>> --
>>> Advertencia legal:
>>> Este mensaje y, en su caso, los archivos anexos son
>>> confidenciales, especialmente en lo que respecta a los datos personales,
>> y
>>> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
>>> y
>>> lo ha recibido por error o tiene conocimiento del mismo por cualquier
>>> motivo, le rogamos que nos lo comunique por este medio y proceda a
>>> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>>> reproducir, alterar, archivar o comunicar a terceros el presente mensaje
>> y
>>> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
>>> legales. Las opiniones contenidas en este mensaje y en los archivos
>>> adjuntos, pertenecen exclusivamente a su remitente y no representan la
>>> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
>>> remitente esté autorizado para ello. El emisor no garantiza la
>> integridad,
>>> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
>>> perjuicios derivados de la captura, incorporaciones de virus o
>>> cualesquiera
>>> otras manipulaciones efectuadas por terceros.
>>> 
>> 


-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 

Re: GSoC proposal for Redis Datastore

[Kevin Ratnasekera]

Hi Xavier,

The proposal you come up with looks very good. Added some comment on the
proposal. Please address before the final submission. Good luck with your
submission.

Regards
Kevin

On Mon, Apr 8, 2019 at 9:44 PM Madhawa Kasun Gunasekara 
wrote:

> Hi Xavier.
>
> Overall, The proposal looks good. I added some comments.
> Good Luck.
>
> Madhawa
>
>
> On Sat, Apr 6, 2019 at 10:09 PM Xavier Sumba
>  wrote:
>
> > Hi Carlos,
> >
> > Thanks so much for your suggestions. I already made the changes.
> >
> > Best,
> > Xavier.
> >
> > > On Apr 6, 2019, at 15:19, carlos muñoz  wrote:
> > >
> > > Hi Xavier.
> > >
> > > The proposal is looking really good. I added some minor comments.
> > >
> > > Good Luck.
> > >
> > > Regards,
> > > Carlos
> > >
> > > El sáb., 6 abr. 2019 a las 12:43, Xavier Sumba
> > > () escribió:
> > >
> > >> Hello,
> > >>
> > >> As discussed in Jira, I would like to participate in GSoC 2019. I have
> > >> been through a lot with finals and projects but I managed to write my
> > >> proposal and work in a small issue. Specifically, I want to work in
> the
> > >> support of Redis DB to Gora [1]. I also worked in the range queries
> for
> > >> Lucene and solved another issue with the conversion of datatypes, a
> pull
> > >> request can be found in [2]. I hope this issue can be merged by this
> > >> weekend :D
> > >>
> > >> Finally, I share my proposal for some feedback before submitting to
> > GSoC (
> > >>
> >
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> > >> <
> > >>
> >
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> > >).
> > >>
> > >>
> > >> Best regards,
> > >> Xavier.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/GORA-527 <
> > >> https://issues.apache.org/jira/browse/GORA-527>
> > >> [2] https://github.com/apache/gora/pull/158 <
> > >> https://github.com/apache/gora/pull/158>
> > >> --
> > >> Advertencia legal:
> > >> Este mensaje y, en su caso, los archivos anexos son
> > >> confidenciales, especialmente en lo que respecta a los datos
> > personales, y
> > >> se dirigen exclusivamente al destinatario referenciado. Si usted no lo
> > es
> > >> y
> > >> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> > >> motivo, le rogamos que nos lo comunique por este medio y proceda a
> > >> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> > >> reproducir, alterar, archivar o comunicar a terceros el presente
> > mensaje y
> > >> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> > >> legales. Las opiniones contenidas en este mensaje y en los archivos
> > >> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> > >> opinión de la Universidad de Cuenca salvo que se diga expresamente y
> el
> > >> remitente esté autorizado para ello. El emisor no garantiza la
> > integridad,
> > >> rapidez o seguridad del presente correo, ni se responsabiliza de
> > posibles
> > >> perjuicios derivados de la captura, incorporaciones de virus o
> > >> cualesquiera
> > >> otras manipulaciones efectuadas por terceros.
> > >>
> >
> >
> > --
> > Advertencia legal:
> > Este mensaje y, en su caso, los archivos anexos son
> > confidenciales, especialmente en lo que respecta a los datos personales,
> y
> > se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> > y
> > lo ha recibido por error o tiene conocimiento del mismo por cualquier
> > motivo, le rogamos que nos lo comunique por este medio y proceda a
> > destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> > reproducir, alterar, archivar o comunicar a terceros el presente mensaje
> y
> > ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> > legales. Las opiniones contenidas en este mensaje y en los archivos
> > adjuntos, pertenecen exclusivamente a su remitente y no representan la
> > opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> > remitente esté autorizado para ello. El emisor no garantiza la
> integridad,
> > rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> > perjuicios derivados de la captura, incorporaciones de virus o
> > cualesquiera
> > otras manipulaciones efectuadas por terceros.
> >
>

Re: GSoC proposal for Redis Datastore

[Madhawa Kasun Gunasekara]

Hi Xavier.

Overall, The proposal looks good. I added some comments.
Good Luck.

Madhawa


On Sat, Apr 6, 2019 at 10:09 PM Xavier Sumba
 wrote:

> Hi Carlos,
>
> Thanks so much for your suggestions. I already made the changes.
>
> Best,
> Xavier.
>
> > On Apr 6, 2019, at 15:19, carlos muñoz  wrote:
> >
> > Hi Xavier.
> >
> > The proposal is looking really good. I added some minor comments.
> >
> > Good Luck.
> >
> > Regards,
> > Carlos
> >
> > El sáb., 6 abr. 2019 a las 12:43, Xavier Sumba
> > () escribió:
> >
> >> Hello,
> >>
> >> As discussed in Jira, I would like to participate in GSoC 2019. I have
> >> been through a lot with finals and projects but I managed to write my
> >> proposal and work in a small issue. Specifically, I want to work in the
> >> support of Redis DB to Gora [1]. I also worked in the range queries for
> >> Lucene and solved another issue with the conversion of datatypes, a pull
> >> request can be found in [2]. I hope this issue can be merged by this
> >> weekend :D
> >>
> >> Finally, I share my proposal for some feedback before submitting to
> GSoC (
> >>
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> >> <
> >>
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> >).
> >>
> >>
> >> Best regards,
> >> Xavier.
> >>
> >> [1] https://issues.apache.org/jira/browse/GORA-527 <
> >> https://issues.apache.org/jira/browse/GORA-527>
> >> [2] https://github.com/apache/gora/pull/158 <
> >> https://github.com/apache/gora/pull/158>
> >> --
> >> Advertencia legal:
> >> Este mensaje y, en su caso, los archivos anexos son
> >> confidenciales, especialmente en lo que respecta a los datos
> personales, y
> >> se dirigen exclusivamente al destinatario referenciado. Si usted no lo
> es
> >> y
> >> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> >> motivo, le rogamos que nos lo comunique por este medio y proceda a
> >> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> >> reproducir, alterar, archivar o comunicar a terceros el presente
> mensaje y
> >> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> >> legales. Las opiniones contenidas en este mensaje y en los archivos
> >> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> >> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> >> remitente esté autorizado para ello. El emisor no garantiza la
> integridad,
> >> rapidez o seguridad del presente correo, ni se responsabiliza de
> posibles
> >> perjuicios derivados de la captura, incorporaciones de virus o
> >> cualesquiera
> >> otras manipulaciones efectuadas por terceros.
> >>
>
>
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> remitente esté autorizado para ello. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
>

Re: GSoC proposal for Redis Datastore

[Xavier Sumba]

Hi Carlos,

Thanks so much for your suggestions. I already made the changes.

Best,
Xavier.

> On Apr 6, 2019, at 15:19, carlos muñoz  wrote:
> 
> Hi Xavier.
> 
> The proposal is looking really good. I added some minor comments.
> 
> Good Luck.
> 
> Regards,
> Carlos
> 
> El sáb., 6 abr. 2019 a las 12:43, Xavier Sumba
> () escribió:
> 
>> Hello,
>> 
>> As discussed in Jira, I would like to participate in GSoC 2019. I have
>> been through a lot with finals and projects but I managed to write my
>> proposal and work in a small issue. Specifically, I want to work in the
>> support of Redis DB to Gora [1]. I also worked in the range queries for
>> Lucene and solved another issue with the conversion of datatypes, a pull
>> request can be found in [2]. I hope this issue can be merged by this
>> weekend :D
>> 
>> Finally, I share my proposal for some feedback before submitting to GSoC (
>> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
>> <
>> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing>).
>> 
>> 
>> Best regards,
>> Xavier.
>> 
>> [1] https://issues.apache.org/jira/browse/GORA-527 <
>> https://issues.apache.org/jira/browse/GORA-527>
>> [2] https://github.com/apache/gora/pull/158 <
>> https://github.com/apache/gora/pull/158>
>> --
>> Advertencia legal:
>> Este mensaje y, en su caso, los archivos anexos son
>> confidenciales, especialmente en lo que respecta a los datos personales, y
>> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
>> y
>> lo ha recibido por error o tiene conocimiento del mismo por cualquier
>> motivo, le rogamos que nos lo comunique por este medio y proceda a
>> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
>> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
>> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
>> legales. Las opiniones contenidas en este mensaje y en los archivos
>> adjuntos, pertenecen exclusivamente a su remitente y no representan la
>> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
>> remitente esté autorizado para ello. El emisor no garantiza la integridad,
>> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
>> perjuicios derivados de la captura, incorporaciones de virus o
>> cualesquiera
>> otras manipulaciones efectuadas por terceros.
>> 


-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 
reproducir, alterar, archivar o comunicar a terceros el presente mensaje y 
ficheros anexos, todo ello bajo pena de incurrir en responsabilidades 
legales. Las opiniones contenidas en este mensaje y en los archivos 
adjuntos, pertenecen exclusivamente a su remitente y no representan la 
opinión de la Universidad de Cuenca salvo que se diga expresamente y el 
remitente esté autorizado para ello. El emisor no garantiza la integridad, 
rapidez o seguridad del presente correo, ni se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualesquiera 
otras manipulaciones efectuadas por terceros.

Re: GSoC proposal for Redis Datastore

[carlos muñoz]

Hi Xavier.

The proposal is looking really good. I added some minor comments.

Good Luck.

Regards,
Carlos

El sáb., 6 abr. 2019 a las 12:43, Xavier Sumba
() escribió:

> Hello,
>
> As discussed in Jira, I would like to participate in GSoC 2019. I have
> been through a lot with finals and projects but I managed to write my
> proposal and work in a small issue. Specifically, I want to work in the
> support of Redis DB to Gora [1]. I also worked in the range queries for
> Lucene and solved another issue with the conversion of datatypes, a pull
> request can be found in [2]. I hope this issue can be merged by this
> weekend :D
>
> Finally, I share my proposal for some feedback before submitting to GSoC (
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
> <
> https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing>).
>
>
> Best regards,
> Xavier.
>
> [1] https://issues.apache.org/jira/browse/GORA-527 <
> https://issues.apache.org/jira/browse/GORA-527>
> [2] https://github.com/apache/gora/pull/158 <
> https://github.com/apache/gora/pull/158>
> --
> Advertencia legal:
> Este mensaje y, en su caso, los archivos anexos son
> confidenciales, especialmente en lo que respecta a los datos personales, y
> se dirigen exclusivamente al destinatario referenciado. Si usted no lo es
> y
> lo ha recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente mensaje y
> ficheros anexos, todo ello bajo pena de incurrir en responsabilidades
> legales. Las opiniones contenidas en este mensaje y en los archivos
> adjuntos, pertenecen exclusivamente a su remitente y no representan la
> opinión de la Universidad de Cuenca salvo que se diga expresamente y el
> remitente esté autorizado para ello. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de posibles
> perjuicios derivados de la captura, incorporaciones de virus o
> cualesquiera
> otras manipulaciones efectuadas por terceros.
>

GSoC proposal for Redis Datastore

[Xavier Sumba]

Hello,

As discussed in Jira, I would like to participate in GSoC 2019. I have been 
through a lot with finals and projects but I managed to write my proposal and 
work in a small issue. Specifically, I want to work in the support of Redis DB 
to Gora [1]. I also worked in the range queries for Lucene and solved another 
issue with the conversion of datatypes, a pull request can be found in [2]. I 
hope this issue can be merged by this weekend :D 

Finally, I share my proposal for some feedback before submitting to GSoC 
(https://docs.google.com/document/d/1uUBfuHk6KVtJ34jN5FziUEfu7_QGp2e3vcgBC_XO5Vk/edit?usp=sharing
 
).
 

Best regards,
Xavier.

[1] https://issues.apache.org/jira/browse/GORA-527 

[2] https://github.com/apache/gora/pull/158 
 
-- 
Advertencia legal: 
Este mensaje y, en su caso, los archivos anexos son 
confidenciales, especialmente en lo que respecta a los datos personales, y 
se dirigen exclusivamente al destinatario referenciado. Si usted no lo es y 
lo ha recibido por error o tiene conocimiento del mismo por cualquier 
motivo, le rogamos que nos lo comunique por este medio y proceda a 
destruirlo o borrarlo, y que en todo caso se abstenga de utilizar, 
reproducir, alterar, archivar o comunicar a terceros el presente mensaje y 
ficheros anexos, todo ello bajo pena de incurrir en responsabilidades 
legales. Las opiniones contenidas en este mensaje y en los archivos 
adjuntos, pertenecen exclusivamente a su remitente y no representan la 
opinión de la Universidad de Cuenca salvo que se diga expresamente y el 
remitente esté autorizado para ello. El emisor no garantiza la integridad, 
rapidez o seguridad del presente correo, ni se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualesquiera 
otras manipulaciones efectuadas por terceros.