[jira] [Resolved] (GORA-653) Upgrade Solr datastore to the latest java driver

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-653.
---
Fix Version/s: 1.0
   Resolution: Fixed

> Upgrade Solr datastore to the latest java driver
> 
>
> Key: GORA-653
> URL: https://issues.apache.org/jira/browse/GORA-653
> Project: Apache Gora
>  Issue Type: Improvement
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Gaby Ortiz accepted for Outreachy

[Madhawa Kasun Gunasekara]

  Hi Gaby,

Congratulations,  Looking forward for your contributions.

Thanks
Madhawa


On Tue, Dec 1, 2020 at 12:05 AM Alfonso Nishikawa <
alfonso.nishik...@gmail.com> wrote:

> Hi, Gaby,
>
> Congratulations!!! :)
>
> Best regars,
>
> Alfonso Nishikawa
>
> El lun, 30 nov 2020 a las 19:13, Furkan KAMACI ()
> escribió:
>
> > Hi,
> >
> > Congrats Gaby!
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Mon, Nov 30, 2020 at 9:08 PM carlos muñoz 
> wrote:
> >
> > > 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 (<
> arqgabyor...@gmail.com
> > >)
> > > 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 

Re: Maria Podorvanova accepted for Outreachy

[Madhawa Kasun Gunasekara]

Hi Maria,

Congratulations,  Looking forward to your contributions.

Thanks
Madhawa


On Tue, Dec 1, 2020 at 12:06 AM Alfonso Nishikawa <
alfonso.nishik...@gmail.com> wrote:

> Hi, María.
>
> Congratulations!!
>
> Best regards,
> Alfonso Nishikawa
>
> El lun, 30 nov 2020 a las 19:13, Furkan KAMACI ()
> escribió:
>
> > Hi,
> >
> > Congrats Maria!
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Mon, Nov 30, 2020 at 9:04 PM carlos muñoz 
> wrote:
> >
> > > 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 

[jira] [Commented] (GORA-562) Add a bin/gora command script for Windows

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara commented on GORA-562:
---

Hi [~alfonso.nishikawa], 

I will check the build failure.

> Add a bin/gora command script for Windows
> -
>
> Key: GORA-562
> URL: https://issues.apache.org/jira/browse/GORA-562
> Project: Apache Gora
>  Issue Type: Improvement
>Affects Versions: 0.9
>Reporter: Alfonso Nishikawa
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We would need a bin/gora.bat executable (or gora.cmd or alike) to compile 
> schemas under Windows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Github actions for Gora Github

[Madhawa Kasun Gunasekara]

Hi Lewis,

Yes, we can add those steps as well. I will add those as well.
I didn't do any documentation. I just created a Jira ticket only [1]

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

Thanks,
Madhawa


On Thu, Jul 30, 2020 at 8:55 PM Kevin Ratnasekera 
wrote:

> Hi Lewis,
>
> +1, Madhawa did the initial work on this. I am not sure whether we have
> documented anything on this.
>
> @Madhawa Kasun Gunasekara  Do you have anything to
> add here?
>
> Regards
> Kevin
>
> On Wed, Jul 29, 2020 at 12:14 PM lewis john mcgibbney 
> wrote:
>
>> Hi dev@,
>> I really like the use of Github Actions to test incoming PR's.
>> Who turned this on? Is this documented anywhere?I also think we could
>> execute a source code formatting check and maybe even findbugs or similar.
>> Any thoughts?
>> Thanks
>>
>> --
>> http://home.apache.org/~lewismc/
>> http://people.apache.org/keys/committer/lewismc
>>
>

[jira] [Resolved] (GORA-659) Upgrade Mongo DB driver to 3.12.4

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-659.
---
Fix Version/s: 1.0
   Resolution: Fixed

> Upgrade Mongo DB driver to 3.12.4
> -
>
> Key: GORA-659
> URL: https://issues.apache.org/jira/browse/GORA-659
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-659) Upgrade Mongo DB driver to 3.12.4

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-659:
-

Assignee: Madhawa Kasun Gunasekara

> Upgrade Mongo DB driver to 3.12.4
> -
>
> Key: GORA-659
> URL: https://issues.apache.org/jira/browse/GORA-659
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-661) Upgrade CouchDB module to the latest driver version

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-661.
---
Fix Version/s: 1.0
   Resolution: Fixed

> Upgrade CouchDB module to the latest driver version
> ---
>
> Key: GORA-661
> URL: https://issues.apache.org/jira/browse/GORA-661
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-couchdb
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-661) Upgrade CouchDB module to the latest driver version

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-661:
-

Assignee: Madhawa Kasun Gunasekara

> Upgrade CouchDB module to the latest driver version
> ---
>
> Key: GORA-661
> URL: https://issues.apache.org/jira/browse/GORA-661
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-couchdb
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>    Assignee: Madhawa Kasun Gunasekara
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-660) Upgrade Hive module to the latest driver version

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-660:
-

Assignee: Kevin Ratnasekera

> Upgrade Hive module to the latest driver version
> 
>
> Key: GORA-660
> URL: https://issues.apache.org/jira/browse/GORA-660
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hive
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>Assignee: Kevin Ratnasekera
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-660) Upgrade Hive module to the latest driver version

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-660:
-

Assignee: Madhawa Kasun Gunasekara  (was: Kevin Ratnasekera)

> Upgrade Hive module to the latest driver version
> 
>
> Key: GORA-660
> URL: https://issues.apache.org/jira/browse/GORA-660
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hive
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>    Assignee: Madhawa Kasun Gunasekara
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-660) Upgrade Hive module to the latest driver version

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-660.
---
Fix Version/s: 1.0
   Resolution: Fixed

> Upgrade Hive module to the latest driver version
> 
>
> Key: GORA-660
> URL: https://issues.apache.org/jira/browse/GORA-660
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hive
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>    Assignee: Madhawa Kasun Gunasekara
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GORA-658) Upgrade Cassandra driver to 3.9.0

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara updated GORA-658:
--
Fix Version/s: 1.0

> Upgrade Cassandra driver to 3.9.0
> -
>
> Key: GORA-658
> URL: https://issues.apache.org/jira/browse/GORA-658
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GORA-658) Upgrade Cassandra driver to 3.9.0

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara commented on GORA-658:
---

Merged pull request [https://github.com/apache/gora/pull/213]

Thanks for the contribution

> Upgrade Cassandra driver to 3.9.0
> -
>
> Key: GORA-658
> URL: https://issues.apache.org/jira/browse/GORA-658
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-658) Upgrade Cassandra driver to 3.9.0

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-658.
---
Resolution: Fixed

> Upgrade Cassandra driver to 3.9.0
> -
>
> Key: GORA-658
> URL: https://issues.apache.org/jira/browse/GORA-658
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-658) Upgrade Cassandra driver to 3.9.0

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-658:
-

