[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(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' >
[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.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
[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
[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)
[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)
[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)
[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)
[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)
[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: --- Affects Version/s: 0.9 > 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 > > 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-648) Improve MapReduceTestUtils to have Hazelcast Jet Workloads
Kevin Ratnasekera created GORA-648: -- Summary: Improve MapReduceTestUtils to have Hazelcast Jet Workloads Key: GORA-648 URL: https://issues.apache.org/jira/browse/GORA-648 Project: Apache Gora Issue Type: Improvement Reporter: Kevin Ratnasekera Current we have workloads for Map Reduce, Spark, Flink in MapReduceTestUtils, these are executed at datastore tests. We need to further extend this to include Hazelcast Jet workloads. So that we can include tests for any datastore to have workloads on Hazelcast Jet Engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-648) Improve MapReduceTestUtils to have Hazelcast Jet Workloads
[ https://issues.apache.org/jira/browse/GORA-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-648: --- Affects Version/s: 0.9 > Improve MapReduceTestUtils to have Hazelcast Jet Workloads > -- > > Key: GORA-648 > URL: https://issues.apache.org/jira/browse/GORA-648 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.9 >Reporter: Kevin Ratnasekera >Priority: Major > > Current we have workloads for Map Reduce, Spark, Flink in MapReduceTestUtils, > these are executed at datastore tests. We need to further extend this to > include Hazelcast Jet workloads. So that we can include tests for any > datastore to have workloads on Hazelcast Jet Engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-546: --- Component/s: gora-jet > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature > Components: gora-jet >Affects Versions: 0.9 >Reporter: Kevin Ratnasekera >Assignee: Lahiru Jayasekara >Priority: Major > Labels: gsoc2019 > Fix For: 1.0 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-546. Resolution: Fixed > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature > Components: gora-jet >Affects Versions: 0.9 >Reporter: Kevin Ratnasekera >Assignee: Lahiru Jayasekara >Priority: Major > Labels: gsoc2019 > Fix For: 1.0 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-546: -- Assignee: Lahiru Jayasekara > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Assignee: Lahiru Jayasekara >Priority: Major > Labels: gsoc2019 > Time Spent: 8h 10m > Remaining Estimate: 0h > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-546: --- Fix Version/s: 1.0 > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Assignee: Lahiru Jayasekara >Priority: Major > Labels: gsoc2019 > Fix For: 1.0 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- 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=17060647#comment-17060647 ] Kevin Ratnasekera commented on GORA-86: --- [~balaShashanka] Do you have any update 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] [Resolved] (GORA-645) Upgrade MongoDB Driver version to 3.12.x
[ https://issues.apache.org/jira/browse/GORA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-645. Resolution: Fixed > Upgrade MongoDB Driver version to 3.12.x > > > Key: GORA-645 > URL: https://issues.apache.org/jira/browse/GORA-645 > Project: Apache Gora > Issue Type: Task >Affects Versions: 0.9 >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Major > Fix For: 1.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-645) Upgrade MongoDB Driver version to 3.12.x
[ https://issues.apache.org/jira/browse/GORA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-645: --- Affects Version/s: (was: 09) 0.9 > Upgrade MongoDB Driver version to 3.12.x > > > Key: GORA-645 > URL: https://issues.apache.org/jira/browse/GORA-645 > Project: Apache Gora > Issue Type: Task >Affects Versions: 0.9 >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Major > Fix For: 1.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-645) Upgrade MongoDB Driver version to 3.12.x
[ https://issues.apache.org/jira/browse/GORA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-645: --- Fix Version/s: 1.0 > Upgrade MongoDB Driver version to 3.12.x > > > Key: GORA-645 > URL: https://issues.apache.org/jira/browse/GORA-645 > Project: Apache Gora > Issue Type: Task >Affects Versions: 09 >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Major > Fix For: 1.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-645) Upgrade MongoDB Driver version to 3.12.x
[ https://issues.apache.org/jira/browse/GORA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-645: --- Affects Version/s: 09 > Upgrade MongoDB Driver version to 3.12.x > > > Key: GORA-645 > URL: https://issues.apache.org/jira/browse/GORA-645 > Project: Apache Gora > Issue Type: Task >Affects Versions: 09 >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GORA-645) Upgrade MongoDB Driver version to 3.12.x
[ https://issues.apache.org/jira/browse/GORA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-645: -- Assignee: Madhawa Kasun Gunasekara > Upgrade MongoDB Driver version to 3.12.x > > > Key: GORA-645 > URL: https://issues.apache.org/jira/browse/GORA-645 > Project: Apache Gora > Issue Type: Task >Reporter: Madhawa Kasun Gunasekara >Assignee: Madhawa Kasun Gunasekara >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-271: --- Component/s: gora-hbase gora-dynamodb > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement > Components: gora-dynamodb, gora-hbase >Affects Versions: 0.3, 0.9 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera updated GORA-271: --- Affects Version/s: 0.9 > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.3, 0.9 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GORA-271) Make consistent across datastores the way of getting the mapping filename
[ https://issues.apache.org/jira/browse/GORA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera reassigned GORA-271: -- Assignee: Lahiru Jayasekara (was: Apostolos Giannakidis) > Make consistent across datastores the way of getting the mapping filename > - > > Key: GORA-271 > URL: https://issues.apache.org/jira/browse/GORA-271 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.3 >Reporter: Apostolos Giannakidis >Assignee: Lahiru Jayasekara >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > While working on GORA-231, I identified several datastores that do not use > the DataStoreFactory.getMappingFile() to retrieve the filename for the > mapping file from the properties file. These datastores are the following: > * gora-cassandra > * gora-dynamodb > * gora-hbase > I believe that this change will be a step forward towards having datastores > consistent to each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GORA-638) Add gora-ignite into the gora-tutorial module
[ https://issues.apache.org/jira/browse/GORA-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Ratnasekera resolved GORA-638. Resolution: Fixed > Add gora-ignite into the gora-tutorial module > - > > Key: GORA-638 > URL: https://issues.apache.org/jira/browse/GORA-638 > Project: Apache Gora > Issue Type: New Feature > Components: gora-tutorial >Affects Versions: 0.9 >Reporter: José Ortiz >Assignee: José Ortiz >Priority: Minor > Fix For: 1.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Hi folks. > I am José Ortiz, a research assistant at CEDIA, and I have been testing some > big data frameworks as part of my current job. I tried to go through the Gora > tutorial [1] using Apache Ignite, but I found out that Ignite is not > supported yet. > > [1] https://gora.apache.org/current/tutorial.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
