Re: Gaby Ortiz accepted for Outreachy
Hi Gaby Congratulations and Welcome, Looking forward to your future contributions for the Apache Gora project.. Best regards, Carlos M. El dom, 29 nov 2020 a las 21:53, gabriela ortiz () escribió: > Hi John. > > Thank you all for your help, John, Alfonso, Carlos, and the other mentors. > > I look forward to working with you on the project. > > My Cwiki username is: mgov88 . > > Best regards, > Gaby > > > El sáb, 28 de nov. de 2020 a la(s) 11:52, John Mora (jhnmora...@gmail.com) > escribió: > > > Hi Gaby. > > > > Congratulations!!! and welcome on board. > > > > Please make sure you sign the internship agreement and follow all the > > instructions of the Outreachy program. > > > > Also, you will have to add a weekly report with progress on the Wiki of > > Apache Gora. You can use the GSoC reports as an example [1], but please > > create a new page for your project in the Outreachy section. And I > > recommend that you upload your proposed timeline and basic information of > > the project on another page similar to this [2], you can copy & paste the > > contents of the project description on the Outreachy platform. > > > > BTW, I think Kevin Ratnasekera can grant permissions on Cwiki, please > send > > us your username of cwiki. > > > > Best, > > John > > > > [1] > > > https://cwiki.apache.org/confluence/display/GORA/Arango+datastore+reports > > > > [2] > > > https://cwiki.apache.org/confluence/display/GORA/ArangoDB+Datastore+Proposal > > > > [3] > > > https://cwiki.apache.org/confluence/display/GORA/Outreachy%3A+December+2020+-+March+2021 > > > > > > -- Forwarded message - > > De: Outreachy Organizers > > Date: lun, 23 nov 2020 a las 11:01 > > Subject: Gaby Ortiz accepted for Outreachy > > To: Gaby Ortiz , djkevincr < > > djkevincr1...@gmail.com>, John Mora , madhawa < > > madh...@apache.org>, Carlos Muñoz , Matt Sicker < > > boa...@gmail.com>, Awasum Yannick , Katia Rojas < > > ka...@apache.org> > > > > > > Congratulations on being accepted for the December 2020 to March 2021 > > Outreachy internship round! > > > > You have been selected as an intern for Apache working with your mentors > > djkevincr and John Mora and madhawa and Carlos Muñoz on the project "Add > a > > datastore for Neo4j in Apache Gora". The Apache coordinators are Matt > > Sicker and Awasum Yannick and Katia Rojas, who are on Cc. > > > > If you don't plan on participating as an intern, please let us know as > > soon as possible. The later you wait, the less likely it is we'll be able > > to fill the internship with another candidate. > > > > Time Commitment > > --- > > > > Your approval to participate in Outreachy is based on the time > commitments > > you listed in your initial application: > > https://www.outreachy.org/eligibility-results/ > > > > If your time commitments are incorrect or have changed (such as if you > > have a job that is not listed on your initial application), please > contact > > us immediately. > > > > Minimum hours per week policy: > > - If an intern's school terms have shifted due to COVID-19 impacts, they > > will only be required to work 10 hours a week during classes and exams. > > - If an intern is otherwise impacted by COVID-19, they will only be > > required to work 30 hours a week. > > - Interns who are not impacted by COVID-19 are required to work 40 hours > > a week. > > - Please read our COVID-19 policy for this round for details: > > > https://www.outreachy.org/blog/2020-08-28/december-2020-internship-applications-open//#covid-19 > > > > Interns are required to work for 12 weeks of the Outreachy internship's > 13 > > week duration. > > > > Please reach out to your mentor if you are impacted by COVID-19. You'll > > need to create a plan for a reduced project timeline. > > > > Internship Guide > > > > > > Please bookmark the Outreachy Internship Guide: > > > > https://www.outreachy.org/docs/internship/ > > > > The internship guide has important dates such as feedback deadlines, > > payment dates, and intern/mentor chat dates. It also provides information > > on blog prompt topics and dates. > > > > What happens next > > - > > > > This email outlines the next steps for participating in the program, so > > please read it carefully. The first most important steps
Re: Maria Podorvanova accepted for Outreachy
Congratulations Maria, Looking forward for your contributions in Apache Gora. Cheers, Carlos M. El sáb, 28 nov 2020 a las 11:51, John Mora () escribió: > Hi Maria. > > Congratulations!!! and welcome on board. > > Please make sure you sign the internship agreement and follow all the > instructions of the Outreachy program. > > Also, you will have to add a weekly report with progress on the Wiki of > Apache Gora. You can use the GSoC reports as an example [1], but please > create a new page for your project in the Outreachy section. And I > recommend that you upload your proposed timeline and basic information of > the project on another page similar to this [2], you can copy & paste the > contents of the project description on the Outreachy platform. > > BTW, I think Kevin Ratnasekera can grant permissions on Cwiki, please send > us your username of cwiki. > > Best, > John > > [1] > https://cwiki.apache.org/confluence/display/GORA/Arango+datastore+reports > > [2] > > https://cwiki.apache.org/confluence/display/GORA/ArangoDB+Datastore+Proposal > > [3] > > https://cwiki.apache.org/confluence/display/GORA/Outreachy%3A+December+2020+-+March+2021 > > > > -- Forwarded message - > De: Outreachy Organizers > Date: lun, 23 nov 2020 a las 11:01 > Subject: Maria Podorvanova accepted for Outreachy > To: Maria Podorvanova , djkevincr < > djkevincr1...@gmail.com>, John Mora , madhawa < > madh...@apache.org>, Carlos Muñoz , Matt Sicker < > boa...@gmail.com>, Awasum Yannick , Katia Rojas < > ka...@apache.org> > > > Congratulations on being accepted for the December 2020 to March 2021 > Outreachy internship round! > > You have been selected as an intern for Apache working with your mentors > djkevincr and John Mora and madhawa and Carlos Muñoz on the project "Add a > datastore for Elasticsearch in Apache Gora". The Apache coordinators are > Matt Sicker and Awasum Yannick and Katia Rojas, who are on Cc. > > If you don't plan on participating as an intern, please let us know as soon > as possible. The later you wait, the less likely it is we'll be able to > fill the internship with another candidate. > > Time Commitment > --- > > Your approval to participate in Outreachy is based on the time commitments > you listed in your initial application: > https://www.outreachy.org/eligibility-results/ > > If your time commitments are incorrect or have changed (such as if you have > a job that is not listed on your initial application), please contact us > immediately. > > Minimum hours per week policy: > - If an intern's school terms have shifted due to COVID-19 impacts, they > will only be required to work 10 hours a week during classes and exams. > - If an intern is otherwise impacted by COVID-19, they will only be > required to work 30 hours a week. > - Interns who are not impacted by COVID-19 are required to work 40 hours a > week. > - Please read our COVID-19 policy for this round for details: > > https://www.outreachy.org/blog/2020-08-28/december-2020-internship-applications-open//#covid-19 > > Interns are required to work for 12 weeks of the Outreachy internship's 13 > week duration. > > Please reach out to your mentor if you are impacted by COVID-19. You'll > need to create a plan for a reduced project timeline. > > Internship Guide > > > Please bookmark the Outreachy Internship Guide: > > https://www.outreachy.org/docs/internship/ > > The internship guide has important dates such as feedback deadlines, > payment dates, and intern/mentor chat dates. It also provides information > on blog prompt topics and dates. > > What happens next > - > > This email outlines the next steps for participating in the program, so > please read it carefully. The first most important steps are: > > 1. Log into the Outreachy website and click the 'Accept Internship' button > on your dashboard: https://www.outreachy.org/dashboard This will prompt > you > to sign the internship agreement. > > 2. Double check that your public information on the announcement page is > correct: https://www.outreachy.org/alums/ If you want to add a photo or > you > need any changes, you can change your public name, location, pronouns (and > their public visibility settings), and links to Twitter, GitLab, and GitHub > on your account page. https://www.outreachy.org/account/ > > 3. Set an email filter to ensure all emails from outreachy.org and > sfconservancy.org go to your Inbox. > > 4. Respond to the Software Freedom Conservancy with your tax form W-9 or > W8-BEN by Dec. 11, 2020. > > 5. Create a blog
Outreachy 2020 deadline
Hi Outreachy applicants. Just a reminder of the contribution period deadline of Outreachy. According to the Outreachy website: In order to be eligible to be selected as an Outreachy intern, each applicant must: 1. Fill out an initial application at https://www.outreachy.org/eligibility/ 2. Record a contribution to your project on the Outreachy site. 3. Complete a final application for your project. The deadline for final applications is Oct. 31, 2020 at 4pm UTC. Applicants will not be able to create a final application after the deadline. Applicants can edit their final application until the deadline. Cheers, Carlos
Re: [WELCOME] John Mora to Gora PMC and Committership
Hi John, Congrats and welcome onboard! Best, Carlos El mar., 15 oct. 2019 a las 6:01, Renato Marroquín Mogrovejo (< renatoj.marroq...@gmail.com>) escribió: > Congrats John! Welcome onboard! > > El mar., 15 oct. 2019 a las 11:32, Furkan KAMACI > () escribió: > > > > Hi, > > > > Congrats and welcome on board John! > > > > Kind Regards, > > Furkan KAMACI > > > > 15 Eki 2019 Sal, saat 12:13 tarihinde Sheriffo Ceesay < > sheri...@apache.org> > > şunu yazdı: > > > > > Congratulations John! Welcome onboard. > > > > > > Sheriffo. > > > > > > On Tue, Oct 15, 2019 at 7:57 AM Cihad Guzel wrote: > > > > > > > Congratulations and Welcome John! > > > > > > > > Cihad Guzel > > > > > > > > > > > > Alfonso Nishikawa , 13 Eki 2019 Paz, > 19:54 > > > > tarihinde şunu yazdı: > > > > > > > > > Hi Gora Community, > > > > > > > > > > I'm very happy to welcome John Mora to our ranks. He has > implemented > > > the > > > > > module gora-kudu this Google Summer of Code. > > > > > John, your account has been created, so you can try your first push > > > > > updating the Gora parent pom.xml [1] and the project webpage [2] > with a > > > > > reference to yourself [1]. If you need some assistance with that > then > > > > > please let me know. > > > > > > > > > > [1] https://github.com/apache/gora/blob/master/pom.xml > > > > > [2] http://gora.apache.org/credits.html > > > > > > > > > > Regards, > > > > > > > > > > Alfonso Nishikawa > > > > > > > > > > > > >
Re: Add GoraExplorer at Related Projects section
Hi, +1 Cheers, Carlos El jue., 5 sept. 2019 a las 6:34, Cihad Guzel () escribió: > +1 > > Cihad Güzel > > > Furkan KAMACI , 5 Eyl 2019 Per, 07:58 tarihinde > şunu yazdı: > > > Hi Alfonso, > > > > Sure! +1. > > > > Kind Regards, > > Furkan KAMACI > > > > 5 Eyl 2019 Per, saat 07:48 tarihinde Kevin Ratnasekera < > > djkevincr1...@gmail.com> şunu yazdı: > > > > > +1 > > > > > > On Thu, Sep 5, 2019 at 2:17 AM Alfonso Nishikawa < > > > alfonso.nishik...@gmail.com> wrote: > > > > > > > Hi! > > > > > > > > I have been thiking about adding GoraExplorer [1] to the Related > > Projects > > > > section of the web, although it is in alpha stage. > > > > Since I would be adding my own project, is everyone OK with that? :) > > > > > > > > [1] https://www.goraexplorer.com/ > > > > [2] http://gora.apache.org/related.html > > > > > > > > Thank you! > > > > > > > > Regards, > > > > > > > > Alfonso Nishikawa > > > > > > > > > >
Re: Kudu datastore reports
itting [7] >>>>>>>- Cassandra store implementation does not implement splitting [8] >>>>>>>- Aerospike store implementation does not implement splitting [9] >>>>>>>- Accumulo store implementation* does* implement splitting [10] >>>>>>> >>>>>>> If Kudu has a method to get the different splits for a table and its >>>>>>> locations, then you will be able to implement the full feature. >>>>>>> >>>>>>> This is Hadoop related and it is not trivial. I haven't elaborated >>>>>>> much, so if you find you need more information let me know :) >>>>>>> >>>>>>> >>>>>>> >>>>>> I will check whether Kudu has these features in order to implement >>>>>> this method. If not I will use the default implementation found in other >>>>>> backends. >>>>>> >>>>>> >>>>>>> About Queries, what I can tell is that Hbase only implements "Start >>>>>>> key" + "End key" because it has only 2 operations: "get" and "scan", and >>>>>>> the querying is for "scan" operation, were you want an interval (or >>>>>>> all) of >>>>>>> the rows. Does Kudu have more querying functionality? >>>>>>> >>>>>>> >>>>>> Yes, Kudu implements a Scanner for querying data among with >>>>>> conditional predicates for filtering. I am using those classes. >>>>>> >>>>>> >>>>>>> About other topic, I am trying to install Kudu in standalone (all in >>>>>>> 1 node). Do you use a Cloudera installation or do you have a standalone >>>>>>> installation? How do you do it? I found some instructions, but they talk >>>>>>> about compiling Kudu [11]. I was looking for something like HBase, that >>>>>>> it >>>>>>> is unzip + execute "hbase start". >>>>>>> >>>>>>> >>>>>> I am using an embedded mini-cluster which comes with compiled >>>>>> binaries and can be used with maven[1] for testing my code. Once I get it >>>>>> mature enough I think I will be testing the datastore with a docker >>>>>> container [2]. I could not find a unzip+execute bundle either and I am >>>>>> kinda noob for compiling it myself. >>>>>> >>>>>> [1] >>>>>> https://kudu.apache.org/docs/developing.html#_jvm_based_integration_testing >>>>>> [2] https://hub.docker.com/r/usuresearch/apache-kudu/ >>>>>> >>>>>> >>>>>>> Good job and thank you!! :) >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Alfonso Nishikawa >>>>>>> >>>>>>> >>>>>>> [1] - https://avro.apache.org/docs/1.8.0/spec.html#Logical+Types >>>>>>> [2] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L175 >>>>>>> [3] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L458 >>>>>>> [4] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L472 >>>>>>> [5] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L479 >>>>>>> [6] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L517 >>>>>>> [7] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java#L533 >>>>>>> [8] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraStore.java#L292 >>>>>>> [9] - >>>>>>> https://github.com/apache/gora/blob/apache-gora-0.9/gora-aerospike/src/main/java/org/apache
Re: Kudu datastore reports
Hi John The first Google Summer of Code evaluation is due on June 28th. Please make sure you submit your Mentors' evaluation on time. Regards, Carlos El dom., 23 jun. 2019 a las 18:29, John Mora () escribió: > Hi all. > > FYI, I updated my report of this week on the Wiki[1]. Also, I pushed my > last commits to my branch [2]. > > As I mentioned in the reports I would like to know how datastores deal > with flush(), should it work always manually executed?. > > Finally, This week I will be implementing object > serialization/deserialization in the methods put, get, delete, exists. Do > you have any suggestions on how to proceed with this task?. > > Footnote: Thanks for the feedback Carlos, I fixed the problem. > > [1] > https://cwiki.apache.org/confluence/display/GORA/GORA-485+Apache+Kudu+datastore+for+Gora+Reports > [2] https://github.com/jhnmora000/gora/tree/GORA-485 > > Cheers, > John > > > El lun., 17 jun. 2019 a las 22:58, carlos muñoz () > escribió: > >> Hi John >> >> Your last changes look good to me. Keep it up. But, I noticed that you >> have created an Enumeration for datatypes, which is very similar to the >> kudu-client's [2]. Probably you should replace [1] for [2] in order to >> avoid code duplication. >> >> [1] >> https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/main/java/org/apache/gora/kudu/mapping/Column.java#L76 >> [2] https://kudu.apache.org/apidocs/org/apache/kudu/Type.html >> >> >> Best, >> Carlos >> >> El sáb., 15 jun. 2019 a las 12:01, John Mora () >> escribió: >> >>> Hi all. >>> >>> I updated my report of this week on the Wiki[1]. I noticed that my code >>> is lacking some javadoc documentation I think I will be working on that >>> this week, also I would like to enable and check schema management tests >>> (createSchema, existsSchema, etc.). >>> >>> [1] >>> https://cwiki.apache.org/confluence/display/GORA/GORA-485+Apache+Kudu+datastore+for+Gora+Reports >>> >>> Cheers, >>> John. >>> >>> >>> El mar., 11 jun. 2019 a las 0:11, John Mora () >>> escribió: >>> >>>> Hi Alfonso. >>>> >>>> Thanks so much for your feedback. I am working on your comments. >>>> >>>> Best, >>>> John >>>> >>>> El lun., 10 jun. 2019 a las 16:11, Alfonso Nishikawa (< >>>> alfonso.nishik...@gmail.com>) escribió: >>>> >>>>> Hi, John. >>>>> >>>>> Regarding your questions at the report [1]: >>>>> >>>>> >>>>>- How to represent partitioning configurations on the mapping file. >>>>> >>>>> This was discussed in other emails, isn't it? :) >>>>> >>>>>- KuduTestHarness requires the Maven plugin os-maven-plugin, which >>>>>needs Maven 3.1.1+, is it a problem for Apache Gora? >>>>> >>>>> I believe it is not a problem. My Ubuntu comes with 3.6.0, far from >>>>> 3.1.1, and I assume everyone uses Maven 3 in a quite new version :) >>>>> >>>>> [1] - >>>>> https://cwiki.apache.org/confluence/display/GORA/GORA-485+Apache+Kudu+datastore+for+Gora+Reports >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Alfonso Nishikawa >>>>> >>>>> >>>>> El lun., 10 jun. 2019 a las 21:07, Alfonso Nishikawa (< >>>>> alfonso.nishik...@gmail.com>) escribió: >>>>> >>>>>> Hi, John. >>>>>> >>>>>> Thank you! >>>>>> Things I have seen: >>>>>> >>>>>> - The version of a maven dependency [1] should go on the Dependency >>>>>> Management of the root pom [2]. Same for [3] and from there, should not >>>>>> set >>>>>> the version there. >>>>>> - Set test dependencies' scope to test, at [4] and from there. >>>>>> - Set the indentation to 2 spaces for the pom [5] >>>>>> - Missing "t" in "localhost" at [6]. >>>>>> - Port 13 for Kudu? That is "Daytime Protocol" RFC 867 and you will >>>>>> need root permission to run it. The default port for kudu is 7051, isn't >>>>>> it? >>>>>> - I would ask you to add the same functionality to load the mapping >>>>>> from conf
Re: Kudu datastore reports
Hi John Your last changes look good to me. Keep it up. But, I noticed that you have created an Enumeration for datatypes, which is very similar to the kudu-client's [2]. Probably you should replace [1] for [2] in order to avoid code duplication. [1] https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/main/java/org/apache/gora/kudu/mapping/Column.java#L76 [2] https://kudu.apache.org/apidocs/org/apache/kudu/Type.html Best, Carlos El sáb., 15 jun. 2019 a las 12:01, John Mora () escribió: > Hi all. > > I updated my report of this week on the Wiki[1]. I noticed that my code is > lacking some javadoc documentation I think I will be working on that this > week, also I would like to enable and check schema management tests > (createSchema, existsSchema, etc.). > > [1] > https://cwiki.apache.org/confluence/display/GORA/GORA-485+Apache+Kudu+datastore+for+Gora+Reports > > Cheers, > John. > > > El mar., 11 jun. 2019 a las 0:11, John Mora () > escribió: > >> Hi Alfonso. >> >> Thanks so much for your feedback. I am working on your comments. >> >> Best, >> John >> >> El lun., 10 jun. 2019 a las 16:11, Alfonso Nishikawa (< >> alfonso.nishik...@gmail.com>) escribió: >> >>> Hi, John. >>> >>> Regarding your questions at the report [1]: >>> >>> >>>- How to represent partitioning configurations on the mapping file. >>> >>> This was discussed in other emails, isn't it? :) >>> >>>- KuduTestHarness requires the Maven plugin os-maven-plugin, which >>>needs Maven 3.1.1+, is it a problem for Apache Gora? >>> >>> I believe it is not a problem. My Ubuntu comes with 3.6.0, far from >>> 3.1.1, and I assume everyone uses Maven 3 in a quite new version :) >>> >>> [1] - >>> https://cwiki.apache.org/confluence/display/GORA/GORA-485+Apache+Kudu+datastore+for+Gora+Reports >>> >>> >>> Regards, >>> >>> Alfonso Nishikawa >>> >>> >>> El lun., 10 jun. 2019 a las 21:07, Alfonso Nishikawa (< >>> alfonso.nishik...@gmail.com>) escribió: >>> Hi, John. Thank you! Things I have seen: - The version of a maven dependency [1] should go on the Dependency Management of the root pom [2]. Same for [3] and from there, should not set the version there. - Set test dependencies' scope to test, at [4] and from there. - Set the indentation to 2 spaces for the pom [5] - Missing "t" in "localhost" at [6]. - Port 13 for Kudu? That is "Daytime Protocol" RFC 867 and you will need root permission to run it. The default port for kudu is 7051, isn't it? - I would ask you to add the same functionality to load the mapping from configuration as in HBase's store [7] in you KuduStore [8]. This will have implications on your readMapping at [9], so take a look at the one for HBase at [10] - I know it is in other backends, but avoid RuntimeExceptions (at least in Java since we have the checked ones) like in [11]. You can wrap them in GoraException. An example is [12] And nothing more :) Keep going, good job. [1] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/pom.xml#L98 [2] - https://github.com/jhnmora000/gora/blob/GORA-485/pom.xml#L890 [3] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/pom.xml#L121 [4] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/pom.xml#L180 [5] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/pom.xml [6] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/test/resources/gora.properties#L18 [7] - https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L92 [8] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/main/java/org/apache/gora/kudu/store/KuduStore.java#L53 [9] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/main/java/org/apache/gora/kudu/mapping/KuduMappingBuilder.java#L81 [10] - https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L822 [11] - https://github.com/jhnmora000/gora/blob/GORA-485/gora-kudu/src/main/java/org/apache/gora/kudu/mapping/KuduMappingBuilder.java#L141 [12] - https://github.com/jhnmora000/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L268 Regards, Alfonso Nishikawa El sáb., 8 jun. 2019 a las 20:26, John Mora () escribió: > Hi all. > > I have just updated my weekly reports on Cwiki [1]. This next week I > think I should be focusing on the create schema operation and solving the > issue of the partitioning configurations in the mapping file. > > Please let me know if you have suggestions, my last commits are > available here [2] > > [1] >
Re: Redis datastore
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 pu
Re: Redis datastore
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
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: [VOTE] RC01 for Apache Gora 0.9 Release
+1 Release this package as Apache Gora 0.9 Regards, Carlos El vie., 10 may. 2019 a las 11:46, Madhawa Kasun Gunasekara (< madhaw...@gmail.com>) escribió: > +1 Release this package as Apache Gora 0.9 > > Tested Cassandra and Solr module. > > Thanks, > Madhawa > > > On Wed, May 8, 2019 at 11:59 AM Kevin Ratnasekera > > wrote: > > > Hi all, > > > > This is the vote on first release candidate (RC01) for next Apache > > > > Gora release version 0.9. > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Gora 0.9 ... > > > > [ ] -1 Do not release this package because … > > > > 38 tickets were resolved and release report is available here : > > > > https://s.apache.org/0.9GoraReleaseNotes > > > > Source release artifacts are available here : > > > > https://dist.apache.org/repos/dist/dev/gora/apache-gora-0.9-RC01/ > > > > Staging repository is available here : > > > > https://repository.apache.org/content/repositories/orgapachegora-1010 > > > > Release candidate is signed through the key A3E66AC7 which is available > > here : > > > > https://dist.apache.org/repos/dist/dev/gora/KEYS > > > > The release candidate is based on the sources tagged with > apache-gora-0.9: > > > > > > > https://gitbox.apache.org/repos/asf?p=gora.git;a=tag;h=61b9a928a076a52a39f1b0771798bbae4742fffc > > > > and is based on the following commit id: > > > > 4b27f2bfebee1a77f9b957929c956ea1b509f9fb > > > > Thank you to everyone that contributed to Apache Gora 0.9 and who are > able > > to vote on the release candidate. > > > > PS: My vote is `[x] +1 Release this package as Apache Gora 0.9`. > > > > Regards > > > > Kevin > > > > >
Re: GSoC proposal for Redis Datastore
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. >
Re: Student proposal for GSOC 2019
Thanks Lahiru. Nice work, I have left a few comments. Regards, Carlos. El lun., 1 abr. 2019 a las 22:22, Lahiru Jayasekera (< mlpjayasek...@gmail.com>) escribió: > Hi Carols, > Enabled the comments. Please add your comments. > > > https://docs.google.com/document/d/1jt1bVlcVyDk1cytS8g-oNJoqZ9hminHWUsY5vBAmvQc/edit?usp=drivesdkr > > Thanks and regards > > On Tue, Apr 2, 2019, 08:38 carlos muñoz > > Hi Lahiru, > > > > Thanks for your interest in Apache Gora. > > The proposal looks interesting, could you please enable the suggestions > > mode on the document?. > > I would like to leave a couple of comments. > > > > Cheers, > > Carlos > > > > > > El lun., 1 abr. 2019 a las 14:06, Lahiru Jayasekera (< > > mlpjayasek...@gmail.com>) escribió: > > > > > Hi all, > > > I would like to do the project "Hazelcast Jet execution engine > > support"[1], > > > for gsoc 2019. I have created a proposal with the help of you. I have > > > attached the draft proposal here and would like to get your kind feed > > back. > > > > > > > > > > > > https://docs.google.com/document/d/1jt1bVlcVyDk1cytS8g-oNJoqZ9hminHWUsY5vBAmvQc/edit?usp=sharing > > > > > > Thanks and Regards > > > Lahiru > > > > > > 1. https://issues.apache.org/jira/browse/GORA-546 > > > > > > -- > > > Lahiru Jayasekara > > > Batch 15 > > > Faculty of Information Technology > > > University of Moratuwa > > > 0716492170 > > > > > >
Re: Student proposal for Google Summer of Code 2019
Hi John. Nice work, the proposal looks promising. I have left a few comments. Best, Carlos El vie., 29 mar. 2019 a las 18:48, John Mora () escribió: > Hi all. > > As I stated on Jira[1] I would like to apply to the Google summer of Code > program with Apache Gora. I have wrote a proposal for the issue and I would > like to share it with you. Could you please give some feedback?. > > > https://docs.google.com/document/d/1ShGFZNmbhbZoLBC7WpmLnloOOAOXLcqfY9VSGOD09cg/edit?usp=sharing > > > Regards, > John. > > [1] https://issues.apache.org/jira/browse/GORA-485 >
Re: Student proposal for GSOC 2019
Hi Lahiru, Thanks for your interest in Apache Gora. The proposal looks interesting, could you please enable the suggestions mode on the document?. I would like to leave a couple of comments. Cheers, Carlos El lun., 1 abr. 2019 a las 14:06, Lahiru Jayasekera (< mlpjayasek...@gmail.com>) escribió: > Hi all, > I would like to do the project "Hazelcast Jet execution engine support"[1], > for gsoc 2019. I have created a proposal with the help of you. I have > attached the draft proposal here and would like to get your kind feed back. > > > https://docs.google.com/document/d/1jt1bVlcVyDk1cytS8g-oNJoqZ9hminHWUsY5vBAmvQc/edit?usp=sharing > > Thanks and Regards > Lahiru > > 1. https://issues.apache.org/jira/browse/GORA-546 > > -- > Lahiru Jayasekara > Batch 15 > Faculty of Information Technology > University of Moratuwa > 0716492170 >
Re: [GSoC 2018] Ignite backend - Status
Hi all. I am working on the changes that you guys suggested and other small improvements. I hope I will be pushing my commits by Thursday. In the meantime, I would like to update Gora's Wiki with details of the project within the GSoC section [1], so I would highly appreciate you grant me write access (my cwiki username: carlosrmng email: carlosr...@gmail.com). BTW, thanks so much for your feedback and support :D Regards, Carlos. [1] https://cwiki.apache.org/confluence/display/GORA/Google+Summer+of+Code 2018-07-17 3:35 GMT-05:00 Alfonso Nishikawa : > > @Lewis, @Nishadi, wow you did a very thorough review, congrats =) I was > liking your comments, but I guess is better just to say I subscribe all > your coments (except one, but already commented :) > > Loooking forward those changes. Carlos, cheer up! :) > Thanks! > > Regards, > > Alfonso > > > > 2018-07-15 7:05 GMT-01:00 Nishadi Kirielle : > >> Hi Carlos, >> >> This is great work..!!! >> I have gone through your code and added some comments. Please have a look >> at them and let me know if you need further clarifications. >> >> Regards, >> Nishadi >> >> On Sun, Jul 8, 2018 at 1:04 AM Lewis John Mcgibbney < >> lewis.mcgibb...@gmail.com> wrote: >> >> > Hi Carlos, I’ll reciew by end of weekend this is an excellent effort >> thank >> > you. >> > Lewis >> > >> > On Sat, Jul 7, 2018 at 07:30 carlos muñoz wrote: >> > >> >> Hi. >> >> >> >> Just a quick update of the project. >> >> >> >> I just have sent a PR [1] with the initial Ignite Backend >> implementation. >> >> All the tests are passing, but I would like to check the code in other >> to >> >> improve it and catch possible errors. So I would highly appreciacte if >> you >> >> review it. >> >> Also, I would like to work on some documentation of the new backend. >> >> Where does the Gora's website code live? and how can I edit it?. >> >> >> >> Best, >> >> Carlos >> >> >> >> [1] https://github.com/apache/gora/pull/134 >> >> >> > -- >> > >> > *Lewis* >> > Dr. Lewis J. McGibbney Ph.D, B.Sc >> > *Skype*: lewis.john.mcgibbney >> > >> > >> > >> > >> > >
Re: GoraExplorer update
Congratulations Alfonso !!! Sorry for the typo :) Carlos 2018-07-07 9:33 GMT-05:00 carlos muñoz : > Congratulations Alonso !!! :D > > Carlos > > 2018-07-06 6:53 GMT-05:00 Renato Marroquín Mogrovejo < > renatoj.marroq...@gmail.com>: > >> Congrats on the degree Alonso! >> >> 2018-07-05 23:18 GMT+02:00 lewis john mcgibbney : >> >> > Nice Alfonso. Congratulations on your degree. >> > Lewis >> > >> > On Thu, Jul 5, 2018 at 14:10 wrote: >> > >> > > >> > > dev Digest 5 Jul 2018 21:10:59 - Issue 1056 >> > > >> > > Topics (messages 10639 through 10639) >> > > >> > > GoraExplorer update >> > > 10639 by: Alfonso Nishikawa >> > > >> > > Administrivia: >> > > >> > > - >> > > To post to the list, e-mail: dev@gora.apache.org >> > > To unsubscribe, e-mail: dev-digest-unsubscr...@gora.apache.org >> > > For additional commands, e-mail: dev-digest-h...@gora.apache.org >> > > >> > > >> -- >> > > >> > > >> > > >> > > >> > > -- Forwarded message -- >> > > From: Alfonso Nishikawa >> > > To: "" >> > > Cc: >> > > Bcc: >> > > Date: Thu, 5 Jul 2018 20:10:15 -0100 >> > > Subject: GoraExplorer update >> > > Hi everyone! >> > > >> > > I finally finished a Degree in Software Engineering. I have been >> offline >> > > for more than 2 months redacting the report, but now I am back :) >> > > >> > > I will create a landing page for GoraExplorer. >> > > I will finish the gora-pig details webpage. >> > > I would want to integrate some needed functionalities to gora-core and >> > > small changes to backends to fully support creating the datastores >> with >> > > code configuration (instead on relying on files). >> > > >> > > Stay tuned :) >> > > >> > > Regards, >> > > >> > > Alfonso Nishikawa >> > > >> > -- >> > http://home.apache.org/~lewismc/ >> > http://people.apache.org/keys/committer/lewismc >> > >> > >
Re: GoraExplorer update
Congratulations Alonso !!! :D Carlos 2018-07-06 6:53 GMT-05:00 Renato Marroquín Mogrovejo < renatoj.marroq...@gmail.com>: > Congrats on the degree Alonso! > > 2018-07-05 23:18 GMT+02:00 lewis john mcgibbney : > > > Nice Alfonso. Congratulations on your degree. > > Lewis > > > > On Thu, Jul 5, 2018 at 14:10 wrote: > > > > > > > > dev Digest 5 Jul 2018 21:10:59 - Issue 1056 > > > > > > Topics (messages 10639 through 10639) > > > > > > GoraExplorer update > > > 10639 by: Alfonso Nishikawa > > > > > > Administrivia: > > > > > > - > > > To post to the list, e-mail: dev@gora.apache.org > > > To unsubscribe, e-mail: dev-digest-unsubscr...@gora.apache.org > > > For additional commands, e-mail: dev-digest-h...@gora.apache.org > > > > > > -- > > > > > > > > > > > > > > > -- Forwarded message -- > > > From: Alfonso Nishikawa > > > To: "" > > > Cc: > > > Bcc: > > > Date: Thu, 5 Jul 2018 20:10:15 -0100 > > > Subject: GoraExplorer update > > > Hi everyone! > > > > > > I finally finished a Degree in Software Engineering. I have been > offline > > > for more than 2 months redacting the report, but now I am back :) > > > > > > I will create a landing page for GoraExplorer. > > > I will finish the gora-pig details webpage. > > > I would want to integrate some needed functionalities to gora-core and > > > small changes to backends to fully support creating the datastores with > > > code configuration (instead on relying on files). > > > > > > Stay tuned :) > > > > > > Regards, > > > > > > Alfonso Nishikawa > > > > > -- > > http://home.apache.org/~lewismc/ > > http://people.apache.org/keys/committer/lewismc > > >
[GSoC 2018] Ignite backend - Status
Hi. Just a quick update of the project. I just have sent a PR [1] with the initial Ignite Backend implementation. All the tests are passing, but I would like to check the code in other to improve it and catch possible errors. So I would highly appreciacte if you review it. Also, I would like to work on some documentation of the new backend. Where does the Gora's website code live? and how can I edit it?. Best, Carlos [1] https://github.com/apache/gora/pull/134
[GSOC 2018] Ignite Backend - Composite primary key.
Hi. While implementing some functionalities of the new Ignite backend, I noticed that Ignite supports composite primary keys. So I wondered if such feature could be useful within Gora or it is better to restrict persistent entities to have a single primary key field. Have other backends already dealt with that?. Regards. Carlos
Re: [GSoC 2018] Ignite Backend - Status
Hi all As Alfonso mentioned the Ignite backend could implement the 3-union fields either by using joined tables or storing serialized objects as binary. Here some comments on those approaches. Using joined tables would definitely has an impact in performance due the fact distributed joins [1] imply some subquery/aggregation overhead. Moreover, the efficiency and results of such joins will depend on the specific configuration used into the Ignite Cluster. On the other hand, from a developing point of view, explicitly referencing persistent entities within class mapping (JPA - like ) will introduce some complexity to the project (fetching strategies, relations handling, etc.) and as far I understand Apache Gore was not conceived in that way. Serializing objects on the other hand sticks to other backends implementation as I noticed while analyzing Gora code. It seems to keep code simple and IO operations efficient due the fact that embedded persistent entities are stored as simple literals into the data stores. In addition, Ignite has the data type BINARY [2] which suits the needs of such fields. In a nutshell, I suggest taking the serialization approach and adapting other backends implementation of 3-union fields in the Ignite backend. But I am not really an expert on the subject so please feel free to give your feedback. [1] https://apacheignite-sql.readme.io/docs/distributed-joins [2] https://apacheignite-sql.readme.io/docs/data-types#section-binary 2018-06-06 5:05 GMT-05:00 Alfonso Nishikawa : > Hi, Carlos. > > About the mapping files and the fields 'boss' and 'webpage', yes, they > reference two other Persistent entities. You can see the schema of Employee > [1], were it has a boss (referencing itself) and a webpage (with the > WebPage schema defined there). > > How to handle this depends on the actual backend. In HBase we serialize > with avro each of the fields that are Persistent entities as shown at [2] > (we get there from [3] > [4] > [5], but this is for HBase). > On the other hand, if I am not worng, MongoDB Store has no problem with > hierarchical data, so it just writes it as it is. > > In your case, it depends on the features of your backend and what approach > wold be better overall. I am seeing that Ignite has SQL + key/value > properties... how interesting :) > I know nothing about, but I would think about the performance costs of > joined tables, the possibility of mapping each persistent into a table, or > the approach like HBase serializing (as a key/value store). Or maybe Ignite > has some functionality for complex data. > Just thinking about it without knowing. > > If I left things unclear don't doubt to ask :) > > Regards, > > Alfonso > > > [1] > https://github.com/apache/gora/blob/apache-gora-0.8/ > gora-core/src/examples/avro/employee.json > [2] > https://github.com/apache/gora/blob/apache-gora-0.8/ > gora-hbase/src/main/java/org/apache/gora/hbase/util/ > HBaseByteInterface.java#L233 > [3] > https://github.com/apache/gora/blob/apache-gora-0.8/ > gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L240 > [4] > https://github.com/apache/gora/blob/apache-gora-0.8/ > gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L262 > [5] > https://github.com/apache/gora/blob/apache-gora-0.8/ > gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L331 > > > 2018-06-06 4:38 GMT-01:00 carlos muñoz : > > > Hi all, > > > > Currently I am working on the Ignite backend, I am using my own fork [1]. > > This is what I have done so far: > > * Read mapping files. > > * Read configuration files (Ignite parameters). > > * Initialize Ignite DataStore through JDBC connection. > > * Implement some trivial methods (#close(), #flush(), > #getSchemaName()...). > > * Set up an embedded Ignite instance within test packages. > > > > The code is broken because I created a DataStoreTestBase implementation > for > > Ignite and due the fact that most DataStore methods are not implemented > yet > > the tests are failing. But the mapping/configuration reading and > connection > > initialization are working fine. > > > > I noticed that the mapping files (gora-XX-mapping.xml) have two fields > > 'boss' and 'webpage', which I assume are references to other objects > (other > > mapped classes). I was wondering how the backend should deal with them. > Is > > there some documentation regarding that?. > > > > Regards, > > Carlos > > > > > > [1] https://github.com/carlosrmng/gora/tree/GORA-535 > > >
[GSoC 2018] Ignite Backend - Status
Hi all, Currently I am working on the Ignite backend, I am using my own fork [1]. This is what I have done so far: * Read mapping files. * Read configuration files (Ignite parameters). * Initialize Ignite DataStore through JDBC connection. * Implement some trivial methods (#close(), #flush(), #getSchemaName()...). * Set up an embedded Ignite instance within test packages. The code is broken because I created a DataStoreTestBase implementation for Ignite and due the fact that most DataStore methods are not implemented yet the tests are failing. But the mapping/configuration reading and connection initialization are working fine. I noticed that the mapping files (gora-XX-mapping.xml) have two fields 'boss' and 'webpage', which I assume are references to other objects (other mapped classes). I was wondering how the backend should deal with them. Is there some documentation regarding that?. Regards, Carlos [1] https://github.com/carlosrmng/gora/tree/GORA-535
Getting Started with GSoC: Apache Ignite as data store
Hi, I am so happy that got into GSoC, thanks. I'd like to start. This week we're in the community bounding period. I am setting up my development environment (installing Apache Ignite). In addition, I am going to add a new backend [1]. Any thoughts? Also, I'd to request access to the WiKi, so I can update some of the work I will be doing. Finally, about the communication, I think it would be okay to keep it in the ML or private messages. Cheers, Carlos. [1] https://cwiki.apache.org/confluence/display/GORA/Writing+a+new+DataStore+for+Gora+HOW_TO
[GoSC 2018] GORA-535 Add a data store for Apache Ignite
Hi. I am Carlos Muñoz and I would like to participate in the GOSC2018 program with this project [1]. I have been getting started with Apache Gora and preparing my GoSC proposal. I would like to share it with you so you can given some comments on how I planned to tackle the issue. https://docs.google.com/document/d/1D2-XaOXVbLbEgMqGrnJGgDXQzv3YNeAYmNcwcUNvJZ4/edit?usp=sharing Thanks in advance for your help. Regards. Carlos [1] https://issues.apache.org/jira/browse/GORA-535