Assignee: Madhawa Kasun Gunasekara

> Upgrade Cassandra driver to 3.9.0
> -
>
> Key: GORA-658
> URL: https://issues.apache.org/jira/browse/GORA-658
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Arne Nissen
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GORA-657) Implement ScyllaDB Datastore module

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara updated GORA-657:
--
Labels: gsoc2020  (was: )

> Implement ScyllaDB Datastore module
> ---
>
> Key: GORA-657
> URL: https://issues.apache.org/jira/browse/GORA-657
> Project: Apache Gora
>  Issue Type: New Feature
>    Reporter: Madhawa Kasun Gunasekara
>Priority: Major
>  Labels: gsoc2020
>
> [https://www.scylladb.com/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GORA-657) Implement ScyllaDB Datastore module

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara updated GORA-657:
--
Description: [https://www.scylladb.com/]

> Implement ScyllaDB Datastore module
> ---
>
> Key: GORA-657
> URL: https://issues.apache.org/jira/browse/GORA-657
> Project: Apache Gora
>  Issue Type: New Feature
>    Reporter: Madhawa Kasun Gunasekara
>Priority: Major
>
> [https://www.scylladb.com/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GORA-657) Implement ScyllaDB Datastore module

[Madhawa Kasun Gunasekara (Jira)]

Madhawa Kasun Gunasekara created GORA-657:
-

 Summary: Implement ScyllaDB Datastore module
 Key: GORA-657
 URL: https://issues.apache.org/jira/browse/GORA-657
 Project: Apache Gora
  Issue Type: New Feature
Reporter: Madhawa Kasun Gunasekara






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-654) Upgrade Lucene datastore to the latest java driver

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-654.
---
Fix Version/s: 1.0
   Resolution: Fixed

> Upgrade Lucene datastore to the latest java driver
> --
>
> Key: GORA-654
> URL: https://issues.apache.org/jira/browse/GORA-654
> Project: Apache Gora
>  Issue Type: Improvement
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GORA-654) Upgrade Lucene datastore to the latest java driver

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara commented on GORA-654:
---

Thanks Rumesh Perera for the pull request

> Upgrade Lucene datastore to the latest java driver
> --
>
> Key: GORA-654
> URL: https://issues.apache.org/jira/browse/GORA-654
> Project: Apache Gora
>  Issue Type: Improvement
>Reporter: Kevin Ratnasekera
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-643) Move to Apache parent POM version 22

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-643.
---
Resolution: Fixed

Thank you Dinuka Perera for the pull request

> Move to Apache parent POM version 22
> 
>
> Key: GORA-643
> URL: https://issues.apache.org/jira/browse/GORA-643
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.9
>Reporter: Kevin Ratnasekera
>Assignee: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Apache parent POM version 22 was released on 2020/01/09.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GORA-645) Upgrade MongoDB Driver version to 3.12.x

[Madhawa Kasun Gunasekara (Jira)]

Madhawa Kasun Gunasekara created GORA-645:
-

 Summary: Upgrade MongoDB Driver version to 3.12.x
 Key: GORA-645
 URL: https://issues.apache.org/jira/browse/GORA-645
 Project: Apache Gora
  Issue Type: Task
Reporter: Madhawa Kasun Gunasekara






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GORA-644) Add Github Workflows for PR

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara resolved GORA-644.
---
Resolution: Fixed

> Add Github Workflows for PR
> ---
>
> Key: GORA-644
> URL: https://issues.apache.org/jira/browse/GORA-644
> Project: Apache Gora
>  Issue Type: Improvement
>    Reporter: Madhawa Kasun Gunasekara
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It would be nice to have at least the source check running for each PR 
> possibly as a GitHub action



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GORA-644) Add Github Workflows for PR

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara updated GORA-644:
--
Fix Version/s: 1.0

> Add Github Workflows for PR
> ---
>
> Key: GORA-644
> URL: https://issues.apache.org/jira/browse/GORA-644
> Project: Apache Gora
>  Issue Type: Improvement
>    Reporter: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It would be nice to have at least the source check running for each PR 
> possibly as a GitHub action



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GORA-644) Add Github Workflows for PR

[Madhawa Kasun Gunasekara (Jira)]

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

Madhawa Kasun Gunasekara reassigned GORA-644:
-

Assignee: Madhawa Kasun Gunasekara

> Add Github Workflows for PR
> ---
>
> Key: GORA-644
> URL: https://issues.apache.org/jira/browse/GORA-644
> Project: Apache Gora
>  Issue Type: Improvement
>    Reporter: Madhawa Kasun Gunasekara
>        Assignee: Madhawa Kasun Gunasekara
>Priority: Minor
> Fix For: 1.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It would be nice to have at least the source check running for each PR 
> possibly as a GitHub action



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Enabling Git workflow for Apache Gora

[Madhawa Kasun Gunasekara]

Hi All,

At the moment, when there is a new PR, we always have to build locally to
make sure the new PR doesn't introduce any regression issues. However, with
Github Actions, we can automate this effort with zero cost. I have written
a Github workflow to automatically build new PRs to check its validity.

[1]  https://github.com/apache/gora/pull/201

Thanks,
Madhawa

[jira] [Created] (GORA-644) Add Github Workflows for PR

[Madhawa Kasun Gunasekara (Jira)]

Madhawa Kasun Gunasekara created GORA-644:
-

 Summary: Add Github Workflows for PR
 Key: GORA-644
 URL: https://issues.apache.org/jira/browse/GORA-644
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Madhawa Kasun Gunasekara


It would be nice to have at least the source check running for each PR possibly 
as a GitHub action



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [WELCOME] Sheriffo Ceesay to Gora PMC and Committership

[Madhawa Kasun Gunasekara]

Hi Sheriffo,

Congratulations and Welcome on board.

Thanks,
Madhawa


On Sat, Sep 28, 2019 at 5:29 AM Kevin Ratnasekera 
wrote:

