Re: [DISCUSS] Interest in rolling a release
Thank you for taking the initiative Lewis. +1 I think we can go ahead with 1.0. Last time when I checked the main branch had one test failure and maybe we should fix that before the release. On Sat, Apr 6, 2024 at 2:39 AM lewis john mcgibbney wrote: > Hi dev@, > What is the current status of Gora with regards to rolling a 0.10? Or Maybe > a 1.0? > Thanks > lewismc > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc >
Re: Personal question to the projects commit procedures
Hi Chris, Damien has been a committer/PMC member of the project since 2014. From time to time, he has been active in approving/committing changes while Lewis/myself held the chair in the project. Regarding myself, I don't think I took over anything after 16 August 2023, I have been approving/committing to the project since 2016. If you take a close look at our commit history you will probably see there are a number of PMC members involved in committing changes to the master, not only me or Damien. We both became involved in committing changes recently, just because we had availability over other PMC members. That doesn't mean, other PMC members are not allowed/encouraged to do commits or I took over Damiens committing Job. Recently the board has been requesting details on delays on GSOC project PR approval/merges. ( as per Last few reports ) That's the reason why I took over the last few commits to the main branch to settle GSoC work. Even though I approved/committed the work, several other PMC members participated helping with reviewing the PRs. But that doesn't mean, the chair is the only person commiting to the main branch. [1] https://github.com/apache/gora/commits/master/ Regards Kevin On Sun, Jan 14, 2024 at 3:40 PM Christofer Dutz wrote: > Hi all, > > while going through the projects recent activity I have come to notice, > that only a single person seems to be committing (At least according to > commits@) when going back in time it shows that this has been this way > for quite some time, however on 16. August 2023 the person doing these > commits changed. So prior to that date all commits were done (or merges > were approved by draz...@apache.org and after that date > djkevi...@apache.org is doing that job). > > Could you please shed some light on which this is that way? > > Chris > > PS: Please keep me in CC with any responses, as I'm not subscribed to this > list. >
[jira] [Commented] (GORA-698) Add GEODE Support
[ https://issues.apache.org/jira/browse/GORA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805535#comment-17805535 ] Kevin Ratnasekera commented on GORA-698: I reverted the PR due to build failures. PR in it s current shape does not execute Gora Integration test suit due to GEODE Server not started properly. Remaining work includes. [1] Write Gora Test driver to start GEODE Server. [2] Execute test suit and Fix test failure. > Add GEODE Support > - > > Key: GORA-698 > URL: https://issues.apache.org/jira/browse/GORA-698 > Project: Apache Gora > Issue Type: New Feature >Reporter: Himanshu >Priority: Major > > [1]https://geode.apache.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GORA-711) Upgrade Ignite version 2.14.0
[ https://issues.apache.org/jira/browse/GORA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766841#comment-17766841 ] Kevin Ratnasekera commented on GORA-711: PR - https://github.com/apache/gora/pull/284 > Upgrade Ignite version 2.14.0 > - > > Key: GORA-711 > URL: https://issues.apache.org/jira/browse/GORA-711 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-711) Upgrade Ignite version 2.14.0
[ https://issues.apache.org/jira/browse/GORA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-711: -- Assignee: Chaminda Neluka > Upgrade Ignite version 2.14.0 > - > > Key: GORA-711 > URL: https://issues.apache.org/jira/browse/GORA-711 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-711) Upgrade Ignite version 2.14.0
[ https://issues.apache.org/jira/browse/GORA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-711. Resolution: Fixed > Upgrade Ignite version 2.14.0 > - > > Key: GORA-711 > URL: https://issues.apache.org/jira/browse/GORA-711 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-711) Upgrade Ignite version 2.14.0
[ https://issues.apache.org/jira/browse/GORA-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-711: --- Fix Version/s: 1.0 > Upgrade Ignite version 2.14.0 > - > > Key: GORA-711 > URL: https://issues.apache.org/jira/browse/GORA-711 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-650. Resolution: Fixed > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > Labels: gsoc2020 > Time Spent: 0.5h > Remaining Estimate: 0h > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-650: -- Assignee: Chaminda Neluka (was: Trisha Melani) > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > Labels: gsoc2020 > Time Spent: 0.5h > Remaining Estimate: 0h > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-650: --- Fix Version/s: 1.0 > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Chaminda Neluka >Priority: Major > Labels: gsoc2020 > Fix For: 1.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-650: -- Assignee: Trisha Melani > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Trisha Melani >Priority: Major > Labels: gsoc2020 > Time Spent: 0.5h > Remaining Estimate: 0h > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-703) Move members to Emeritus status
[ https://issues.apache.org/jira/browse/GORA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-703. Resolution: Done > Move members to Emeritus status > --- > > Key: GORA-703 > URL: https://issues.apache.org/jira/browse/GORA-703 > Project: Apache Gora > Issue Type: Task > Components: website > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-703) Move members to Emeritus status
[ https://issues.apache.org/jira/browse/GORA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-703: -- Assignee: Kevin Ratnasekera > Move members to Emeritus status > --- > > Key: GORA-703 > URL: https://issues.apache.org/jira/browse/GORA-703 > Project: Apache Gora > Issue Type: Task > Components: website > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-712) Upgrade Apache parent pom version - 29
[ https://issues.apache.org/jira/browse/GORA-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-712: --- Description: Version 29 released recently - https://github.com/apache/maven-apache-parent/blob/apache-29/pom.xml > Upgrade Apache parent pom version - 29 > -- > > Key: GORA-712 > URL: https://issues.apache.org/jira/browse/GORA-712 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Priority: Major > > Version 29 released recently - > https://github.com/apache/maven-apache-parent/blob/apache-29/pom.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-712) Upgrade Apache parent pom version - 29
Kevin Ratnasekera created GORA-712: -- Summary: Upgrade Apache parent pom version - 29 Key: GORA-712 URL: https://issues.apache.org/jira/browse/GORA-712 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-711) Upgrade Ignite version 2.14.0
Kevin Ratnasekera created GORA-711: -- Summary: Upgrade Ignite version 2.14.0 Key: GORA-711 URL: https://issues.apache.org/jira/browse/GORA-711 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-710) Upgrade Gora-Rethinkdb to latest Rethinkdb driver
[ https://issues.apache.org/jira/browse/GORA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-710. Resolution: Not A Problem > Upgrade Gora-Rethinkdb to latest Rethinkdb driver > - > > Key: GORA-710 > URL: https://issues.apache.org/jira/browse/GORA-710 > Project: Apache Gora > Issue Type: Improvement > Components: gora-rethinkdb > Reporter: Kevin Ratnasekera >Priority: Major > > Current latest is at [1] > [1] https://github.com/rethinkdb/rethinkdb-java/releases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GORA-710) Upgrade Gora-Rethinkdb to latest Rethinkdb driver
[ https://issues.apache.org/jira/browse/GORA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708149#comment-17708149 ] Kevin Ratnasekera commented on GORA-710: Closing since current Gora code has the latest driver - https://github.com/rethinkdb/rethinkdb-java/releases > Upgrade Gora-Rethinkdb to latest Rethinkdb driver > - > > Key: GORA-710 > URL: https://issues.apache.org/jira/browse/GORA-710 > Project: Apache Gora > Issue Type: Improvement > Components: gora-rethinkdb > Reporter: Kevin Ratnasekera >Priority: Major > > Current latest is at [1] > [1] https://github.com/rethinkdb/rethinkdb-java/releases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (GORA-710) Upgrade Gora-Rethinkdb to latest Rethinkdb driver
[ https://issues.apache.org/jira/browse/GORA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708149#comment-17708149 ] Kevin Ratnasekera edited comment on GORA-710 at 4/3/23 10:25 PM: - Closing since current Gora code has the latest driver - 2.4.4. https://github.com/rethinkdb/rethinkdb-java/releases was (Author: djkevincr): Closing since current Gora code has the latest driver - https://github.com/rethinkdb/rethinkdb-java/releases > Upgrade Gora-Rethinkdb to latest Rethinkdb driver > - > > Key: GORA-710 > URL: https://issues.apache.org/jira/browse/GORA-710 > Project: Apache Gora > Issue Type: Improvement > Components: gora-rethinkdb > Reporter: Kevin Ratnasekera >Priority: Major > > Current latest is at [1] > [1] https://github.com/rethinkdb/rethinkdb-java/releases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-710) Upgrade Gora-Rethinkdb to latest Rethinkdb driver
[ https://issues.apache.org/jira/browse/GORA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-710: --- Description: Current latest is at [1] [1] https://github.com/rethinkdb/rethinkdb-java/releases was: Current latest is at [1] [1] https://github.com/rethinkdb/rethinkdb/releases/tag/v2.4.3 > Upgrade Gora-Rethinkdb to latest Rethinkdb driver > - > > Key: GORA-710 > URL: https://issues.apache.org/jira/browse/GORA-710 > Project: Apache Gora > Issue Type: Improvement > Components: gora-rethinkdb > Reporter: Kevin Ratnasekera >Priority: Major > > Current latest is at [1] > [1] https://github.com/rethinkdb/rethinkdb-java/releases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-710) Upgrade Gora-Rethinkdb to latest Rethinkdb driver
[ https://issues.apache.org/jira/browse/GORA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-710: --- Issue Type: Improvement (was: Bug) > Upgrade Gora-Rethinkdb to latest Rethinkdb driver > - > > Key: GORA-710 > URL: https://issues.apache.org/jira/browse/GORA-710 > Project: Apache Gora > Issue Type: Improvement > Components: gora-rethinkdb > Reporter: Kevin Ratnasekera >Priority: Major > > Current latest is at [1] > [1] https://github.com/rethinkdb/rethinkdb/releases/tag/v2.4.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-708) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-708: --- Issue Type: New Feature (was: Bug) > GSoC/Outreachy Project Idea > --- > > Key: GORA-708 > URL: https://issues.apache.org/jira/browse/GORA-708 > Project: Apache Gora > Issue Type: New Feature > Reporter: Kevin Ratnasekera >Priority: Major > Labels: full-time, gsoc2023 > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on ArangoDB module - > https://issues.apache.org/jira/browse/GORA-650 > 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 > 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-707) Upgrade Gora-Hive to latest Hive driver
[ https://issues.apache.org/jira/browse/GORA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-707: --- Component/s: (was: part-time) > Upgrade Gora-Hive to latest Hive driver > --- > > Key: GORA-707 > URL: https://issues.apache.org/jira/browse/GORA-707 > Project: Apache Gora > Issue Type: New Feature > Components: gora-hive > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-707) Upgrade Gora-Hive to latest Hive driver
[ https://issues.apache.org/jira/browse/GORA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-707: --- Issue Type: New Feature (was: Improvement) > Upgrade Gora-Hive to latest Hive driver > --- > > Key: GORA-707 > URL: https://issues.apache.org/jira/browse/GORA-707 > Project: Apache Gora > Issue Type: New Feature > Components: gora-hive, part-time > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-709) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-709: --- Issue Type: New Feature (was: Bug) > GSoC/Outreachy Project Idea > --- > > Key: GORA-709 > URL: https://issues.apache.org/jira/browse/GORA-709 > Project: Apache Gora > Issue Type: New Feature > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2023, part-time > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on Geode module - > https://issues.apache.org/jira/browse/GORA-698 > 2. Upgrade Hadoop version - https://issues.apache.org/jira/browse/GORA-537 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-709) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-709: --- Labels: gsoc2023 part-time (was: gsoc2023) > GSoC/Outreachy Project Idea > --- > > Key: GORA-709 > URL: https://issues.apache.org/jira/browse/GORA-709 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2023, part-time > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on Geode module - > https://issues.apache.org/jira/browse/GORA-698 > 2. Upgrade Hadoop version - https://issues.apache.org/jira/browse/GORA-537 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-707) Upgrade Gora-Hive to latest Hive driver
[ https://issues.apache.org/jira/browse/GORA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-707: --- Issue Type: Improvement (was: New Feature) > Upgrade Gora-Hive to latest Hive driver > --- > > Key: GORA-707 > URL: https://issues.apache.org/jira/browse/GORA-707 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hive > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-708) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-708: --- Labels: full-time gsoc2023 (was: gsoc2023) > GSoC/Outreachy Project Idea > --- > > Key: GORA-708 > URL: https://issues.apache.org/jira/browse/GORA-708 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > Labels: full-time, gsoc2023 > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on ArangoDB module - > https://issues.apache.org/jira/browse/GORA-650 > 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 > 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-707) Upgrade Gora-Hive to latest Hive driver
[ https://issues.apache.org/jira/browse/GORA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-707: --- Component/s: part-time > Upgrade Gora-Hive to latest Hive driver > --- > > Key: GORA-707 > URL: https://issues.apache.org/jira/browse/GORA-707 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hive, part-time > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-708) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-708: --- Labels: gsoc2023 (was: ) > GSoC/Outreachy Project Idea > --- > > Key: GORA-708 > URL: https://issues.apache.org/jira/browse/GORA-708 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2023 > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on ArangoDB module - > https://issues.apache.org/jira/browse/GORA-650 > 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 > 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-709) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-709: --- Labels: gsoc2023 (was: ) > GSoC/Outreachy Project Idea > --- > > Key: GORA-709 > URL: https://issues.apache.org/jira/browse/GORA-709 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2023 > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on Geode module - > https://issues.apache.org/jira/browse/GORA-698 > 2. Upgrade Hadoop version - https://issues.apache.org/jira/browse/GORA-537 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-709) GSoC/Outreachy Project Idea
Kevin Ratnasekera created GORA-709: -- Summary: GSoC/Outreachy Project Idea Key: GORA-709 URL: https://issues.apache.org/jira/browse/GORA-709 Project: Apache Gora Issue Type: Bug Reporter: Kevin Ratnasekera I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on Geode module - https://issues.apache.org/jira/browse/GORA-698 2. Upgrade Hadoop version - https://issues.apache.org/jira/browse/GORA-537 We could scope out the project adding / removing sub tasks based on the available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-708) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-708: --- Description: I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on ArangoDB module - https://issues.apache.org/jira/browse/GORA-650 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 We could scope out the project adding / removing sub tasks based on the available capacity of the student and project. was: I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on ArangoDB module - https://issues.apache.org/jira/browse/GORA-650 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 We could scope out the project adding / removing sub tasks based on the available capacity of the student. > GSoC/Outreachy Project Idea > --- > > Key: GORA-708 > URL: https://issues.apache.org/jira/browse/GORA-708 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on ArangoDB module - > https://issues.apache.org/jira/browse/GORA-650 > 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 > 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student and project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-708) GSoC/Outreachy Project Idea
Kevin Ratnasekera created GORA-708: -- Summary: GSoC/Outreachy Project Idea Key: GORA-708 URL: https://issues.apache.org/jira/browse/GORA-708 Project: Apache Gora Issue Type: Bug Reporter: Kevin Ratnasekera I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on ArangoDB module - https://issues.apache.org/jira/browse/GORA-650 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 We could scope out the project adding / removing sub task based on the available capacity of the student. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-708) GSoC/Outreachy Project Idea
[ https://issues.apache.org/jira/browse/GORA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-708: --- Description: I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on ArangoDB module - https://issues.apache.org/jira/browse/GORA-650 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 We could scope out the project adding / removing sub tasks based on the available capacity of the student. was: I would like to propose a project idea suitable for GSoC and Outreachy comprises of following sub tasks. 1. Complete rest of unfinished work on ArangoDB module - https://issues.apache.org/jira/browse/GORA-650 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 We could scope out the project adding / removing sub task based on the available capacity of the student. > GSoC/Outreachy Project Idea > --- > > Key: GORA-708 > URL: https://issues.apache.org/jira/browse/GORA-708 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera >Priority: Major > > I would like to propose a project idea suitable for GSoC and Outreachy > comprises of following sub tasks. > 1. Complete rest of unfinished work on ArangoDB module - > https://issues.apache.org/jira/browse/GORA-650 > 2. Upgrade HBase driver - https://issues.apache.org/jira/browse/GORA-706 > 3. Upgrade Hive driver - https://issues.apache.org/jira/browse/GORA-707 > We could scope out the project adding / removing sub tasks based on the > available capacity of the student. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-707) Upgrade Gora-Hive to latest Hive driver
[ https://issues.apache.org/jira/browse/GORA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-707: --- Issue Type: Improvement (was: Bug) > Upgrade Gora-Hive to latest Hive driver > --- > > Key: GORA-707 > URL: https://issues.apache.org/jira/browse/GORA-707 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hive > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-707) Upgrade Gora-Hive to latest Hive driver
Kevin Ratnasekera created GORA-707: -- Summary: Upgrade Gora-Hive to latest Hive driver Key: GORA-707 URL: https://issues.apache.org/jira/browse/GORA-707 Project: Apache Gora Issue Type: Bug Components: gora-hive Reporter: Kevin Ratnasekera -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-706) Upgrade Gora-HBase to latest HBase driver
[ https://issues.apache.org/jira/browse/GORA-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-706: --- Issue Type: Improvement (was: Bug) > Upgrade Gora-HBase to latest HBase driver > - > > Key: GORA-706 > URL: https://issues.apache.org/jira/browse/GORA-706 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hbase > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GORA-706) Upgrade Gora-HBase to latest HBase driver
[ https://issues.apache.org/jira/browse/GORA-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-706: --- Summary: Upgrade Gora-HBase to latest HBase driver (was: Upgrade HBase to latest driver) > Upgrade Gora-HBase to latest HBase driver > - > > Key: GORA-706 > URL: https://issues.apache.org/jira/browse/GORA-706 > Project: Apache Gora > Issue Type: Bug > Components: gora-hbase > Reporter: Kevin Ratnasekera >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-706) Upgrade HBase to latest driver
Kevin Ratnasekera created GORA-706: -- Summary: Upgrade HBase to latest driver Key: GORA-706 URL: https://issues.apache.org/jira/browse/GORA-706 Project: Apache Gora Issue Type: Bug Components: gora-hbase Reporter: Kevin Ratnasekera -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-651) Upgrade OrientDB to the latest version 3
[ https://issues.apache.org/jira/browse/GORA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-651. Fix Version/s: 1.0 Resolution: Fixed > Upgrade OrientDB to the latest version 3 > > > Key: GORA-651 > URL: https://issues.apache.org/jira/browse/GORA-651 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > Fix For: 1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seem version 3 based releases [1] have been there for a while, we should > upgrade from 2.2.22. > [1] https://orientdb.com/releases/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-651) Upgrade OrientDB to the latest version 3
[ https://issues.apache.org/jira/browse/GORA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-651: -- Assignee: Kevin Ratnasekera > Upgrade OrientDB to the latest version 3 > > > Key: GORA-651 > URL: https://issues.apache.org/jira/browse/GORA-651 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > It seem version 3 based releases [1] have been there for a while, we should > upgrade from 2.2.22. > [1] https://orientdb.com/releases/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-705) Update Apache Gora site with Neo4j Gora datastore
Kevin Ratnasekera created GORA-705: -- Summary: Update Apache Gora site with Neo4j Gora datastore Key: GORA-705 URL: https://issues.apache.org/jira/browse/GORA-705 Project: Apache Gora Issue Type: Bug Components: website Affects Versions: 0.9 Reporter: Kevin Ratnasekera Fix For: 1.0 Attachments: gora-neo4j.md, index.md Update attached files in Apache Gora website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-663) Add datastore for Neo4j
[ https://issues.apache.org/jira/browse/GORA-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-663. Fix Version/s: 1.0 Resolution: Fixed > Add datastore for Neo4j > --- > > Key: GORA-663 > URL: https://issues.apache.org/jira/browse/GORA-663 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 >Reporter: Carlos Muñoz >Assignee: Gaby Ortiz >Priority: Major > Labels: outreachy2020 > Fix For: 1.0 > > Attachments: gora-neo4j.md, index.md > > Time Spent: 50m > Remaining Estimate: 0h > > Graph databases are becoming increasingly popular in big data applications. > Maybe we should consider work with them in Apache Gora. > [https://neo4j.com/developer/get-started/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-704) Fix build failure due to Spark Upgrade
Kevin Ratnasekera created GORA-704: -- Summary: Fix build failure due to Spark Upgrade Key: GORA-704 URL: https://issues.apache.org/jira/browse/GORA-704 Project: Apache Gora Issue Type: Bug Affects Versions: 0.9 Reporter: Kevin Ratnasekera Fix For: 1.0 https://issues.apache.org/jira/browse/GORA-702 due to recent upgrade, Spark Test is getting failed due to below error. java.lang.NoSuchMethodError: org.apache.hadoop.conf.Configuration.getPassword(Ljava/lang/String;)[C at org.apache.gora.mongodb.mapreduce.TestMongoStoreWordCount.testSparkWordCount(TestMongoStoreWordCount.java:67) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-694) Upgrade Aerospike datastore java driver to the latest
[ https://issues.apache.org/jira/browse/GORA-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-694. Resolution: Fixed > Upgrade Aerospike datastore java driver to the latest > - > > Key: GORA-694 > URL: https://issues.apache.org/jira/browse/GORA-694 > Project: Apache Gora > Issue Type: Improvement > Components: gora-aerospike >Affects Versions: 0.9 >Reporter: Trisha Melani >Assignee: Trisha Melani >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-694) Upgrade Aerospike datastore java driver to the latest
[ https://issues.apache.org/jira/browse/GORA-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-694: -- Assignee: Trisha Melani > Upgrade Aerospike datastore java driver to the latest > - > > Key: GORA-694 > URL: https://issues.apache.org/jira/browse/GORA-694 > Project: Apache Gora > Issue Type: Improvement > Components: gora-aerospike >Affects Versions: 0.9 >Reporter: Trisha Melani >Assignee: Trisha Melani >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-703) Move members to Emeritus status
Kevin Ratnasekera created GORA-703: -- Summary: Move members to Emeritus status Key: GORA-703 URL: https://issues.apache.org/jira/browse/GORA-703 Project: Apache Gora Issue Type: Task Components: website Reporter: Kevin Ratnasekera -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-702) Upgrade spark to 2.4.8
[ https://issues.apache.org/jira/browse/GORA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-702. Resolution: Fixed > Upgrade spark to 2.4.8 > -- > > Key: GORA-702 > URL: https://issues.apache.org/jira/browse/GORA-702 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Tom Cunningham >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GORA-702) Upgrade spark to 2.4.8
[ https://issues.apache.org/jira/browse/GORA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699377#comment-17699377 ] Kevin Ratnasekera commented on GORA-702: PR raised on - https://github.com/apache/gora/pull/272 > Upgrade spark to 2.4.8 > -- > > Key: GORA-702 > URL: https://issues.apache.org/jira/browse/GORA-702 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Tom Cunningham >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-702) Upgrade spark to 2.4.8
[ https://issues.apache.org/jira/browse/GORA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-702: -- Assignee: Tom Cunningham > Upgrade spark to 2.4.8 > -- > > Key: GORA-702 > URL: https://issues.apache.org/jira/browse/GORA-702 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Assignee: Tom Cunningham >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-702) Upgrade spark to 2.4.8
Kevin Ratnasekera created GORA-702: -- Summary: Upgrade spark to 2.4.8 Key: GORA-702 URL: https://issues.apache.org/jira/browse/GORA-702 Project: Apache Gora Issue Type: Improvement Components: gora-core Affects Versions: 0.9 Reporter: Kevin Ratnasekera Fix For: 1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-693) Improve Gora Jet Test Cases
[ https://issues.apache.org/jira/browse/GORA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-693. Resolution: Fixed > Improve Gora Jet Test Cases > --- > > Key: GORA-693 > URL: https://issues.apache.org/jira/browse/GORA-693 > Project: Apache Gora > Issue Type: Improvement > Components: gora-jet >Affects Versions: 0.9 >Reporter: Trisha Melani > Assignee: Kevin Ratnasekera >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-693) Improve Gora Jet Test Cases
[ https://issues.apache.org/jira/browse/GORA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-693: -- Assignee: Kevin Ratnasekera > Improve Gora Jet Test Cases > --- > > Key: GORA-693 > URL: https://issues.apache.org/jira/browse/GORA-693 > Project: Apache Gora > Issue Type: Improvement > Components: gora-jet >Affects Versions: 0.9 >Reporter: Trisha Melani > Assignee: Kevin Ratnasekera >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-693) Improve Gora Jet Test Cases
[ https://issues.apache.org/jira/browse/GORA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-693: -- Assignee: Trisha Melani (was: Kevin Ratnasekera) > Improve Gora Jet Test Cases > --- > > Key: GORA-693 > URL: https://issues.apache.org/jira/browse/GORA-693 > Project: Apache Gora > Issue Type: Improvement > Components: gora-jet >Affects Versions: 0.9 >Reporter: Trisha Melani >Assignee: Trisha Melani >Priority: Major > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-701) Fix Github workflow build for PRs
[ https://issues.apache.org/jira/browse/GORA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-701. Resolution: Fixed > Fix Github workflow build for PRs > - > > Key: GORA-701 > URL: https://issues.apache.org/jira/browse/GORA-701 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > > Currently this Error - The runner has received a shutdown signal prevent us > running builds on pull requests. > This is already reported and solution is discussed here - > https://github.com/actions/runner-images/issues/6709 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GORA-699) Unstable build due to test Redis test failures
[ https://issues.apache.org/jira/browse/GORA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-699. Fix Version/s: 1.0 Resolution: Fixed > Unstable build due to test Redis test failures > -- > > Key: GORA-699 > URL: https://issues.apache.org/jira/browse/GORA-699 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > Fix For: 1.0 > > > [main] INFO [grokzen/redis-cluster:latest] - Creating container for image: > grokzen/redis-cluster:latest > [main] INFO [grokzen/redis-cluster:latest] - Starting container with ID: > fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 > [main] INFO [grokzen/redis-cluster:latest] - Container > grokzen/redis-cluster:latest is starting: > fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 > [main] ERROR [grokzen/redis-cluster:latest] - Could not start container > org.testcontainers.containers.ContainerLaunchException: Timed out waiting for > log output matching '.*Background AOF rewrite finished successfully.*' > at > org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:49) > at > org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:35) > at > org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:892) > at > org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:440) > at > org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:325) > at > org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81) > at > org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:323) > at > org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311) > at > org.apache.gora.redis.GoraRedisTestDriver.setUpClass(GoraRedisTestDriver.java:57) > at > org.apache.gora.store.DataStoreTestBase.setUpClass(DataStoreTestBase.java:61) > at > org.apache.gora.store.DataStoreTestBase.setUp(DataStoreTestBase.java:80) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBo
[jira] [Assigned] (GORA-699) Unstable build due to test Redis test failures
[ https://issues.apache.org/jira/browse/GORA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-699: -- Assignee: Kevin Ratnasekera > Unstable build due to test Redis test failures > -- > > Key: GORA-699 > URL: https://issues.apache.org/jira/browse/GORA-699 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > > [main] INFO [grokzen/redis-cluster:latest] - Creating container for image: > grokzen/redis-cluster:latest > [main] INFO [grokzen/redis-cluster:latest] - Starting container with ID: > fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 > [main] INFO [grokzen/redis-cluster:latest] - Container > grokzen/redis-cluster:latest is starting: > fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 > [main] ERROR [grokzen/redis-cluster:latest] - Could not start container > org.testcontainers.containers.ContainerLaunchException: Timed out waiting for > log output matching '.*Background AOF rewrite finished successfully.*' > at > org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:49) > at > org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:35) > at > org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:892) > at > org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:440) > at > org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:325) > at > org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81) > at > org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:323) > at > org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311) > at > org.apache.gora.redis.GoraRedisTestDriver.setUpClass(GoraRedisTestDriver.java:57) > at > org.apache.gora.store.DataStoreTestBase.setUpClass(DataStoreTestBase.java:61) > at > org.apache.gora.store.DataStoreTestBase.setUp(DataStoreTestBase.java:80) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at > org.apache.ma
[jira] [Assigned] (GORA-701) Fix Github workflow build for PRs
[ https://issues.apache.org/jira/browse/GORA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-701: -- Assignee: Kevin Ratnasekera > Fix Github workflow build for PRs > - > > Key: GORA-701 > URL: https://issues.apache.org/jira/browse/GORA-701 > Project: Apache Gora > Issue Type: Bug > Reporter: Kevin Ratnasekera > Assignee: Kevin Ratnasekera >Priority: Major > > Currently this Error - The runner has received a shutdown signal prevent us > running builds on pull requests. > This is already reported and solution is discussed here - > https://github.com/actions/runner-images/issues/6709 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-701) Fix Github workflow build for PRs
Kevin Ratnasekera created GORA-701: -- Summary: Fix Github workflow build for PRs Key: GORA-701 URL: https://issues.apache.org/jira/browse/GORA-701 Project: Apache Gora Issue Type: Bug Reporter: Kevin Ratnasekera Currently this Error - The runner has received a shutdown signal prevent us running builds on pull requests. This is already reported and solution is discussed here - https://github.com/actions/runner-images/issues/6709 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GORA-699) Unstable build due to test Redis test failures
Kevin Ratnasekera created GORA-699: -- Summary: Unstable build due to test Redis test failures Key: GORA-699 URL: https://issues.apache.org/jira/browse/GORA-699 Project: Apache Gora Issue Type: Bug Reporter: Kevin Ratnasekera [main] INFO [grokzen/redis-cluster:latest] - Creating container for image: grokzen/redis-cluster:latest [main] INFO [grokzen/redis-cluster:latest] - Starting container with ID: fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 [main] INFO [grokzen/redis-cluster:latest] - Container grokzen/redis-cluster:latest is starting: fd00f67a80705cc56cf16e9ccf1c1b74605dbf30755f26d3743e664c8b3ca991 [main] ERROR [grokzen/redis-cluster:latest] - Could not start container org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*Background AOF rewrite finished successfully.*' at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:49) at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:35) at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:892) at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:440) at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:325) at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81) at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:323) at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311) at org.apache.gora.redis.GoraRedisTestDriver.setUpClass(GoraRedisTestDriver.java:57) at org.apache.gora.store.DataStoreTestBase.setUpClass(DataStoreTestBase.java:61) at org.apache.gora.store.DataStoreTestBase.setUp(DataStoreTestBase.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) [main] ERROR [grokzen/redis-cluster:latest] - Log output from the failed container: -- IP Before trim: '172.17.0.3 ' -- IP Before split: '172.17.0.3' -- IP After trim: '172.17.0.3' port 5000 sentinel monitor sentinel7000 127.0.0.1 7000 2 sentinel down-after-milliseconds sentinel7000 5000 sentinel failover-timeout sentinel7000 6 sentinel parallel-syncs sentinel7000 1 port 5001 sentinel monitor sentinel7001 127.0.0.1 7001 2 sentinel down-after-milliseconds sentinel7001 5000 sentinel failover-timeout sentinel7001 6 sentinel parallel
[jira] [Resolved] (GORA-690) Upgrade to Apache pom parent 24
[ https://issues.apache.org/jira/browse/GORA-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-690. Resolution: Fixed [~trisha] Thank you for the contribution. > Upgrade to Apache pom parent 24 > --- > > Key: GORA-690 > URL: https://issues.apache.org/jira/browse/GORA-690 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.9 >Reporter: Trisha Melani >Assignee: Trisha Melani >Priority: Minor > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GORA-690) Upgrade to Apache pom parent 24
[ https://issues.apache.org/jira/browse/GORA-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-690: -- Assignee: Trisha Melani > Upgrade to Apache pom parent 24 > --- > > Key: GORA-690 > URL: https://issues.apache.org/jira/browse/GORA-690 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.9 >Reporter: Trisha Melani >Assignee: Trisha Melani >Priority: Minor > Fix For: 1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GORA-405) Create Gora OpenAPI specification
[ https://issues.apache.org/jira/browse/GORA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425188#comment-17425188 ] Kevin Ratnasekera commented on GORA-405: Hi [~lewismc] Thank you for the suggestion, I updated the Jira ticket. :) Regards Kevin > Create Gora OpenAPI specification > - > > Key: GORA-405 > URL: https://issues.apache.org/jira/browse/GORA-405 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler, gora-core >Reporter: Udesh Liyanaarachchi >Assignee: Udesh Liyanaarachchi >Priority: Minor > Labels: gsoc2019, outreachy2021 > Fix For: 1.0 > > > As to the discussion [~lewismc] initiated in the > [mail list > thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we > need to implement a REST API for GORA. > This is the initial proposal documentation for the [GORA REST > API|http://docs.apachegoraapi.apiary.io/]. > The plan will be to implement the API with [Apache CXF > |http://cxf.apache.org] using [CXF's JAXRS > |http://cxf.apache.org/docs/jax-rs.html] implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-405) Create Gora OpenAPI specification
[ https://issues.apache.org/jira/browse/GORA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-405: --- Summary: Create Gora OpenAPI specification (was: Create Gora REST API) > Create Gora OpenAPI specification > - > > Key: GORA-405 > URL: https://issues.apache.org/jira/browse/GORA-405 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler, gora-core >Reporter: Udesh Liyanaarachchi >Assignee: Udesh Liyanaarachchi >Priority: Minor > Labels: gsoc2019, outreachy2021 > Fix For: 1.0 > > > As to the discussion [~lewismc] initiated in the > [mail list > thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we > need to implement a REST API for GORA. > This is the initial proposal documentation for the [GORA REST > API|http://docs.apachegoraapi.apiary.io/]. > The plan will be to implement the API with [Apache CXF > |http://cxf.apache.org] using [CXF's JAXRS > |http://cxf.apache.org/docs/jax-rs.html] implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-405) Create Gora REST API
[ https://issues.apache.org/jira/browse/GORA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-405: --- Labels: gsoc2019 outreachy2021 (was: gsoc2019) > Create Gora REST API > > > Key: GORA-405 > URL: https://issues.apache.org/jira/browse/GORA-405 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler, gora-core >Reporter: Udesh Liyanaarachchi >Assignee: Udesh Liyanaarachchi >Priority: Minor > Labels: gsoc2019, outreachy2021 > Fix For: 1.0 > > > As to the discussion [~lewismc] initiated in the > [mail list > thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we > need to implement a REST API for GORA. > This is the initial proposal documentation for the [GORA REST > API|http://docs.apachegoraapi.apiary.io/]. > The plan will be to implement the API with [Apache CXF > |http://cxf.apache.org] using [CXF's JAXRS > |http://cxf.apache.org/docs/jax-rs.html] implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Add datastore for Elasticsearch. Outreachy Week 13 Report
Hi Maria, Finally I made some time to review and merge your PR into the master branch. Thank you for all the contributions you have made to Apache Gora, during your Outreachy internship. Regards Kevin On Tue, Mar 2, 2021 at 11:30 AM Maria Podorvanova < podorvanova.ma...@gmail.com> wrote: > Hi, > > Report #13 > Week 13: February, 28 - March, 2 > Activities: > - Submitted final feedback > - Posted last blog post > - Created a separate ticket[1] for Elasticsearch documentation for Apache > Gora website and attached a patch with my documentation > - Made a PR[2] with my code > > Question: > CI build failed with weird errors, I am not sure what they are caused by. > Should I do something about it? > > [1] https://issues.apache.org/jira/browse/GORA-670 > [2] https://github.com/apache/gora/pull/234 > > Regards, > Maria >
[jira] [Resolved] (GORA-664) Add datastore for Elasticsearch
[ https://issues.apache.org/jira/browse/GORA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-664. Fix Version/s: 1.0 Resolution: Fixed > Add datastore for Elasticsearch > --- > > Key: GORA-664 > URL: https://issues.apache.org/jira/browse/GORA-664 > Project: Apache Gora > Issue Type: New Feature >Reporter: Carlos Muñoz >Assignee: Mariia Podorvanova >Priority: Major > Labels: outreachy2020 > Fix For: 1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Elasticsearch is a Lucene-based search engine that primarily focuses on > distribution and availability. It could be a good alternative for the > gora-solr module. > > [https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-664) Add datastore for Elasticsearch
[ https://issues.apache.org/jira/browse/GORA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397559#comment-17397559 ] Kevin Ratnasekera commented on GORA-664: [~mariia.podorvanova] Finally I was able to allocate some time to review and merge your PR. Thank you for your hard work during the Outreachy Internship. > Add datastore for Elasticsearch > --- > > Key: GORA-664 > URL: https://issues.apache.org/jira/browse/GORA-664 > Project: Apache Gora > Issue Type: New Feature >Reporter: Carlos Muñoz >Assignee: Mariia Podorvanova >Priority: Major > Labels: outreachy2020 > Time Spent: 10m > Remaining Estimate: 0h > > Elasticsearch is a Lucene-based search engine that primarily focuses on > distribution and availability. It could be a good alternative for the > gora-solr module. > > [https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-679) Restlet JARs and third party dependencies aren’t available in the main public Maven repository
[
https://issues.apache.org/jira/browse/GORA-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341018#comment-17341018
]
Kevin Ratnasekera commented on GORA-679:
Hi [~lewismc]
This jar is getting resolved to http://maven.restlet.org repository in my local
machine.
[*INFO*] *-<* org.apache.gora:gora-solr
*>--*
[*INFO*] *Building Apache Gora :: Solr 1.0-SNAPSHOT
[18/28]*
[*INFO*] *---[ bundle
]---*
Downloading from central:
https://repo.maven.apache.org/maven2/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom
Downloading from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom
Downloaded from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom
(614 B at 75 B/s)
Downloading from central:
https://repo.maven.apache.org/maven2/org/restlet/jee/org.restlet.parent/2.3.1/org.restlet.parent-2.3.1.pom
Downloading from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.parent/2.3.1/org.restlet.parent-2.3.1.pom
Downloaded from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.parent/2.3.1/org.restlet.parent-2.3.1.pom
(9.4 kB at 7.0 kB/s)
Downloading from central:
https://repo.maven.apache.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.pom
Downloading from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.pom
Downloaded from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.pom
(915 B at 397 B/s)
Downloading from central:
https://repo.maven.apache.org/maven2/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.jar
Downloading from central:
https://repo.maven.apache.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.jar
Downloading from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.jar
Downloading from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.jar
Downloaded from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.1/org.restlet.ext.servlet-2.3.1.jar
(23 kB at 8.6 kB/s)
Downloaded from maven-restlet:
http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.jar
(709 kB at 179 kB/s)
> Restlet JARs and third party dependencies aren’t available in the main public
> Maven repository
> --
>
> Key: GORA-679
> URL: https://issues.apache.org/jira/browse/GORA-679
> Project: Apache Gora
> Issue Type: Improvement
> Components: build process
>Affects Versions: 0.9
>Reporter: Lewis John McGibbney
>Priority: Blocker
> Fix For: 1.0
>
>
> The CI process complains about the following issue which ultimately fails the
> builds
> {code:bash}
> Error: Failed to execute goal on project gora-solr: Could not resolve
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT:
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 ->
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-default-http-blocker
> (http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet
> (http://maven.restlet.org, default, releases+snapshots), apache.snapshots
> (http://repository.apache.org/snapshots, default, disabled)] -> [Help 1]
> {code}
> I took at look at the [Restlet
> website|https://restlet.talend.com/downloads/current/] and discovered the
> following
> {quote}The Maven repository for Restlet is accessible from
> https://maven.restlet.talend.com and contains all Restlet JARs and third
> party dependencies that aren’t available in the main public Maven repository.
> It is automatically refreshed once a day if the build succeeds.{quote}
> So it looks like we need to update the Maven configuration to accommodate the
> change...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [PROPOSAL] Pull request hackathon
+1 I am in Lewis. I will help out, I Apologize from my end not having much time to review these with recent times. On Fri, May 7, 2021 at 11:31 PM Lewis John McGibbney wrote: > Hi dev@, > I was taking a look at the Gora pull requests. > Firsly, let me say how encouraged I am by all of the new modules... this > is really neat! A lot of hard work has gone into producing these results. > There are quite a few open pull requests. With that in mind, I wondered if > anyone would be interested having a virtual hackathon of sorts where we > could openly review the open pull requests one at a time and determine what > needs to be done to get them into master branch. > Is anyone interested in this? I so, can do a Doodle poll for availability. > Thanks > lewismc >
Re: GSoc 2021 rewrite gora-sql from JOOQ Library
Hi Lewis, Madhawa and Myself volunteered to mentor this project. We are looking forward to taking this project, if we are able to allocate a slot from Apache. I have observed you have done some work on gora-sql, we are looking forward for your feedback. Regards Kevin On Tue, May 4, 2021 at 12:36 AM lewis john mcgibbney wrote: > Yeah I’ll take a look but unfortunately I’m not in a position to mentor > this time. > I’ll have a look and make any suggestions. > Thank you > > On Mon, May 3, 2021 at 10:12 Mohamed Infaz wrote: > > > Hi Lewis, > > > > Thanks for getting back to me, yes this project is going ahead but I > think > > it's in the proposal evaluation stage. > > Can you kindly provide me feedback on this project? > > > > Regards, > > Infaz. > > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc >
Re: [Gora] builds.apache.org
Hi Alfonso, I just checked the Any23 job configuration link, I get the same error related to missing permissions. I think only committers of the particular project are allowed to read / write access to build configurations. Let's see whether we can find issues with our current gora-pipeline configuration. Regards Kevin On Sat, Mar 27, 2021 at 2:54 PM Alfonso Nishikawa < alfonso.nishik...@gmail.com> wrote: > Hi! > > It seems I dont have the permission task/configure to access > https://ci-builds.apache.org/job/Any23/job/any23-master-jdk8/configure :( > May I get the permissions? :) > > Thank you! > > Regards, > Alfonso > > > El mar, 23 mar 2021 a las 7:54, Alfonso Nishikawa (< > alfonso.nishik...@gmail.com>) escribió: > >> Hi, Lewis! >> >> I will take a look and comment if I have any issue. >> >> Thank you!! :) >> >> Regards, >> Alfonso >> >> El mar., 23 mar. 2021 1:12, Lewis John McGibbney >> escribió: >> >>> Hi Alfonso, >>> The Gora builds now reside on the Cloudbees Jenkins server (which I >>> think you already figured out) >>> https://ci-builds.apache.org/job/Gora/job/gora-pipeline/job/master/ >>> I don't have time to look into configuring the job right now but if you >>> look at the Any23 build we did a while back, then you can basically copy it >>> for the Gora master build >>> https://ci-builds.apache.org/job/Any23/job/any23-master-jdk8/configure >>> I hope this makes sense. >>> lewismc >>> >>> On 2021/03/13 16:48:49, Alfonso Nishikawa >>> wrote: >>> > Hi! >>> > >>> > I am reopening this topic because I found that the jars master >>> x.x-SNAPSHOT >>> > are not being published to the repository of snapshots at the apache >>> > repository >>> > >>> https://repository.apache.org/#view-repositories;snapshots-group~browsestorage~org/apache/gora/gora-hbase/1.0-SNAPSHOT/ >>> > since Jun 2020. >>> > >>> > I guess we would need to add a "deploy" step to the Jenkins file (see >>> > https://github.com/apache/gora/pull/229 , >>> > https://www.jenkins.io/doc/book/pipeline/jenkinsfile/) but does anyone >>> > exactly what command is it? Or how to configure it? Maybe I have to ask >>> > INFRA? >>> > >>> > Let me know :) >>> > >>> > Thank you! >>> > >>> > Regards, >>> > Alfonso Nishikawa >>> > >>> > >>> > >>> > >>> > El sáb, 31 oct 2020 a las 17:28, Alfonso Nishikawa (< >>> > alfonso.nishik...@gmail.com>) escribió: >>> > >>> > > All merits go for Damien :D Thanks too! >>> > > >>> > > Best regards, >>> > > >>> > > Alfonso Nishikawa >>> > > >>> > > El sáb., 31 oct. 2020 a las 16:59, Kevin Ratnasekera (< >>> > > djkevincr1...@gmail.com>) escribió: >>> > > >>> > >> Hi Damien/Alfonso, >>> > >> >>> > >> I just noticed the jenkins build system works just fine. Thank you >>> for >>> > >> setting up builds again. :) >>> > >> >>> > >> Regards >>> > >> Kevin >>> > >> >>> > >> On Tue, Oct 27, 2020 at 5:27 AM Alfonso Nishikawa < >>> > >> alfonso.nishik...@gmail.com> wrote: >>> > >> >>> > >>> Hi, Damien. >>> > >>> >>> > >>> I really don't know anything about how to configure Jenkins, so >>> > >>> everything >>> > >>> seems ok to me n_nU >>> > >>> >>> > >>> Thank you! >>> > >>> >>> > >>> Best regards, >>> > >>> >>> > >>> Alfonso Nishikawa >>> > >>> >>> > >>> El sáb., 24 oct. 2020 a las 21:15, Damien Raude-Morvan (< >>> > >>> draz...@drazzib.com>) >>> > >>> escribió: >>> > >>> >>> > >>> > Hi Kevin & Alfonso ! >>> > >>> > >>> > >>> > I've pretty good experience regarding creating Jenkinsfile for >>> Java >>> > >>> > projects. I think this is the way to go for Gora. >>> > >>> > >>> > >>> >
[jira] [Created] (GORA-673) Improve Apache Gora source Documentations
Kevin Ratnasekera created GORA-673: -- Summary: Improve Apache Gora source Documentations Key: GORA-673 URL: https://issues.apache.org/jira/browse/GORA-673 Project: Apache Gora Issue Type: Task Affects Versions: 0.9 Reporter: Kevin Ratnasekera Improve javadoc documentation for Apache Gora Core module API. Fix all the javadoc related build issues as well incomplete documentations for these core APIs. Improve datastore documentations for mapping file and property file attributes with proper descriptions and possible/default values. Improve documentations for gora-tutorial module samples so that it can be easily understood. Update all the readme files and runnable scripts ( sh files ) and it s documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[Discuss] Apache Gora Next Release
Hi all, This is to initiate a discussion on $subject. I think there's considerable work already merged to master branch. Is there anything else we want to include in the Gora 1.0 development drive or can we go ahead and produce a release candidate? Regards Kevin
Re: Add datastore for Elasticsearch. Outreachy Week 11 Report
Hi Maria, Thank you for hard work Maria. Can you raise a PR, once you are comfortable with changes? Regards Kevin On Thu, Feb 25, 2021 at 10:06 AM Maria Podorvanova < podorvanova.ma...@gmail.com> wrote: > Hi John, > > Thanks for your comment. I am working on it. > > Regards, > Maria > > On Wed, 24 Feb 2021 at 17:50, John Mora wrote: > >> Hi Maria. >> >> Thanks for the update. >> >> Unfortunately, looping through all possible values in the range is not a >> practical solution. >> >> You should use the range query feature for this: >> >> https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-range-query.html >> >> I think you should manually add a special field in the elasticsearch >> record that you can range query (you can add it to the mapping file as a >> 'mock' primary key field). It will be basically a copy of the '_id' field. >> >> Here, you can find a similar workaround in the Redis DataStore where >> Sorted Sets were as secondary indexes for range queries. >> >> >> https://github.com/apache/gora/blob/master/gora-redis/src/main/java/org/apache/gora/redis/store/RedisStore.java#L299 >> >> Best, >> John >> >> El sáb, 20 feb 2021 a las 3:01, Maria Podorvanova (< >> podorvanova.ma...@gmail.com>) escribió: >> >>> Hi, >>> >>> Report #11 >>> Week 11: February, 14 - February, 20 >>> Activities: >>> - Added scaling_factor support [1] >>> - Removed unsupported Elasticsearch data types [2] >>> - Implemented Metadata Analyzer for Elasticsearch Store [3] >>> - Tried to fix range query by “_id” field [4] >>> - Wrote documentation for Apache Gora website [5] >>> - Polished and sent my CV for reviewing >>> >>> Question: >>> >>>1. I tried to fix the issue, where Elasticsearch "_id" field does >>>not support range queries. I've tried treating "_id" as a number, but one >>>of the test "_id" field values is "http://foo.com/;. So >>>my approach did not work, but I decided to commit[4] my work on this >>> issue >>>in order to show you what I tried to do. >>> >>> >>> [1] >>> https://github.com/apache/gora/commit/670a04c51f4a6d169df319ed5fd3d1d0abd81870 >>> [2] >>> https://github.com/apache/gora/commit/55020d722f9424021fefe8d94b6bf3ece213226d >>> [3] >>> https://github.com/apache/gora/commit/c491a6447d197b0509473294ee844834b1623a63 >>> [4] >>> https://github.com/apache/gora/commit/a870ca8a2075af7cbab75b9341a94de4966fbf7a >>> [5] >>> https://docs.google.com/document/d/1AF6MG3pqe6A5Z0KtLooEKQlipuyeObbYlAa4O7rFXqM/edit?usp=sharing >>> >>> Regards, >>> Maria >>> >>
Re: Your project's website
Hi Andrew, Happy new year to you too. Apologize for the late checking on this. I will go through this, and get back to you. Regards Kevin On Sat, Jan 9, 2021 at 8:03 PM Andrew Wetmore wrote: > Hi, and happy New Year. > > Have you been able to make any progress in migrating your project website > off the Apache CMS and onto some other technology? Infra has suggestions if > you are stuck. > > Andrew > > On Mon, Aug 17, 2020 at 10:23 AM Andrew Wetmore > wrote: > > > Hi, all. > > > > Any progress on preparing to migrate the site off the CMS? You can open a > > Jira ticket at any time for INFRA to track the work we will need to do, > and > > you will also need to hold a PMC vote to approve the move and allow Infra > > to close down your presence on the CMS once the move is complete. > > > > Thanks! > > > > Andrew > > > > On Wed, Aug 5, 2020 at 9:16 AM Andrew Wetmore > wrote: > > > >> Hi: > >> > >> I am part of the Infrastructure team, and am writing to ask whether your > >> project is still using the Apache CMS for your project website. As you > >> know, the CMS is reaching end-of-life, and we need projects to move > their > >> websites onto a different option within the next few weeks. > >> > >> There are several alternatives available, including those listed on this > >> page [1] on managing project websites. Infra is assembling a Wiki page > [2] > >> on migrating a website from the CMS, and is looking forward to helping > >> projects with this transition. > >> > >> Please let me know whether your site is still on the Apache CMS and, if > >> so, who will be the project point-of-contact with Infra for the > migration. > >> > >> Thank you! > >> > >> > >> > >> > >> [1] https://infra.apache.org/project-site.html > >> > >> [2] > >> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > >> > >> > >> > >> -- > >> Andrew Wetmore > >> Technical Writer-Editor > >> Infra > >> *Apache Software Foundation* > >> andr...@apache.org > >> > >> > >> < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > >> www.avast.com > >> < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > >> > <#m_6950646739042879479_m_4824096393059235209_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >> > > > > > > -- > > Andrew Wetmore > > Technical Writer-Editor > > Infra > > *Apache Software Foundation* > > andr...@apache.org > > > > > -- > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org >
Re: [Gora] builds.apache.org
Hi Damien/Alfonso, I just noticed the jenkins build system works just fine. Thank you for setting up builds again. :) Regards Kevin On Tue, Oct 27, 2020 at 5:27 AM Alfonso Nishikawa < alfonso.nishik...@gmail.com> wrote: > Hi, Damien. > > I really don't know anything about how to configure Jenkins, so everything > seems ok to me n_nU > > Thank you! > > Best regards, > > Alfonso Nishikawa > > El sáb., 24 oct. 2020 a las 21:15, Damien Raude-Morvan (< > draz...@drazzib.com>) > escribió: > > > Hi Kevin & Alfonso ! > > > > I've pretty good experience regarding creating Jenkinsfile for Java > > projects. I think this is the way to go for Gora. > > > > This approach is described on ASF wiki : Multibranch Pipeline recipes > > < > > > https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes > > > > > > > I've created a new issue (GORA-668 > > <https://issues.apache.org/jira/browse/GORA-668>) on this subject > > > > Regards, > > > > Le sam. 24 oct. 2020 à 14:46, Kevin Ratnasekera > > > a > > écrit : > > > > > Hi Alfonso, > > > > > > Apologize for taking time to respond to your email. Thank you for > taking > > > over this and creating the ticket. Let's see what we can do, once INFRA > > > responds back to the ticket. > > > > > > Regards > > > Kevin > > > > > > On Sat, Oct 24, 2020 at 5:45 PM Alfonso Nishikawa < > > > alfonso.nishik...@gmail.com> wrote: > > > > > > > Created: https://issues.apache.org/jira/browse/INFRA-21024 > > > > > > > > Now we just have to wait, and I believe we would have to create some > > jobs > > > > after? If I am not wrong, Infra does not create the jobs, but I hope > I > > am > > > > mistaken :) > > > > > > > > Best regards, > > > > > > > > Alfonso Nishikawa > > > > > > > > El sáb., 24 oct. 2020 a las 12:06, Alfonso Nishikawa (< > > > > alfonso.nishik...@gmail.com>) escribió: > > > > > > > > > Hi, Damien. > > > > > > > > > > Yes, I will create the ticket :) Let's see if I manage to get it > > done, > > > > > since I never wrote to Infra :) > > > > > > > > > > Thank you! > > > > > > > > > > Best regards, > > > > > > > > > > Alfonso Nishikawa > > > > > > > > > > El vie., 23 oct. 2020 a las 19:38, Damien Raude-Morvan (< > > > > > draz...@drazzib.com>) escribió: > > > > > > > > > >> Hi Alfonso! > > > > >> > > > > >> Gora builds used to be at > https://builds.apache.org/job/gora-trunk/ > > > > >> but it seems that the old Jenkins instance has been dropped... > > > > >> > > > > >> I've find a reference on this subject on build@ > > > > >> => [IMPORTANT] - Migration to ci-builds.a.o > > > > >> < > > > > >> > > > > > > > > > > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > > > > >> > > > > > >> > > > > >> Alfonso, if you have time, can you please a ticket in order to > > > re-create > > > > >> our job ? > > > > >> > > > > >> Best regards, > > > > >> > > > > >> Le jeu. 22 oct. 2020 à 18:35, Alfonso Nishikawa < > > > > >> alfonso.nishik...@gmail.com> > > > > >> a écrit : > > > > >> > > > > >> > Hi, pals. > > > > >> > > > > > >> > Can I ask Infra about getting Gora into builds.apache.org or > can > > > only > > > > >> be > > > > >> > done by the Chair? :) > > > > >> > Anyone has any insight about this? > > > > >> > > > > > >> > Thank you!! > > > > >> > > > > > >> > Regards, > > > > >> > > > > > >> > Alfonso Nishikawa > > > > >> > > > > > >> > El mar., 20 oct. 2020 a las 21:17, Alfonso Nishikawa (< > > > > >> > alfonso.nishik...@gmail.com>) escribió: > > > > >> > > > > > >> > > Hi! > > > > >> > > > > > > >> > > I took a look and I don't find our project in > builds.apache.org > > > to > > > > >> see > > > > >> > if > > > > >> > > it is building satisfactorily. I took a look because I am > > getting > > > a > > > > >> > > ClassCast error in gora-infinispan tests and wanted to see if > it > > > is > > > > a > > > > >> > > problem related to my computer or master. > > > > >> > > > > > > >> > > Can we see the status of success somewhere? I expected to see > it > > > in > > > > >> > > builds.apache.org > > > > >> > > Don we have to ask Infra? > > > > >> > > > > > > >> > > Thank you! :) > > > > >> > > > > > > >> > > Regards, > > > > >> > > > > > > >> > > Alfonso Nishikawa > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > >> -- > > > > >> Damien > > > > >> > > > > > > > > > > > > > > > > > > -- > > Damien > > >
Re: Can't assign issues in Jira
Hi Alfonso, I just checked your admin rights on JIRA, it seems you are assigned with admin permissions. I think it's required to add those people as gora contributors [1] before assigning them any JIRA ticket. [1] https://issues.apache.org/jira/plugins/servlet/project-config/GORA/roles Regards Kevin On Thu, Oct 29, 2020 at 1:35 AM Alfonso Nishikawa < alfonso.nishik...@gmail.com> wrote: > Hi! > > Does anyone knows why we can't assign issues to some people, though they > have an account in jira? When I try to assign the issue they don't show in > the list. I'm thinking about Gaby, Mariia and Nilo, that recently started > working on different issue. > > Best regards, > > Alfonso Nishikawa >
Re: [Gora] builds.apache.org
Hi Alfonso, Apologize for taking time to respond to your email. Thank you for taking over this and creating the ticket. Let's see what we can do, once INFRA responds back to the ticket. Regards Kevin On Sat, Oct 24, 2020 at 5:45 PM Alfonso Nishikawa < alfonso.nishik...@gmail.com> wrote: > Created: https://issues.apache.org/jira/browse/INFRA-21024 > > Now we just have to wait, and I believe we would have to create some jobs > after? If I am not wrong, Infra does not create the jobs, but I hope I am > mistaken :) > > Best regards, > > Alfonso Nishikawa > > El sáb., 24 oct. 2020 a las 12:06, Alfonso Nishikawa (< > alfonso.nishik...@gmail.com>) escribió: > > > Hi, Damien. > > > > Yes, I will create the ticket :) Let's see if I manage to get it done, > > since I never wrote to Infra :) > > > > Thank you! > > > > Best regards, > > > > Alfonso Nishikawa > > > > El vie., 23 oct. 2020 a las 19:38, Damien Raude-Morvan (< > > draz...@drazzib.com>) escribió: > > > >> Hi Alfonso! > >> > >> Gora builds used to be at https://builds.apache.org/job/gora-trunk/ > >> but it seems that the old Jenkins instance has been dropped... > >> > >> I've find a reference on this subject on build@ > >> => [IMPORTANT] - Migration to ci-builds.a.o > >> < > >> > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > >> > > >> > >> Alfonso, if you have time, can you please a ticket in order to re-create > >> our job ? > >> > >> Best regards, > >> > >> Le jeu. 22 oct. 2020 à 18:35, Alfonso Nishikawa < > >> alfonso.nishik...@gmail.com> > >> a écrit : > >> > >> > Hi, pals. > >> > > >> > Can I ask Infra about getting Gora into builds.apache.org or can only > >> be > >> > done by the Chair? :) > >> > Anyone has any insight about this? > >> > > >> > Thank you!! > >> > > >> > Regards, > >> > > >> > Alfonso Nishikawa > >> > > >> > El mar., 20 oct. 2020 a las 21:17, Alfonso Nishikawa (< > >> > alfonso.nishik...@gmail.com>) escribió: > >> > > >> > > Hi! > >> > > > >> > > I took a look and I don't find our project in builds.apache.org to > >> see > >> > if > >> > > it is building satisfactorily. I took a look because I am getting a > >> > > ClassCast error in gora-infinispan tests and wanted to see if it is > a > >> > > problem related to my computer or master. > >> > > > >> > > Can we see the status of success somewhere? I expected to see it in > >> > > builds.apache.org > >> > > Don we have to ask Infra? > >> > > > >> > > Thank you! :) > >> > > > >> > > Regards, > >> > > > >> > > Alfonso Nishikawa > >> > > > >> > > >> > >> > >> -- > >> Damien > >> > > >
Re: Congratulations to GSoC 2020 Students of Apache Gora
Hi Students, As per weekly reports and progress reported to me, you should have nearly completed your projects. Please make sure to send your final project PR as early as possible, get merged before the evaluation. Regards Kevin On Mon, Jul 27, 2020 at 5:39 PM Arne Nissen wrote: > Hi Kevin, > > I updated the wiki page. Sorry for the late. > > Thanks, > Arne > > On Fri, Jul 24, 2020 at 12:43 AM Kevin Ratnasekera < > djkevincr1...@gmail.com> wrote: > >> It seems ArangoDB and RethinkDB store projects are updated with weekly >> reports. >> >> @Arne Nissen Can you please update your >> reports with the progress you made? >> >> Regards >> Kevin >> >> >> On Thu, Jul 16, 2020 at 3:44 PM Furkan KAMACI >> wrote: >> >>> Hi GSoC Students, >>> >>> Since phase 2 evaluations will start on July 27, could you update your >>> reports on the wiki? >>> >>> Kind Regards, >>> Furkan KAMACI >>> >>> On Tue, Jun 30, 2020 at 4:08 PM Rumesh Perera >>> wrote: >>> >>> > Hi Kamaci and Kevin, >>> > >>> > I have update my weekly reports here : >>> > >>> https://cwiki.apache.org/confluence/display/GORA/RethinkDB+datastore+reports >>> > I have sent a PR : https://github.com/apache/gora/pull/219 on my >>> current >>> > working branch. Implementation is mostly complete >>> > except for query implementation. I will complete the rest of the >>> > implementation next coming weeks, and in parallel will also cover >>> > full coverage >>> > of the datastore base test cases. Currently it passes 12 test cases of >>> > datastore base test cases. >>> > >>> > Regards >>> > Rumesh >>> > >>> > On Tue, Jun 30, 2020 at 6:08 PM Arne Nissen >> > >>> > wrote: >>> > >>> >> Hi Kevin, >>> >> >>> >> I have updated the following as well. I will also send a pull request >>> ones >>> >> I finished testing CRUD operations with ScyllaDB. >>> >> >>> >> >>> >> >>> https://cwiki.apache.org/confluence/display/GORA/Scylladb+Datastore+reports >>> >> >>> >> >>> https://cwiki.apache.org/confluence/display/GORA/ScyllaDB+Datastore++Proposal >>> >> >>> >> https://github.com/arnenissen/gora/tree/GORA-657 >>> >> >>> >> Thanks, >>> >> Arne >>> >> >>> >> >>> >> >>> >> On Mon, Jun 29, 2020 at 9:48 AM Dinuka Perera < >>> ndinukaper...@gmail.com> >>> >> wrote: >>> >> >>> >> > Hi Furkan/Kevin, >>> >> > >>> >> > I have updated the following >>> >> > >>> >> > ArangoDB proposal : >>> >> > >>> >> > >>> >> >>> https://cwiki.apache.org/confluence/display/GORA/ArangoDB+Datastore+Proposal >>> >> > ArangoDB reports : >>> >> > >>> >> >>> https://cwiki.apache.org/confluence/display/GORA/Arango+datastore+reports >>> >> > ArangoDB Branch/PR : https://github.com/apache/gora/pull/218 >>> >> > >>> >> > Please review and let me know your feedback. >>> >> > >>> >> > Regards >>> >> > Dinuka >>> >> > >>> >> > On Mon, Jun 29, 2020 at 5:50 AM Kevin Ratnasekera < >>> >> djkevincr1...@gmail.com >>> >> > > >>> >> > wrote: >>> >> > >>> >> > > Hi Students, >>> >> > > >>> >> > > Apologize for the late reply. As I have reached out to you >>> offline, >>> >> > please >>> >> > > share your WIKI usernames. I will add you to Gora WIKI space. >>> >> > > >>> >> > > Regards >>> >> > > Kevin >>> >> > > >>> >> > > On Fri, Jun 26, 2020 at 1:42 AM Arne Nissen < >>> >> arnenissen70...@gmail.com> >>> >> > > wrote: >>> >> > > >>> >> > > > Hi Kevin, >>> >> > > > >>> >> > > > Can you provide me access to the wiki, please? >>> >> > >
Re: Github actions for Gora Github
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 >
Re: Congratulations to GSoC 2020 Students of Apache Gora
It seems ArangoDB and RethinkDB store projects are updated with weekly reports. @Arne Nissen Can you please update your reports with the progress you made? Regards Kevin On Thu, Jul 16, 2020 at 3:44 PM Furkan KAMACI wrote: > Hi GSoC Students, > > Since phase 2 evaluations will start on July 27, could you update your > reports on the wiki? > > Kind Regards, > Furkan KAMACI > > On Tue, Jun 30, 2020 at 4:08 PM Rumesh Perera > wrote: > > > Hi Kamaci and Kevin, > > > > I have update my weekly reports here : > > > https://cwiki.apache.org/confluence/display/GORA/RethinkDB+datastore+reports > > I have sent a PR : https://github.com/apache/gora/pull/219 on my current > > working branch. Implementation is mostly complete > > except for query implementation. I will complete the rest of the > > implementation next coming weeks, and in parallel will also cover > > full coverage > > of the datastore base test cases. Currently it passes 12 test cases of > > datastore base test cases. > > > > Regards > > Rumesh > > > > On Tue, Jun 30, 2020 at 6:08 PM Arne Nissen > > wrote: > > > >> Hi Kevin, > >> > >> I have updated the following as well. I will also send a pull request > ones > >> I finished testing CRUD operations with ScyllaDB. > >> > >> > >> > https://cwiki.apache.org/confluence/display/GORA/Scylladb+Datastore+reports > >> > >> > https://cwiki.apache.org/confluence/display/GORA/ScyllaDB+Datastore++Proposal > >> > >> https://github.com/arnenissen/gora/tree/GORA-657 > >> > >> Thanks, > >> Arne > >> > >> > >> > >> On Mon, Jun 29, 2020 at 9:48 AM Dinuka Perera > >> wrote: > >> > >> > Hi Furkan/Kevin, > >> > > >> > I have updated the following > >> > > >> > ArangoDB proposal : > >> > > >> > > >> > https://cwiki.apache.org/confluence/display/GORA/ArangoDB+Datastore+Proposal > >> > ArangoDB reports : > >> > > >> > https://cwiki.apache.org/confluence/display/GORA/Arango+datastore+reports > >> > ArangoDB Branch/PR : https://github.com/apache/gora/pull/218 > >> > > >> > Please review and let me know your feedback. > >> > > >> > Regards > >> > Dinuka > >> > > >> > On Mon, Jun 29, 2020 at 5:50 AM Kevin Ratnasekera < > >> djkevincr1...@gmail.com > >> > > > >> > wrote: > >> > > >> > > Hi Students, > >> > > > >> > > Apologize for the late reply. As I have reached out to you offline, > >> > please > >> > > share your WIKI usernames. I will add you to Gora WIKI space. > >> > > > >> > > Regards > >> > > Kevin > >> > > > >> > > On Fri, Jun 26, 2020 at 1:42 AM Arne Nissen < > >> arnenissen70...@gmail.com> > >> > > wrote: > >> > > > >> > > > Hi Kevin, > >> > > > > >> > > > Can you provide me access to the wiki, please? > >> > > > > >> > > > Thanks, > >> > > > Arne > >> > > > > >> > > > On Thu, Jun 25, 2020 at 9:01 PM Furkan KAMACI < > >> furkankam...@gmail.com> > >> > > > wrote: > >> > > > > >> > > >> Hi GSoC Students, > >> > > >> > >> > > >> First evaluations will start on June 29. So, please update the > Gora > >> > wiki > >> > > >> as > >> > > >> soon as possible and let us know if you have any questions. > >> > > >> > >> > > >> Kind Regards, > >> > > >> Furkan KAMACI > >> > > >> > >> > > >> On Sat, Jun 20, 2020 at 6:49 PM Furkan KAMACI < > >> furkankam...@gmail.com > >> > > > >> > > >> wrote: > >> > > >> > >> > > >> > Hi GSoC Students, > >> > > >> > > >> > > >> > Unfortunately, there is not 'any' report from students at the > >> wiki. > >> > > >> Please > >> > > >> > write your reports and upload proposals to the page I've > created > >> for > >> > > >> GSoC > >> > > >> > 2
Re: Congratulations to GSoC 2020 Students of Apache Gora
Hi Students, Apologize for the late reply. As I have reached out to you offline, please share your WIKI usernames. I will add you to Gora WIKI space. Regards Kevin On Fri, Jun 26, 2020 at 1:42 AM Arne Nissen wrote: > Hi Kevin, > > Can you provide me access to the wiki, please? > > Thanks, > Arne > > On Thu, Jun 25, 2020 at 9:01 PM Furkan KAMACI > wrote: > >> Hi GSoC Students, >> >> First evaluations will start on June 29. So, please update the Gora wiki >> as >> soon as possible and let us know if you have any questions. >> >> Kind Regards, >> Furkan KAMACI >> >> On Sat, Jun 20, 2020 at 6:49 PM Furkan KAMACI >> wrote: >> >> > Hi GSoC Students, >> > >> > Unfortunately, there is not 'any' report from students at the wiki. >> Please >> > write your reports and upload proposals to the page I've created for >> GSoC >> > 2020 [1]. Also, please check the previous reports from here [2] as I >> > mentioned before. >> > >> > The first evaluation period is between June 29 - July 3. I would like to >> > repeat the words that I've said: >> > >> > The first remarkable point of the successful GSoC projects is "keeping >> > communication" which is more important than you may think. >> > >> > Let us know if you have any questions. >> > >> > [1] https://cwiki.apache.org/confluence/display/GORA/GSoC+2020 >> > [2] >> https://cwiki.apache.org/confluence/display/GORA/Google+Summer+of+Code >> > >> > On Thu, May 28, 2020 at 12:58 AM Kevin Ratnasekera < >> > djkevincr1...@gmail.com> wrote: >> > >> >> Hi GSoC Students, >> >> >> >> There were several students who have been working with me fixing >> several >> >> JIRA tickets, please make sure you submit PRs and get them merged >> before >> >> community bonding. Also as mentioned by Kamaci, please make sure you >> add >> >> your proposal add to WIKI and please setup you weekly reporting pages >> >> before community bonding is completed. All communication from now >> onwards >> >> has to come into either public threads in gora dev list or WIKI >> reporting. >> >> >> >> Regards >> >> Kevin >> >> >> >> On Tue, May 26, 2020 at 4:56 AM Furkan KAMACI >> >> wrote: >> >> >> >> > Hi GSOC Students, >> >> > >> >> > The community bonding period will end on June 1, 2020. So, feel free >> to >> >> > pick up some warm-up issues and ask if you have any questions! >> >> > >> >> > Kind Regards, >> >> > Furkan KAMACI >> >> > >> >> > >> >> > On Sun, May 10, 2020 at 8:15 AM Dinuka Perera < >> ndinukaper...@gmail.com> >> >> > wrote: >> >> > >> >> > > Thank you all for accepting me. I am looking forward to work with >> you. >> >> > > >> >> > > On Sun, May 10, 2020 at 5:55 AM Arne Nissen < >> >> arnenissen70...@gmail.com> >> >> > > wrote: >> >> > > >> >> > > > Thank you very much. >> >> > > > >> >> > > > Regards, >> >> > > > Arne >> >> > > > >> >> > > > On Mon, May 4, 2020 at 11:21 PM Sheriffo Ceesay < >> >> sneceesa...@gmail.com >> >> > > >> >> > > > wrote: >> >> > > > >> >> > > > > Congratulations to all the Apache Gora GSoC Students! Hoping to >> >> see a >> >> > > > great >> >> > > > > contribution from you all. >> >> > > > > >> >> > > > > On Mon, 4 May 2020 at 22:05, Furkan KAMACI < >> >> furkankam...@gmail.com> >> >> > > > wrote: >> >> > > > > >> >> > > > > > Hi GSoC Students, >> >> > > > > > >> >> > > > > > Congrats you all! >> >> > > > > > >> >> > > > > > We are in the community bonding period until June 1. During >> this >> >> > > > period, >> >> > > > > > you should get to know your mentors, read documentation, get >> up >> >> to >> >> > > > speed >> >> > > > > to >> >> > > > > > begin working on your projects [1] >> >> > > > > > >> >> > > > > > Please check issues at Jira [2] to find tasks that you can >> work >> >> as >> >> > a >> >> > > > > > warm-up. On the other hand, please check previous reports >> from >> >> here >> >> > > [3] >> >> > > > > and >> >> > > > > > be ready to fill weekly progress reports there. >> >> > > > > > >> >> > > > > > The first remarkable point of the successful GSoC projects is >> >> > > "keeping >> >> > > > > > communication" which is most important than you may think. >> >> > > > > > >> >> > > > > > Let us know if you have any questions. I hope you have a >> great >> >> > > > experience >> >> > > > > > during your GSoC period! >> >> > > > > > >> >> > > > > > [1] >> >> > > > > > >> >> > > > > > >> >> > > > > >> >> > > > >> >> > > >> >> > >> >> >> http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html >> >> > > > > > [2] https://issues.apache.org/jira/projects/GORA/issues >> >> > > > > > [3] >> >> > > > > >> >> > >> https://cwiki.apache.org/confluence/display/GORA/Google+Summer+of+Code >> >> > > > > > >> >> > > > > > Kind Regards, >> >> > > > > > Furkan KAMACI >> >> > > > > > >> >> > > > > -- >> >> > > > > >> >> > > > > **Sheriffo Ceesay** >> >> > > > > >> >> > > > >> >> > > >> >> > >> >> >> > >> >
[jira] [Created] (GORA-661) Upgrade CouchDB module to the latest driver version
Kevin Ratnasekera created GORA-661: -- Summary: 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-660) Upgrade Hive module to the latest driver version
Kevin Ratnasekera created GORA-660: -- Summary: 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Congratulations to GSoC 2020 Students of Apache Gora
Hi GSoC Students, There were several students who have been working with me fixing several JIRA tickets, please make sure you submit PRs and get them merged before community bonding. Also as mentioned by Kamaci, please make sure you add your proposal add to WIKI and please setup you weekly reporting pages before community bonding is completed. All communication from now onwards has to come into either public threads in gora dev list or WIKI reporting. Regards Kevin On Tue, May 26, 2020 at 4:56 AM Furkan KAMACI wrote: > Hi GSOC Students, > > The community bonding period will end on June 1, 2020. So, feel free to > pick up some warm-up issues and ask if you have any questions! > > Kind Regards, > Furkan KAMACI > > > On Sun, May 10, 2020 at 8:15 AM Dinuka Perera > wrote: > > > Thank you all for accepting me. I am looking forward to work with you. > > > > On Sun, May 10, 2020 at 5:55 AM Arne Nissen > > wrote: > > > > > Thank you very much. > > > > > > Regards, > > > Arne > > > > > > On Mon, May 4, 2020 at 11:21 PM Sheriffo Ceesay > > > > wrote: > > > > > > > Congratulations to all the Apache Gora GSoC Students! Hoping to see a > > > great > > > > contribution from you all. > > > > > > > > On Mon, 4 May 2020 at 22:05, Furkan KAMACI > > > wrote: > > > > > > > > > Hi GSoC Students, > > > > > > > > > > Congrats you all! > > > > > > > > > > We are in the community bonding period until June 1. During this > > > period, > > > > > you should get to know your mentors, read documentation, get up to > > > speed > > > > to > > > > > begin working on your projects [1] > > > > > > > > > > Please check issues at Jira [2] to find tasks that you can work as > a > > > > > warm-up. On the other hand, please check previous reports from here > > [3] > > > > and > > > > > be ready to fill weekly progress reports there. > > > > > > > > > > The first remarkable point of the successful GSoC projects is > > "keeping > > > > > communication" which is most important than you may think. > > > > > > > > > > Let us know if you have any questions. I hope you have a great > > > experience > > > > > during your GSoC period! > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html > > > > > [2] https://issues.apache.org/jira/projects/GORA/issues > > > > > [3] > > > > > https://cwiki.apache.org/confluence/display/GORA/Google+Summer+of+Code > > > > > > > > > > Kind Regards, > > > > > Furkan KAMACI > > > > > > > > > -- > > > > > > > > **Sheriffo Ceesay** > > > > > > > > > >
[jira] [Updated] (GORA-656) Hazelcast IMap backed datastore
[ https://issues.apache.org/jira/browse/GORA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-656: --- Labels: gsoc2020 (was: ) > Hazelcast IMap backed datastore > --- > > Key: GORA-656 > URL: https://issues.apache.org/jira/browse/GORA-656 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2020 > > Current implementation of JCache datastore is written in a way that it will > work with any JCache provider. Even though we have made explicitly available > Hazelcast JCache provider to the classpath. This implementation should be > based on the native interfaces of IMap. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-656) Hazelcast IMap backed datastore
Kevin Ratnasekera created GORA-656: -- Summary: Hazelcast IMap backed datastore Key: GORA-656 URL: https://issues.apache.org/jira/browse/GORA-656 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera Current implementation of JCache datastore is written in a way that it will work with any JCache provider. Even though we have made explicitly available Hazelcast JCache provider to the classpath. This implementation should be based on the native interfaces of IMap. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-655) Implement RethinkDB datastore module
[ https://issues.apache.org/jira/browse/GORA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-655: --- Labels: gsoc2020 (was: ) > Implement RethinkDB datastore module > - > > Key: GORA-655 > URL: https://issues.apache.org/jira/browse/GORA-655 > Project: Apache Gora > Issue Type: Improvement > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2020 > > Technical comparison to MongoDB is available. [1] > [1] https://rethinkdb.com/docs/comparison-tables/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-653) Upgrade Solr datastore to the latest java driver
[ https://issues.apache.org/jira/browse/GORA-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-653: --- Summary: Upgrade Solr datastore to the latest java driver (was: Upgrade Solr datastore client to the latest java driver) > 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 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-654) Upgrade Lucene datastore to the latest java driver
Kevin Ratnasekera created GORA-654: -- Summary: 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-653) Upgrade Solr datastore client to the latest java driver
[ https://issues.apache.org/jira/browse/GORA-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-653: --- Summary: Upgrade Solr datastore client to the latest java driver (was: Upgrade Solr datastore client to the latest) > Upgrade Solr datastore client 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 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-650: --- Labels: gsoc2020 (was: ) > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.9 > Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2020 > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-651) Upgrade OrientDB to the latest version 3
Kevin Ratnasekera created GORA-651: -- Summary: Upgrade OrientDB to the latest version 3 Key: GORA-651 URL: https://issues.apache.org/jira/browse/GORA-651 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera It seem version 3 based releases [1] have been there for a while, we should upgrade from 2.2.22. [1] https://orientdb.com/releases/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-86) Support JOOQ API within gora-sql module
[ https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065983#comment-17065983 ] Kevin Ratnasekera commented on GORA-86: --- [~balaShashanka] Please let us know if you need any further help on this. > Support JOOQ API within gora-sql module > > > Key: GORA-86 > URL: https://issues.apache.org/jira/browse/GORA-86 > Project: Apache Gora > Issue Type: Improvement > Components: gora-sql >Affects Versions: 0.2 >Reporter: Lewis John McGibbney >Priority: Major > Labels: gsoc2014, gsoc2016, mentor > Fix For: 1.0 > > Attachments: gsoc_proposal.docx > > > We've discussed this recently and Lukas Eder has been helpful enough to > provide an his opinion, which acts as an overview from a different > perspective, on whether JOOQ is appropriate for Gora. > This issue should act as a separate but linked issue to GORA-74, and we > should discuss what happens to the SQL type code that we maintain within > Gora. As this module is not being utilised very much just now there is really > no overwhelming argument yet to adopt JOOQ, however hopefully we can iron > this out within the correspondence. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-561) Update MongoDB java driver to the latest 3.10.1 version
[ https://issues.apache.org/jira/browse/GORA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065981#comment-17065981 ] Kevin Ratnasekera commented on GORA-561: [~madhawa] [~drazzib] Can we close ticket with recent upgrade to MongoDB datastore? > Update MongoDB java driver to the latest 3.10.1 version > --- > > Key: GORA-561 > URL: https://issues.apache.org/jira/browse/GORA-561 > Project: Apache Gora > Issue Type: Improvement > Components: gora-mongodb >Reporter: Madhawa Kasun Gunasekara >Priority: Major > > current version 3.5.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GORA-639) Add new YCSB dependency for gora-benchmark module
[ https://issues.apache.org/jira/browse/GORA-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-639. Resolution: Fixed > Add new YCSB dependency for gora-benchmark module > - > > Key: GORA-639 > URL: https://issues.apache.org/jira/browse/GORA-639 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Affects Versions: 0.9 >Reporter: Sheriffo Ceesay >Assignee: Sheriffo Ceesay >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > YCSB is the main dependency of gora-benchmark module. At the time of the > implementation of the module, the dependency wasn't published to maven > central. This issue was reported to the maintainers and it is now fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-650) Add datastore for ArangoDB
[ https://issues.apache.org/jira/browse/GORA-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-650: --- Issue Type: New Feature (was: Improvement) > Add datastore for ArangoDB > -- > > Key: GORA-650 > URL: https://issues.apache.org/jira/browse/GORA-650 > Project: Apache Gora > Issue Type: New Feature > Reporter: Kevin Ratnasekera >Priority: Major > > May be we should consider extending our multimodal datastore support with > ArangoDB. [1] > [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-650) Add datastore for ArangoDB
Kevin Ratnasekera created GORA-650: -- Summary: Add datastore for ArangoDB Key: GORA-650 URL: https://issues.apache.org/jira/browse/GORA-650 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera May be we should consider extending our multimodal datastore support with ArangoDB. [1] [1] https://www.arangodb.com/why-arangodb/multi-model/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