> Hi Sheriffo,
>
> Welcome on board. I’m looking forward to working with you  :)
>
> Regards
> Kevin
>
> On Sat, Sep 28, 2019 at 3:24 AM Sheriffo Ceesay 
> wrote:
>
> > Hi,
> >
> > Thank you all for the very warm welcome. I am very much delighted and
> > humbled to be part of this great team.
> >
> > @Lewis John Mcgibbney  , thanks for the
> > pointers, once the account creation process is completed, I will go ahead
> > and complete the rest of the process.
> >
> > Thank you.
> > Kind regards
> >
> >
> > **Sheriffo Ceesay**
> >
> >
> > On Fri, Sep 27, 2019 at 5:46 PM Furkan KAMACI 
> > wrote:
> >
> > > Hi,
> > >
> > > Welcom Sheriffo!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > 26 Eyl 2019 Per, saat 23:19 tarihinde Cihad Guzel 
> > > şunu yazdı:
> > >
> > >> Hi Sheriffo,
> > >>
> > >> Welcome on board. Great to have you here!
> > >>
> > >> Cihad Guzel
> > >>
> > >>
> > >> lewis john mcgibbney , 26 Eyl 2019 Per, 22:40
> > >> tarihinde
> > >> şunu yazdı:
> > >>
> > >> > Hi dev@,
> > >> > I'm very happy to welcome Sheriffo Ceesay to our ranks. Sheriffo was
> > >> one of
> > >> > our GSoC students this year with his work resulting in a
> benchmarking
> > >> > module based on Yahoo!'s Cloud Serving Benchmark [0].
> > >> > Sheriffo is finishing off his Ph.D. at the University of St.
> Andrews,
> > >> in my
> > >> > mother country of Scotland and has mentioned that he will be pretty
> > >> quiet
> > >> > until that is done. I personally with you the very best with that.
> > >> > Sheriffo, once your account is created it is customary to commit
> your
> > >> > details to the Gora parent pom.xml [1]. If you need some assistance
> > with
> > >> > that then please let me know.
> > >> > Lewis
> > >> >
> > >> > [0] https://github.com/apache/gora/tree/master/gora-benchmark
> > >> > [1] https://github.com/apache/gora/blob/master/pom.xml#L53
> > >> >
> > >> > --
> > >> > http://home.apache.org/~lewismc/
> > >> > http://people.apache.org/keys/committer/lewismc
> > >> >
> > >>
> > >
> >
>

Re: [VOTE] RC03 for Apache Gora 0.9 Release

[Madhawa Kasun Gunasekara]

+1 to release.

Thanks,
Madhawa


On Wed, Aug 14, 2019 at 8:32 AM Nishadi Kirielle  wrote:

> +1 to Release this package as Apache Gora 0.9.
>
> Best Regards,
> Nishadi
>
> On Wed, Aug 14, 2019 at 1:01 PM Nishadi Kirielle 
> wrote:
>
> > +1 Release this package as Apache Gora 0.9
> >
> > On Wed, Aug 14, 2019 at 3:01 AM Kevin Ratnasekera <
> djkevincr1...@gmail.com>
> > wrote:
> >
> >> Hi all,
> >>
> >> This is the vote on third release candidate (RC03) 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 …
> >>
> >> 48 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-RC03/
> >>
> >> Staging repository is available here :
> >>
> >> https://repository.apache.org/content/repositories/orgapachegora-1018
> >>
> >> 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=cdf7704dca90f531ec932ca08799579eaf80b0df
> >>
> >> and is based on the following commit id:
> >>
> >> bd4b34ae74725d57b31ab5e83da3ea77f6213643
> >>
> >> Thank you to everyone 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: 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

[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: GSoC 2019 - Redis DB

[Madhawa Kasun Gunasekara]

Hi Xavier,

Please upload your proposal to the Apache Gora confluence space [1]. In the
GSoC period, we expect reporting also, You can create a Page in the Reports
space [2], and add your weekly reports. In is the way everyone can have a
visibility of your work.

In this community bonding period, we expect you to fix some JIRA issues in
Apache Gora project [3].  Looking forward for your contributions  in Apache
Gora. :)

[1] https://cwiki.apache.org/confluence/display/GORA/GSoC+2019+Proposals
[2] https://cwiki.apache.org/confluence/display/GORA/GSoC+2019+Reports
[3] https://issues.apache.org/jira/issues/
<https://issues.apache.org/jira/issues/?filter=-1=project%20%3D%20GORA%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Open%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20in%20(currentUser())%20order%20by%20updated%20DESC>

Thanks,
Madhawa


On Sat, May 18, 2019 at 6:32 PM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> Congratulations Xavier,
> Looking forward for your contributions in Apache Gora.
>
>  Thanks,
> Madhawa
>
>
> On Sun, May 12, 2019 at 5:52 AM FRANCISCO XAVIER SUMBA TORAL
>  wrote:
>
>> Hello,
>>
>> I am really happy that I have been accepted in GSoC. I will work
>> implementing Redis DB as a new datastore. I wanted to say thanks to all
>> those mentors that provide me some feedback and I want to make the most of
>> this Summer working in that issue.
>>
>>
>> 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: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

[Madhawa Kasun Gunasekara]

Hi Lahiru,

Congratulations and Welcome, Looking forward to your future contributions
for Apache
Gora project.

Regards
Madhawa


On Tue, May 7, 2019 at 8:32 AM Lahiru Jayasekera 
wrote:

> Hi all,
> I have received the acceptance letter for GSOC 2019 for the project
> "Hazelcast Jet execution engine support for Apache Gora". I am really
> delightful of this huge opportunity. Thank you very much for accepting my
> proposal. I hope to give my full capacity to finish this project. Please
> let me know of any other things that I need to do to start my GSOC journey.
>
> Thanks and Regards
> Lahiru
>
> -- Forwarded message -
> From: Google Summer of Code 
> Date: Tue, May 7, 2019 at 2:21 AM
> Subject: GSoC 2019: Congratulations, your proposal with The Apache
> Software Foundation has been accepted!
> To: 
>
>
> [image: Google Summer of Code]
>
> Hi Lahiru Jayasekara,
>
> Your proposal Hazelcast Jet execution engine support for Apache Gora
> 
> has been accepted!
>
> Welcome to GSoC 2019!
>
> We look forward to seeing the great things you will accomplish this summer
> with The Apache Software Foundation.
>
> The next thing you need to do is read the Information for Accepted
> Students
> .
> It contains important information you need to know about your participation
> in GSoC 2019.
>
> You will receive another email in the next few days with information about
> your stipend.
>
> If you have any questions, please email the Google Summer of Code support
> team at gsoc-supp...@google.com.
>
> Have a great summer!
>
> -*Google Summer of Code team*
>
> This email was sent to mlpjayasek...@gmail.com.
>
> You are receiving this email because of your participation in Google
> Summer of Code 2019.
> https://summerofcode.withgoogle.com
>
> To leave the program and stop receiving all emails, you can go to your
> profile  and
> request deletion of your program profile.
>
> For any questions, please contact gsoc-supp...@google.com. Replies to
> this message go to an unmonitored mailbox.
>
> © 2019 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
>
>
> --
> Lahiru Jayasekara
> Batch 15
> Faculty of Information Technology
> University of Moratuwa
> 0716492170
>

Re: [VOTE] RC01 for Apache Gora 0.9 Release

[Madhawa Kasun Gunasekara]

 +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: POC for hazelcast jet integration

[Madhawa Kasun Gunasekara]

Hi Lahiru,

Good initiative.
It seems like we need to use hadoop-hdfs and hadoop common with version
2.8.3. Try adding these dependencies, and exclude the old dependency from
the gora, or otherwise, we can do a version upgrade in gora for Hadoop. at
the moment we use Hadoop version 2.5.2 in gora but I prefer to upgrade the
Hadoop versions in the gora to 2.8.3.

Recently hazelcast developers released 3.0 version, We can try that also.

Thanks,
Madhawa


On Sat, Apr 6, 2019 at 9:53 PM Lahiru Jayasekera 
wrote:

> Hi all,
> I have come up with a poc for hazelcast jet execution engine support for
> gora.
>
> https://github.com/LahiruJayasekara/gora/blob/poc-hazelcast-jet/gora-tutorial/src/main/java/org/apache/gora/tutorial/log/HazelcastJetPOC.java
>
> Here I have wrote a custom source for jet. What this does is read the
> AccessLog table created via LogManager example, and feed the PageView
> objects to jet.
>
> I have also looked into using hdfs connectors of jet. But I encountered a
> problem with conflicting hadoop versions. InputFormat class used in gora is
> from pacjage 'org.apache.hadoop.mapreduce', but in jet it is '
> org.apache.hadoop.mapred.InputFormat'.
>
> Anyway the proposed poc works as expected. Please add your suggestions
> here.
>
> Thanks and regards
>
> --
> Lahiru Jayasekara
> Batch 15
> Faculty of Information Technology
> University of Moratuwa
> 0716492170
>

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: Student proposal for GSOC 2019

[Madhawa Kasun Gunasekara]

Hi Lahiru,

Overall, the proposal looks good, you can address the points mentioned by
Kevin. Try to make your proposal very attractive way. Add more technical
stuff.

Thanks,
Madhawa


On Mon, Apr 8, 2019 at 4:58 PM Lahiru Jayasekera 
wrote:

> Hi Kevin,
> Thanks for the feedback. I'll work on the POC further.
>
> Thanks
>
> On Mon, Apr 8, 2019 at 1:12 PM Kevin Ratnasekera 
> wrote:
>
> > Hi Lahiru,
> >
> > There is nothing to apologize for. What I mentioned was, even though you
> > addressed Carlos in the email, he was not CC ed to the email sent to me.
> I
> > know that you have mistakenly sent that email CC ing only me.
> > Regarding the POC, I don't see you you have created the Input Format or
> > Connection Interface that is needed for Jet jobs. On the other hand, also
> > you have created on top tutorial module. These are just my feedback, have
> > feedback on other people in the dev list. And try to improve your
> proposal.
> > My feedback is just one factor. You know how opensource work since you
> > worked for WSO2.
> >
> > Regards
> > Kevin
> >
> > On Mon, Apr 8, 2019 at 12:57 PM Lahiru Jayasekera <
> mlpjayasek...@gmail.com>
> > wrote:
> >
> >> Hi Kevin,
> >> I have added those to proposal.
> >> Sorry I have directly emailed you. I will respond to mailing list.
> >>
> >> Thanks
> >>
> >> On Mon, Apr 8, 2019 at 11:53 AM Kevin Ratnasekera <
> >> djkevincr1...@gmail.com> wrote:
> >>
> >>> Hi Lahiru,
> >>>
> >>> Please add all the contributions, POC etc to Proposal. I ll have a
> look.
> >>> Also please respond to mailing list, above email is directly sent to
> me. (
> >>> Carlos is not copied ) Good luck with your proposal.
> >>>
> >>> Regards
> >>> Kevin
> >>>
> >>> On Mon, Apr 8, 2019 at 11:26 AM Lahiru Jayasekera <
> >>> mlpjayasek...@gmail.com> wrote:
> >>>
>  Hi Kevin and Carlos,
>  I have addressed the comments in draft proposal. Appreciate if you can
>  please have a look before I submit it to GSOC.
> 
>  Thanks
> 
>  On Mon, Apr 8, 2019 at 11:11 AM Lahiru Jayasekera <
>  mlpjayasek...@gmail.com> wrote:
> 
> > Hi all,
> > I have created a POC for the project and I have sent a mail to the
> > mailing list too. Your kind feedback is appreciated.
> >
> > On Wed, Apr 3, 2019 at 3:58 PM Kevin Ratnasekera <
> > djkevincr1...@gmail.com> wrote:
> >
> >> Hi Lahiru,
> >>
> >> Sure, thanks for the update.
> >>
> >> Regards
> >> Kevin
> >>
> >> On Wed, Apr 3, 2019 at 7:03 AM Lahiru Jayasekera <
> >> mlpjayasek...@gmail.com> wrote:
> >>
> >>> Hi Kevin,
> >>> Working on them. Thanks for the feedback.
> >>>
> >>> Thanks
> >>>
> >>> On Tue, Apr 2, 2019 at 2:24 PM Kevin Ratnasekera <
> >>> djkevincr1...@gmail.com> wrote:
> >>>
>  Hi Lahiru,
> 
>  Overall proposal looks good :) I have added some comments where
> you
>  can improve.
> 
>  Regards
>  Kevin
> 
>  On Tue, Apr 2, 2019 at 9:53 AM Lahiru Jayasekera <
>  mlpjayasek...@gmail.com> wrote:
> 
> > Thanks Carlos
> >
> > On Tue, Apr 2, 2019 at 9:26 AM carlos muñoz <
> carlosr...@gmail.com>
> > wrote:
> >
> > > 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 <
> carlosr...@gmail.com
> > wrote:
> > > >
> > > > > 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.
> > > > > >
> > 

Re: [VOTE] Move Canonical Gora Source Code to gitbox.apache.org

[Madhawa Kasun Gunasekara]

+1
Madhawa


On Sun, Dec 9, 2018 at 9:48 PM Cihad Guzel  wrote:

> +1
>
> 9 Ara 2018 Paz 00:59 tarihinde Furkan KAMACI  şunu
> yazdı:
>
> > +1
> >
> > On Sat, Dec 8, 2018 at 11:43 PM Kevin Ratnasekera <
> djkevincr1...@gmail.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > On Sat, Dec 8, 2018 at 3:38 PM lewis john mcgibbney <
> lewi...@apache.org>
> > > wrote:
> > >
> > > > dev@,
> > > > As per Daniel Gruno's NOTICE [0], all https://git-wip-us.apache.org
> > > > repositories will be moved to the new gitbox service which includes
> > > direct
> > > > write access on github as well as the standard ASF commit access via
> > > > gitbox.apache.org.
> > > > We can do this voluntarily or we can be forced to do it (which
> > basically
> > > > means we are being forced to do it but the former option at least
> > enables
> > > > us to have some input into how it is done.)
> > > > This thread is a VOTE for us to move the canonical Gora source code
> > over
> > > to
> > > > gitbox.apache.org. There will be no severe impact to our users or
> dev@
> > > > community. I anticipate the only impact to be the requirement to
> change
> > > the
> > > > remote canonical origin mapping in your Git client. Everything else
> > > should
> > > > be fine.
> > > > Some benefits include the ability for us to use the normal Github
> > > workflow
> > > > for merging, etc. so infact it will probably streamline some aspects
> of
> > > our
> > > > development workflow.
> > > > Please VOTE as follows
> > > >
> > > > [ ] +1 Move the canonical Gora source code from
> > > > https://git-wip-us.apache.org to gitbox.apache.org.
> > > > [ ] +1 DO NOT move the canonical Gora source code from
> > > > https://git-wip-us.apache.org to gitbox.apache.org (please provide
> > > > justification)
> > > >
> > > > This VOTE will be open a minimum of 72 hours.
> > > > Here is my +1
> > > > Lewis
> > > >
> > > >
> > > > [0] https://s.apache.org/aGMR
> > > > --
> > > > http://home.apache.org/~lewismc/
> > > > http://people.apache.org/keys/committer/lewismc
> > > >
> > > >
> > > > --
> > > > http://home.apache.org/~lewismc/
> > > > http://people.apache.org/keys/committer/lewismc
> > > >
> > >
> >
>

Re: GSoC 2018: You are a mentor for Talat UYARER

[Madhawa Kasun Gunasekara]

Congratulations Talat :)

Madhawa

On Thu, Apr 26, 2018 at 11:53 PM, Kevin Ratnasekera  wrote:

> Congratulations Talat :)
>
> -- Forwarded message --
> From: Google Summer of Code 
> Date: Mon, Apr 23, 2018 at 9:57 PM
> Subject: GSoC 2018: You are a mentor for Talat UYARER
> To: djkevincr1...@gmail.com
>
>
> [image: Google Summer of Code]
>
> Congratulations, you will be spending the next few months working with
> Talat UYARER on Redis Implementation For Gora
>  organization/5718432427802624/proposal/6289501358391296/>
> .
>
> Please welcome
>  your
> student into your community and work with them to plan the milestones they
> will need to meet. Setting clear expectations early is one of the best ways
> to help your student succeed.
>
> You can read the Mentor Manual
>  for some
> great tips on how to communicate with your student and make a project plan.
>
> If you have any questions please contact our Google Open Source Programs
> team at gsoc-supp...@google.com or email the mentors mailing list if
> appropriate.
>
> -Google Open Source Programs team
>
> This email was sent to djkevincr1...@gmail.com.
>
> You are receiving this email because of your participation in Google Summer
> of Code 2018.
> https://summerofcode.withgoogle.com
>
> To leave the program and stop receiving all emails, you can go to your
> profile  and
> request deletion of your program profile.
>
> For any questions, please contact gsoc-supp...@google.com. Replies to this
> message go to an unmonitored mailbox.
>
> © 2018 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
>  Mountain+View,+CA+94043,+USA=gmail=g>
>

Re: GoraExplorer

[Madhawa Kasun Gunasekara]

Awesome Job Alfonso !!!

Regards,
Madhawa

Madhawa

On Sat, Feb 3, 2018 at 12:37 AM, lewis john mcgibbney 
wrote:

> This is absolutely dynamite Alfonso. Really really cool.
> If I were you, I would consider further development of this through GSoC. I
> would be happy to co-mentor such an effort.
> This is so refreshing.
> Lewis
>
> On Thu, Feb 1, 2018 at 9:18 PM,  wrote:
>
> >
> > From: Alfonso Nishikawa 
> > To: "" 
> > Cc:
> > Bcc:
> > Date: Tue, 30 Jan 2018 23:02:19 -0100
> > Subject: GoraExplorer
> > Hi!
> >
> > GoraExplorer is a NoSQL databases manager through Apache Gora.
> >
> > At this moment only works with HBase, sorry :S
> > I will try to create a video explaining it in a few days, but I leave it
> to
> > you deployed at [1] if anyone wants to take a look and comment. It is in
> an
> > alpha stage, so expect several things to break :P
> > Actually, you can only access tables (forget "Admin" menu).
> >
> > There are two tables defined (one for Nutch, one for Twitter) with some
> > example data. If anyone breaks too much de data write me and I will
> restore
> > it :)
> >
> > user:pass = admin:admin
> >
> > There is no usage explanation in this email, so maybe I will find out if
> > the application is VERY unintuitive, or "only" unintuitive xD
> >
> > You may ask for changes :) I will try to implement them if I can, but I
> > don't promise much :S
> >
> > I hope you like it :S
> >
> > [1] -
> > http://ec2-52-26-56-192.us-west-2.compute.amazonaws.com:
> 8080/goraexplorer/
> >
> >
>

Re: [REQUIRED] Testers for Nutch 2.X and Gora 0.8 integrations

[Madhawa Kasun Gunasekara]

Hi Lewis,

I would like to test Apache Cassandra and Solr.

Thanks,
Madhawa

Madhawa

On Thu, Oct 5, 2017 at 6:39 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> We are currently working on upgrading Nutch 2.X to use Gora 0.8,
> specifically the new backends.
> As a reminder, Gora 0.8 ships with the following modules
>
> DBTest Result
> Apache Avro 1.8.1
> Apache Hadoop 2.5.2
> Apache HBase 1.2.3
> Apache Cassandra 3.11.0 (Datastax Java Driver 3.3.0)
> Apache Solr 6.5.1
> MongoDB 3.4.9 OK
> Apache Accumlo 1.7.1
> Apache Spark 1.4.1
> Apache CouchDB 1.4.2 (test containers 1.1.0)
> Amazon DynamoDB (driver) 1.10.55
> Infinispan 7.2.5.Final
> JCache 1.0.0 with Hazelcast 3.6.4 support.
> OrientDB 2.2.22
> Aerospike 4.0.6
>
> We are essentially looking for testers for as many/all of the above as
> possible. If you can help and are able to post your results, then please
> send them to https://github.com/apache/nutch/pull/229
> Thanks
> Lewis
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Re: [VOTE] Apache Gora 0.8 RC#1

[Madhawa Kasun Gunasekara]

++1


Madhawa

On Sat, Sep 16, 2017 at 8:30 AM, Furkan KAMACI 
wrote:

> +1
>
> On Sat, Sep 16, 2017 at 1:50 PM, Alfonso Nishikawa <
> alfonso.nishik...@gmail.com> wrote:
>
>> +1
>>
>> 2017-09-15 9:40 GMT-01:00 lewis john mcgibbney :
>>
>>> Hi Folks,
>>> I would like to open a VOTE on releasing Gora 0.8 RC#1. Thank you to
>>> everyone that was able to contribute to this development drive.
>>>
>>> We solved 35 issues:
>>>  https://s.apache.org/phXx
>>>
>>> SVN source tag (r999):
>>> https://svn.apache.org/repos/asf/any23/tags/X.Y/
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/orgapachegora-1005
>>>
>>> PGP release keys (signed using 48BAEBF6):
>>> https://dist.apache.org/repos/dist/dev/gora/KEYS
>>>
>>> Vote will be open for 72 hours.
>>>
>>> [ ] +1, let's get it rmblee!!!
>>> [ ] +/-0, fine, but consider to fix few issues before...
>>> [ ] -1, nope, because... (and please explain why)
>>>
>>> P.S. Here is my +1
>>>
>>> --
>>> http://home.apache.org/~lewismc/
>>> @hectorMcSpector
>>> http://www.linkedin.com/in/lmcgibbney
>>>
>>
>>
>

Re: GORA-497 Migrate Cassandra Thrift to CQL - Final Evaluation

[Madhawa Kasun Gunasekara]

Thanks for the feedbacks

Regards,
Madhawa

Madhawa

On Sun, Aug 27, 2017 at 11:56 PM, Renato Marroquín Mogrovejo <
renatoj.marroq...@gmail.com> wrote:

> Great job Madhawa! Looking forward for more cool contributions in the
> future :)
>
>
> Best,
>
> Renato M.
>
> 2017-08-26 14:18 GMT-07:00 Furkan KAMACI <furkankam...@gmail.com>:
>
>> Great!
>>
>>
>> 26 Ağu 2017 Cmt, saat 21:26 tarihinde Alfonso Nishikawa <
>> alfonso.nishik...@gmail.com> şunu yazdı:
>>
>>> Great! Good job!
>>>
>>> Regards,
>>> Alfonso Nishikawa
>>>
>>> El 26 ago. 2017 2:09 p. m., "Madhawa Kasun Gunasekara" <
>>> madhaw...@gmail.com>
>>> escribió:
>>>
>>> > Hi All,
>>> >
>>> > This week is the last week of GSoC project period. So In the End, I was
>>> > able to complete the Cassandra module, I have completely rewritten the
>>> > module to support Cassandra CQL. and I have supported native
>>> serialization
>>> > and Avro serialization both in Cassandra data store. I have added test
>>> > cases for both serializations. and attach a patch for the
>>> documentation on
>>> > web site as well. In the community bonding period, I have fixed some
>>> bugs
>>> > in Solr data store and I have upgraded the Solr library as well.
>>> >
>>> > During this GSoC period, I was able to fix following issues.
>>> > 1. https://issues.apache.org/jira/browse/GORA-299
>>> > 2. https://issues.apache.org/jira/browse/GORA-308
>>> > 3. https://issues.apache.org/jira/browse/GORA-310
>>> > 4. https://issues.apache.org/jira/browse/GORA-311
>>> > 5. https://issues.apache.org/jira/browse/GORA-497
>>> > 6. https://issues.apache.org/jira/browse/GORA-498
>>> > <https://issues.apache.org/jira/browse/GORA-497>
>>> > 7. https://issues.apache.org/jira/browse/GORA-509
>>> >
>>> >
>>> > During this GSoC period, I was able to improve my technological
>>> knowledge
>>> > and learned so many new things. I would like to thank my mentors Lewis
>>> and
>>> > Kevin, for providing wonderful guidance to make this project
>>> successful.
>>> > and also like to thank Renato, Alfonso and the gora community for
>>> providing
>>> > the support.
>>> >
>>> > It's my pleasure to contribute to the Apache gora project and I'm
>>> looking
>>> > forward to contribute to the gora project.
>>> >
>>> > This is my first GSoC experience and Thanks everyone for making it a
>>> > memorable one.
>>> >
>>> > Thanks,
>>> > Madhawa
>>> >
>>>
>>
>

GORA-497 Migrate Cassandra Thrift to CQL - Final Evaluation

[Madhawa Kasun Gunasekara]

Hi All,

This week is the last week of GSoC project period. So In the End, I was
able to complete the Cassandra module, I have completely rewritten the
module to support Cassandra CQL. and I have supported native serialization
and Avro serialization both in Cassandra data store. I have added test
cases for both serializations. and attach a patch for the documentation on
web site as well. In the community bonding period, I have fixed some bugs
in Solr data store and I have upgraded the Solr library as well.

During this GSoC period, I was able to fix following issues.
1. https://issues.apache.org/jira/browse/GORA-299
2. https://issues.apache.org/jira/browse/GORA-308
3. https://issues.apache.org/jira/browse/GORA-310
4. https://issues.apache.org/jira/browse/GORA-311
5. https://issues.apache.org/jira/browse/GORA-497
6. https://issues.apache.org/jira/browse/GORA-498

7. https://issues.apache.org/jira/browse/GORA-509


During this GSoC period, I was able to improve my technological knowledge
and learned so many new things. I would like to thank my mentors Lewis and
Kevin, for providing wonderful guidance to make this project successful.
and also like to thank Renato, Alfonso and the gora community for providing
the support.

It's my pleasure to contribute to the Apache gora project and I'm looking
forward to contribute to the gora project.

This is my first GSoC experience and Thanks everyone for making it a
memorable one.

Thanks,
Madhawa

Re: gora-solr-5 still remains

[Madhawa Kasun Gunasekara]

Hi Lewis,

No, This class has been missed from my previous solr6 upgrade pull request.
So I have sent a pull request to remove this class [1]

[1] https://github.com/apache/gora/pull/108

Thanks,
Madhawa

Madhawa

On Wed, Jun 7, 2017 at 8:38 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I just noticed that gora-solr-5 module still remains in SCM.
> https://github.com/apache/gora/tree/master/gora-solr-5/
> src/test/java/org/apache/gora/solr/store
> I assume this is not intentional?
> lewis
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Upgrading solr version in solr module

[Madhawa Kasun Gunasekara]

Hi Devs,

I'm Madhawa Gunasekara from Sri Lanka. First of all, I would like to thanks
to the Gora community to accepting my project proposal for "Rewriting Gora
Cassandra module to support CQL" project in Google Summer of Code 2017. I'm
looking forward to have a good project experience by working with Apache
Gora

At the moment I'm working on this JIRA issue [1]. therefore I'm upgrading
solr version in gora-solr module. Since there are two solr modules in the
gora project, shall I create a another solr module to support solr 6
version? or shall we refactor to make one solr module?

Let me know what is the suitable way to do this. BTW I'm I'm +1 to create
one solr module.

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

Thanks,
Madhawa

Re: GSoC 2017: You are a mentor for Madhawa Gunasekara

[Madhawa Kasun Gunasekara]

Thanks Kevin. Looking forward to doing more contributions to gora project.

Regards,
Madhawa

Madhawa

On Thu, May 4, 2017 at 10:15 PM, Kevin Ratnasekera 
wrote:

> Congratulations Madhawa :)
>
> -- Forwarded message --
> From: Google Summer of Code 
> Date: Thu, May 4, 2017 at 9:33 PM
> Subject: GSoC 2017: You are a mentor for Madhawa Gunasekara
> To: djkevincr1...@gmail.com
>
>
> [image: Google Summer of Code]
>
> Congratulations, you will be spending the next few months working with
> Madhawa Gunasekara on Rewrite Cassandra Module in Apache Gora to support
> CQL
> 
> .
>
> Please welcome
>  your
> student into your community and work with them to plan the milestones they
> will need to meet. Setting clear expectations early is one of the best ways
> to help your student succeed.
>
> You can read the Mentor Manual
>  for
> some great tips on how to communicate with your student and make a project
> plan.
>
> If you have any questions please contact our Google Open Source Programs
> team at gsoc-supp...@google.com or email the mentors mailing list if
> appropriate.
>
> -Google Open Source Programs team
>
> This email was sent to djkevincr1...@gmail.com.
>
> You are receiving this email because of your participation in Google
> Summer of Code 2017.
> https://summerofcode.withgoogle.com
>
> To leave the program and stop receiving all emails, you can go to your
> profile  and
> request deletion of your program profile.
>
> For any questions, please contact gsoc-supp...@google.com. Replies to
> this message go to an unmonitored mailbox.
>
> © 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043,
> USA
>
>

Re: [VOTE] Release Apache Gora 0.7

[Madhawa Kasun Gunasekara]

+1

Madhawa

On Sat, Mar 18, 2017 at 12:39 AM, Pierre Sutra <0tr...@gmail.com> wrote:

> +1
>
> Pierre
>
>
>
> On 17/03/2017 07:27, lewis john mcgibbney wrote:
>
>> Hi Folks,
>>
>> I am very happy to get a VOTE out for Apache Gora 0.7 Release Candidate
>> #1.
>>
>> We solved 80 issues: https://s.apache.org/YrmC
>>
>> Git source tag (3b48688f51d6cf618c760b24a341874f12e160d2):
>> https://s.apache.org/Vkhi
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachegora-1004
>>
>> Source Release Artifacts: https://dist.apache.org/repos/dist/dev/gora/0.7
>>
>> PGP release keys (signed using 48BAEBF6):
>> http://www.apache.org/dist/gora/KEYS
>>
>> Vote will be open for at least 72 hours.
>> Thank you to everyone that is able to VOTE as well as everyone that
>> contributed to Apache Gora 0.7.
>>
>> [ ] +1, let's get it released!!!
>> [ ] +/-0, fine, but consider to fix few issues before...
>> [ ] -1, nope, because... (and please explain why)
>>
>> p.s. Here's my +1
>>
>>
>

Re: [Cassandra Store] Need to migrate to CQL Interface

[Madhawa Kasun Gunasekara]

Hi Renato,

Sure, I would like to work on this. Thanks for the initial skeleton work.

Thanks,
Madhawa

Madhawa

On Wed, Feb 8, 2017 at 1:49 AM, Renato Marroquín Mogrovejo <
renatoj.marroq...@gmail.com> wrote:

> Hey guys,
>
> Sorry for the late reply, but I am writing on the jira page so we can keep
> track of this over there.
> But if you can take this on Madhawa, it'd be great! :)
>
>
> Best,
>
> Renato M.
>
> 2017-01-30 19:07 GMT+01:00 lewis john mcgibbney <lewi...@apache.org>:
>
>> Once we fix https://issues.apache.org/jira/browse/GORA-443
>>
>>
>> On Sat, Jan 28, 2017 at 9:04 PM, Madhawa Kasun Gunasekara <
>> madhaw...@gmail.com> wrote:
>>
>>> Hi Lewis,
>>>
>>> When is the next release? I can work on this task.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> Madhawa
>>>
>>> On Fri, Jan 27, 2017 at 11:54 PM, lewis john mcgibbney <
>>> lewi...@apache.org> wrote:
>>>
>>>> Hi Folks,
>>>> Yes the entire gora-cassandra module needs an overhaul. It is horribly
>>>> dated now and quite frankly shoudl most likely be disabled in our next
>>>> release.
>>>> Lewis
>>>>
>>>> On Sun, Dec 11, 2016 at 12:39 AM, Madhawa Kasun Gunasekara <
>>>> madhaw...@gmail.com> wrote:
>>>>
>>>> > Hi Alfonso,
>>>> >
>>>> > Hector has been no longer used in Cassandra community. Community has
>>>> been
>>>> > migrated to CQL (Cassandra Query Language), which is very much
>>>> similar to
>>>> > SQL. and also currently Gora-Cassandra component is not compatible
>>>> with
>>>> > Cassandra database servers which use CQL 3,4 versions.
>>>> >
>>>> > CQL performance is much better than thrift (Hector) [1]. I created
>>>> jira
>>>> > issue for this task [2] as well.
>>>> >
>>>> > [1] http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-faster
>>>> > [2] https://issues.apache.org/jira/browse/GORA-497
>>>> >
>>>> > Thanks,
>>>> > Madhawa
>>>> >
>>>> > Madhawa
>>>> >
>>>> > On Sat, Dec 10, 2016 at 9:55 PM, Alfonso Nishikawa <
>>>> > alfonso.nishik...@gmail.com> wrote:
>>>> >
>>>> >> Hi, Madhawa.
>>>> >>
>>>> >> I don't know much about Cassandra :( but I think I read time ago
>>>> about
>>>> >> some comment about the benefits of being capable of swapping the
>>>> library.
>>>> >> Would be very handy to what you tell.
>>>> >>
>>>> >> Renato, was there an issue about that?
>>>> >>
>>>> >> Regards,
>>>> >>
>>>> >> Alfonso Nishikawa
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> 2016-12-10 2:56 GMT-01:00 Madhawa Kasun Gunasekara <
>>>> madhaw...@gmail.com>:
>>>> >>
>>>> >>> Hi Gora Devs,
>>>> >>>
>>>> >>> As you all know,  Hector is not supported for the latest cassandra
>>>> >>> releases. Shall we migrate into CQL interface. WDYT ?? I would like
>>>> to work
>>>> >>> on this task. Let me know your opinions as well.
>>>> >>>
>>>> >>> Thanks,
>>>> >>> Madhawa
>>>> >>>
>>>> >>
>>>> >>
>>>> >
>>>>
>>>>
>>>> --
>>>> http://home.apache.org/~lewismc/
>>>> @hectorMcSpector
>>>> http://www.linkedin.com/in/lmcgibbney
>>>>
>>>
>>>
>>
>>
>> --
>> http://home.apache.org/~lewismc/
>> @hectorMcSpector
>> http://www.linkedin.com/in/lmcgibbney
>>
>
>

Re: [Cassandra Store] Need to migrate to CQL Interface

[Madhawa Kasun Gunasekara]

Hi Lewis,

When is the next release? I can work on this task.

Thanks,
Madhawa

Madhawa

On Fri, Jan 27, 2017 at 11:54 PM, lewis john mcgibbney <lewi...@apache.org>
wrote:

> Hi Folks,
> Yes the entire gora-cassandra module needs an overhaul. It is horribly
> dated now and quite frankly shoudl most likely be disabled in our next
> release.
> Lewis
>
> On Sun, Dec 11, 2016 at 12:39 AM, Madhawa Kasun Gunasekara <
> madhaw...@gmail.com> wrote:
>
> > Hi Alfonso,
> >
> > Hector has been no longer used in Cassandra community. Community has been
> > migrated to CQL (Cassandra Query Language), which is very much similar to
> > SQL. and also currently Gora-Cassandra component is not compatible with
> > Cassandra database servers which use CQL 3,4 versions.
> >
> > CQL performance is much better than thrift (Hector) [1]. I created jira
> > issue for this task [2] as well.
> >
> > [1] http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-faster
> > [2] https://issues.apache.org/jira/browse/GORA-497
> >
> > Thanks,
> > Madhawa
> >
> > Madhawa
> >
> > On Sat, Dec 10, 2016 at 9:55 PM, Alfonso Nishikawa <
> > alfonso.nishik...@gmail.com> wrote:
> >
> >> Hi, Madhawa.
> >>
> >> I don't know much about Cassandra :( but I think I read time ago about
> >> some comment about the benefits of being capable of swapping the
> library.
> >> Would be very handy to what you tell.
> >>
> >> Renato, was there an issue about that?
> >>
> >> Regards,
> >>
> >> Alfonso Nishikawa
> >>
> >>
> >>
> >>
> >> 2016-12-10 2:56 GMT-01:00 Madhawa Kasun Gunasekara <madhaw...@gmail.com
> >:
> >>
> >>> Hi Gora Devs,
> >>>
> >>> As you all know,  Hector is not supported for the latest cassandra
> >>> releases. Shall we migrate into CQL interface. WDYT ?? I would like to
> work
> >>> on this task. Let me know your opinions as well.
> >>>
> >>> Thanks,
> >>> Madhawa
> >>>
> >>
> >>
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Re: Gora-Mongodb auth mechanism for SCRAM-SHA-1

[Madhawa Kasun Gunasekara]

Hi Alfonso,

I have added the fix with https://github.com/apache/gora/pull/90
and also created a jira [1] for tracking as well.

I have added an additional property to specify authentication mechanism
gora.mongodb.authentication.type
and added all the supported authentication mechanisms [2] as well.

[1] https://issues.apache.org/jira/browse/GORA-498
[2]
http://mongodb.github.io/mongo-java-driver/3.4/driver/tutorials/authentication/

Thanks,
Madhawa

Madhawa

On Sat, Dec 10, 2016 at 10:29 PM, Alfonso Nishikawa <
alfonso.nishik...@gmail.com> wrote:

> Hi, Shaharia.
>
> I don't know much about MongoDB, but taking a look at MongoStore [1] and
> Mongo documentation [2] I suspect that there is not a way at this moment.
> But, I read in .createCredential() documentation that it states at [3]:
>
> *"Creates a MongoCredential instance with an unspecified mechanism. The
> client will negotiate the best mechanism based on the version of the server
> that the client is authenticating to. If the server version is 3.0 or
> higher, the driver will authenticate using the SCRAM-SHA-1 mechanism.
> Otherwise, the driver will authenticate using the MONGODB_CR mechanism."*
>
> so it should be working. If it does not work, I don't know why :\
>
> In the meantime, if you need SCRAM-SHA-1 and will not use MONGODB-CR, you
> can try to modify the line at [1] to use .createScramSha1Credential
> 
> ()and 'mvn install' it.
>
> [1] - https://github.com/apache/gora/blob/master/gora-mongodb/
> src/main/java/org/apache/gora/mongodb/store/MongoStore.java#L156
> [2] - http://api.mongodb.com/java/current/com/mongodb/MongoCredential.html
> [3] - http://api.mongodb.com/java/current/com/mongodb/
> MongoCredential.html#createCredential-java.lang.
> String-java.lang.String-char:A-
>
> Or let's wait until someone with more knowledge answers :)
>
> Regards,
>
> Alfonso Nishikawa
>
>
> 2016-12-10 12:55 GMT-01:00 Shaharia Azam :
>
>> Hello All,
>> MongoDB has 2 types of Authentication Mechanism.
>>
>> Is there any way to define authMechanism in Gora Mongodb? Currently it
>> works well only for MONGODB-CR. So what about SCRAM-SHA-1?
>>
>> Thanks,
>> Shaharia
>>
>>
>

Re: [Cassandra Store] Need to migrate to CQL Interface

[Madhawa Kasun Gunasekara]

Hi Alfonso,

Hector has been no longer used in Cassandra community. Community has been
migrated to CQL (Cassandra Query Language), which is very much similar to
SQL. and also currently Gora-Cassandra component is not compatible with
Cassandra database servers which use CQL 3,4 versions.

CQL performance is much better than thrift (Hector) [1]. I created jira
issue for this task [2] as well.

[1] http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-faster
[2] https://issues.apache.org/jira/browse/GORA-497

Thanks,
Madhawa

Madhawa

On Sat, Dec 10, 2016 at 9:55 PM, Alfonso Nishikawa <
alfonso.nishik...@gmail.com> wrote:

> Hi, Madhawa.
>
> I don't know much about Cassandra :( but I think I read time ago about
> some comment about the benefits of being capable of swapping the library.
> Would be very handy to what you tell.
>
> Renato, was there an issue about that?
>
> Regards,
>
> Alfonso Nishikawa
>
>
>
>
> 2016-12-10 2:56 GMT-01:00 Madhawa Kasun Gunasekara <madhaw...@gmail.com>:
>
>> Hi Gora Devs,
>>
>> As you all know,  Hector is not supported for the latest cassandra
>> releases. Shall we migrate into CQL interface. WDYT ?? I would like to work
>> on this task. Let me know your opinions as well.
>>
>> Thanks,
>> Madhawa
>>
>
>

[Cassandra Store] Need to migrate to CQL Interface

[Madhawa Kasun Gunasekara]

Hi Gora Devs,

As you all know,  Hector is not supported for the latest cassandra
releases. Shall we migrate into CQL interface. WDYT ?? I would like to work
on this task. Let me know your opinions as well.

Thanks,
Madhawa