[jira] [Resolved] (GORA-714) FTBFS: Conjars.org repository is dead
[
https://issues.apache.org/jira/browse/GORA-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan resolved GORA-714.
--
Fix Version/s: 1.0
Resolution: Fixed
{{build}} and {{deploy}} steps are now fixed
[https://ci-builds.apache.org/job/Gora/job/gora-pipeline/job/master/45/]
Tests fails with an OutOfMemory error (will look into it)
> FTBFS: Conjars.org repository is dead
> -
>
> Key: GORA-714
> URL: https://issues.apache.org/jira/browse/GORA-714
> Project: Apache Gora
> Issue Type: Bug
> Components: maven
>Affects Versions: 1.0
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Fix For: 1.0
>
>
> AFAICT, the maven repository previously at conjars.org has been removed (see
> [1])
> Since Apache Gora {{pom.xml}} reference this repo, it currently fails to
> builds from source
> {code:java}
>
> conjars
> https://conjars.org/repo
>
> {code}
> {quote}This repos has been added with the following commit
> [https://github.com/apache/gora/commit/22d3af831dbd279151a55f610a747859fc20c74e]
> {quote}
> h5. Proposed change
> It seems we don't have *direct usage* for any conjars related, I will try to
> track we have added this repository and suggest to remove this reference.
> h5. Reference informations
> * [1] [https://groups.google.com/g/cascading-user/c/qAQvajapawI]
> * [2] [https://conjars.wensel.net/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (GORA-692) Upgrade MongoDB datastore driver to latest 3.12.10
[ https://issues.apache.org/jira/browse/GORA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan resolved GORA-692. -- Assignee: Trisha Melani Resolution: Fixed I'm marking this issue as _resolved_ (merged last year !) > Upgrade MongoDB datastore driver to latest 3.12.10 > -- > > Key: GORA-692 > URL: https://issues.apache.org/jira/browse/GORA-692 > Project: Apache Gora > Issue Type: Improvement > Components: gora-mongodb >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] [Commented] (GORA-714) FTBFS: Conjars.org repository is dead
[
https://issues.apache.org/jira/browse/GORA-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753820#comment-17753820
]
Damien Raude-Morvan commented on GORA-714:
--
It seems Drill project had the same issue
# DRILL-8418
> FTBFS: Conjars.org repository is dead
> -
>
> Key: GORA-714
> URL: https://issues.apache.org/jira/browse/GORA-714
> Project: Apache Gora
> Issue Type: Bug
> Components: maven
>Affects Versions: 1.0
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
>
> AFAICT, the maven repository previously at conjars.org has been removed (see
> [1])
> Since Apache Gora {{pom.xml}} reference this repo, it currently fails to
> builds from source
> {code:java}
>
> conjars
> https://conjars.org/repo
>
> {code}
> {quote}This repos has been added with the following commit
> [https://github.com/apache/gora/commit/22d3af831dbd279151a55f610a747859fc20c74e]
> {quote}
> h5. Proposed change
> It seems we don't have *direct usage* for any conjars related, I will try to
> track we have added this repository and suggest to remove this reference.
> h5. Reference informations
> * [1] [https://groups.google.com/g/cascading-user/c/qAQvajapawI]
> * [2] [https://conjars.wensel.net/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (GORA-714) FTBFS: Conjars.org repository is dead
Damien Raude-Morvan created GORA-714:
Summary: FTBFS: Conjars.org repository is dead
Key: GORA-714
URL: https://issues.apache.org/jira/browse/GORA-714
Project: Apache Gora
Issue Type: Bug
Components: maven
Affects Versions: 1.0
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
AFAICT, the maven repository previously at conjars.org has been removed (see
[1])
Since Apache Gora {{pom.xml}} reference this repo, it currently fails to builds
from source
{code:java}
conjars
https://conjars.org/repo
{code}
{quote}This repos has been added with the following commit
[https://github.com/apache/gora/commit/22d3af831dbd279151a55f610a747859fc20c74e]
{quote}
h5. Proposed change
It seems we don't have *direct usage* for any conjars related, I will try to
track we have added this repository and suggest to remove this reference.
h5. Reference informations
* [1] [https://groups.google.com/g/cascading-user/c/qAQvajapawI]
* [2] [https://conjars.wensel.net/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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=17341303#comment-17341303
]
Damien Raude-Morvan commented on GORA-679:
--
CC from my comment on
[https://github.com/apache/gora/pull/242#issuecomment-835225855
:)|https://github.com/apache/gora/pull/242#issuecomment-835225855]
{quote}Hi @djkevincr !
I've tracked down this FTBFS issue and came to the same conclusion : it's
linked to a behavior change in lastest Maven 3.8.1 (described in
[CVE-2021-26291 section of release
notes](https://maven.apache.org/docs/3.8.1/release-notes.html)).
@djkevincr Could you please push your _djkevincr:GORA-679-2_ branch on official
Apache git repository so that it gets build with our [Jenkins
pipeline](https://ci-builds.apache.org/blue/organizations/jenkins/Gora%2Fgora-pipeline/branches).
It seems much more stable than Github Action to check for build success :)
{quote}
> 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
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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] [Commented] (GORA-674) Failure of testcontainers-java on recent Docker runtime
[
https://issues.apache.org/jira/browse/GORA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319713#comment-17319713
]
Damien Raude-Morvan commented on GORA-674:
--
hi [~minfaz] !
Apache Gora integrations tests seems to be running fine (since my last fixes on
master) either on my own box, in
[Jenkins|https://ci-builds.apache.org/job/Gora/job/gora-pipeline/job/master/21/testReport/]
or in [Github Actions|https://github.com/apache/gora/runs/2314348597]
Could you please provide a more detailled stacktrace ? Is it still "Can't get
Docker image:" error ? Please open a new GORA issue if needed.
Thanks !
> Failure of testcontainers-java on recent Docker runtime
> ---
>
> Key: GORA-674
> URL: https://issues.apache.org/jira/browse/GORA-674
> Project: Apache Gora
> Issue Type: Bug
> Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: docker, testcontainers
> Fix For: 1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As reported by [~alfonso.nishikawa]
> Right now I see that CouchDB fails
> {code:java}
> org.apache.gora.couchdb.store.TestCouchDBStore.org.apache.gora.couchdb.store.TestCouchDBStore
>
> Can't get Docker image: RemoteDockerImage(imageName=couchdb:1.6.1,
> imagePullPolicy=DefaultPullPolicy())
> Caused by: com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: testcontainersofficial/ryuk:0.3.0"}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-674) Failure of testcontainers-java on recent Docker runtime
[
https://issues.apache.org/jira/browse/GORA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318590#comment-17318590
]
Damien Raude-Morvan commented on GORA-674:
--
[~minfaz] Ok thanks !
Just to confirm your tests, [commit
b0cc476550e12396030e5c819d5556f050e3db38|https://github.com/testcontainers/testcontainers-java/commit/b0cc476550e12396030e5c819d5556f050e3db38]
in testcontainers-java - which fix issue we were discussing - is only included
since *1.15.1* release and is not in *1.15.0*
I've just merged [PR 236|https://github.com/apache/gora/pull/236] into master
to fix our build/tests
> Failure of testcontainers-java on recent Docker runtime
> ---
>
> Key: GORA-674
> URL: https://issues.apache.org/jira/browse/GORA-674
> Project: Apache Gora
> Issue Type: Bug
> Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: docker, testcontainers
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As reported by [~alfonso.nishikawa]
> Right now I see that CouchDB fails
> {code:java}
> org.apache.gora.couchdb.store.TestCouchDBStore.org.apache.gora.couchdb.store.TestCouchDBStore
>
> Can't get Docker image: RemoteDockerImage(imageName=couchdb:1.6.1,
> imagePullPolicy=DefaultPullPolicy())
> Caused by: com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: testcontainersofficial/ryuk:0.3.0"}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-675) Perform Sonar static code analysis on Jenkins
[ https://issues.apache.org/jira/browse/GORA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313876#comment-17313876 ] Damien Raude-Morvan commented on GORA-675: -- Waiting for INFRA to setup repository > Perform Sonar static code analysis on Jenkins > - > > Key: GORA-675 > URL: https://issues.apache.org/jira/browse/GORA-675 > Project: Apache Gora > Issue Type: Task > Components: build process >Reporter: Damien Raude-Morvan >Assignee: Damien Raude-Morvan >Priority: Minor > > I would like to use [https://sonarcloud.io/] in order to perform static code > analysis on Apache Gora project. > This analysis should be automatically triggered on our Jenkins job as > described on > https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-675) Perform Sonar static code analysis on Jenkins
Damien Raude-Morvan created GORA-675: Summary: Perform Sonar static code analysis on Jenkins Key: GORA-675 URL: https://issues.apache.org/jira/browse/GORA-675 Project: Apache Gora Issue Type: Task Components: build process Reporter: Damien Raude-Morvan Assignee: Damien Raude-Morvan I would like to use [https://sonarcloud.io/] in order to perform static code analysis on Apache Gora project. This analysis should be automatically triggered on our Jenkins job as described on https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-674) Failure of testcontainers-java on recent Docker runtime
[
https://issues.apache.org/jira/browse/GORA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310084#comment-17310084
]
Damien Raude-Morvan commented on GORA-674:
--
It seems to be linked to a recent change on Docker Runtime API (local Docker
installation) which to seems to be unsupported by *testcontainers 1.14* that we
currently use everywhere in our test.
[https://github.com/testcontainers/testcontainers-java/issues/3574]
{quote}Ok, "filter by image name" query parameter in {{/images/json}} got
removed on Docker's API.
Although the query param was deprecated (I wish we could run Docker in a strict
API mode - will explore)
Sorry for this. We will release a hotfix ASAP. Meanwhile, consider pre-pulling
{{testcontainers/ryuk:0.3.0}} and {{alpine:3.5}} :(
{quote}
I will take care of this upgrade to testcontainers 1.15
> Failure of testcontainers-java on recent Docker runtime
> ---
>
> Key: GORA-674
> URL: https://issues.apache.org/jira/browse/GORA-674
> Project: Apache Gora
> Issue Type: Bug
> Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: docker, testcontainers
>
> As reported by [~alfonso.nishikawa]
> Right now I see that CouchDB fails
> {code:java}
> org.apache.gora.couchdb.store.TestCouchDBStore.org.apache.gora.couchdb.store.TestCouchDBStore
>
> Can't get Docker image: RemoteDockerImage(imageName=couchdb:1.6.1,
> imagePullPolicy=DefaultPullPolicy())
> Caused by: com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: testcontainersofficial/ryuk:0.3.0"}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GORA-674) Failure of testcontainers-java on recent Docker runtime
Damien Raude-Morvan created GORA-674:
Summary: Failure of testcontainers-java on recent Docker runtime
Key: GORA-674
URL: https://issues.apache.org/jira/browse/GORA-674
Project: Apache Gora
Issue Type: Bug
Components: build process
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
As reported by [~alfonso.nishikawa]
Right now I see that CouchDB fails
{code:java}
org.apache.gora.couchdb.store.TestCouchDBStore.org.apache.gora.couchdb.store.TestCouchDBStore
Can't get Docker image: RemoteDockerImage(imageName=couchdb:1.6.1,
imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.NotFoundException:
{"message":"No such image: testcontainersofficial/ryuk:0.3.0"}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
[
https://issues.apache.org/jira/browse/GORA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224206#comment-17224206
]
Damien Raude-Morvan commented on GORA-669:
--
Yes, I've identified a similar problem on another job (see INFRA-21058).
FYI, I'm working on improving job stability in
{{GORA-669-improve-tests-stability}} branch
> MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
> --
>
> Key: GORA-669
> URL: https://issues.apache.org/jira/browse/GORA-669
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-mongodb
>Affects Versions: 1.0
>Reporter: Alfonso Nishikawa
>Assignee: Damien Raude-Morvan
>Priority: Critical
> Attachments: image-2020-10-30-22-40-24-419.png
>
>
> It happens in the [Jenkins
> build|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/3/console]
> and it happens to myself in local.
> When the test tries to launch the container it just keeps waiting forever for
> no reason.
> After a millennia, it just fails (I guess timeout), like in [build
> #2|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/2/testReport/].
> !image-2020-10-30-22-40-24-419.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
[ https://issues.apache.org/jira/browse/GORA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224171#comment-17224171 ] Damien Raude-Morvan commented on GORA-669: -- [~alfonso.nishikawa] After all, this issue seems to be reproducible on Jenkins (check latest builds on [build.apache.org|https://ci-builds.apache.org/job/Gora/job/gora-pipeline/job/master/]) (on) I have to find a way to reproduce that locally... > MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending > -- > > Key: GORA-669 > URL: https://issues.apache.org/jira/browse/GORA-669 > Project: Apache Gora > Issue Type: Bug > Components: gora-mongodb >Affects Versions: 1.0 >Reporter: Alfonso Nishikawa >Assignee: Damien Raude-Morvan >Priority: Critical > Attachments: image-2020-10-30-22-40-24-419.png > > > It happens in the [Jenkins > build|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/3/console] > and it happens to myself in local. > When the test tries to launch the container it just keeps waiting forever for > no reason. > After a millennia, it just fails (I guess timeout), like in [build > #2|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/2/testReport/]. > !image-2020-10-30-22-40-24-419.png|thumbnail! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
[
https://issues.apache.org/jira/browse/GORA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224090#comment-17224090
]
Damien Raude-Morvan commented on GORA-669:
--
Hi [~alfonso.nishikawa] !
I'm unable to reproduce (locally) this timeout on
{{SCRAM_SHA_1_AuthenticationTest}} in MongoDB test suite.
Our [Jenkins
job|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/] seems
fine since build #4 but I don't see any related changes on MongoDB test suite.
Could you please perform a new local test suite execution and capture a JVM
thread dump once build is stuck ?
> MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
> --
>
> Key: GORA-669
> URL: https://issues.apache.org/jira/browse/GORA-669
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-mongodb
>Affects Versions: 1.0
>Reporter: Alfonso Nishikawa
>Assignee: Damien Raude-Morvan
>Priority: Critical
> Attachments: image-2020-10-30-22-40-24-419.png
>
>
> It happens in the [Jenkins
> build|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/3/console]
> and it happens to myself in local.
> When the test tries to launch the container it just keeps waiting forever for
> no reason.
> After a millennia, it just fails (I guess timeout), like in [build
> #2|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/2/testReport/].
> !image-2020-10-30-22-40-24-419.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending
[ https://issues.apache.org/jira/browse/GORA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan reassigned GORA-669: Assignee: Damien Raude-Morvan > MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending > -- > > Key: GORA-669 > URL: https://issues.apache.org/jira/browse/GORA-669 > Project: Apache Gora > Issue Type: Bug > Components: gora-mongodb >Affects Versions: 1.0 >Reporter: Alfonso Nishikawa >Assignee: Damien Raude-Morvan >Priority: Critical > Attachments: image-2020-10-30-22-40-24-419.png > > > It happens in the [Jenkins > build|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/3/console] > and it happens to myself in local. > When the test tries to launch the container it just keeps waiting forever for > no reason. > After a millennia, it just fails (I guess timeout), like in [build > #2|https://builds.apache.org/job/Gora/job/gora-pipeline/job/master/2/testReport/]. > !image-2020-10-30-22-40-24-419.png|thumbnail! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GORA-668) Create a Jenkinsfile for Multibranch Pipeline
[
https://issues.apache.org/jira/browse/GORA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17220694#comment-17220694
]
Damien Raude-Morvan commented on GORA-668:
--
Here is my [PR-229|https://github.com/apache/gora/pull/229] for a
[Jenkinsfile|https://www.jenkins.io/doc/book/pipeline/jenkinsfile/] for Apache
Gora.
h3. Add Jenkinsfile
There is two stages in this pipeline:
* *Build* which trigger {{mvn clean install}} targets
* *Test* which trigger {{mvn verify}} and transform any failure as UNSTABLE
status for Jenkins job
h3. Improve tests stability
I've also improved _Aerospike_ and _RethinkDB_ tests.
I'm using [container's ip address returned by
_testcontainer_|https://www.testcontainers.org/features/networking/#getting-the-container-host]
instead of {{localhost}} to support use case where Jenkins is running inside
Docker (aka Docker in Docker)
> Create a Jenkinsfile for Multibranch Pipeline
> -
>
> Key: GORA-668
> URL: https://issues.apache.org/jira/browse/GORA-668
> Project: Apache Gora
> Issue Type: Task
> Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to provide an easy way to setup our builds on Jenkins (aka
> ci-builds.apache.org)
> I would like to commit a {{Jenskinsfile}} in our repository as described in
> [Multibranch Pipeline
> recipes|https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GORA-668) Create a Jenkinsfile for Multibranch Pipeline
[
https://issues.apache.org/jira/browse/GORA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-668:
-
Description:
In order to provide an easy way to setup our builds on Jenkins (aka
ci-builds.apache.org)
I would like to commit a {{Jenskinsfile}} in our repository as described in
[Multibranch Pipeline
recipes|https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes]
> Create a Jenkinsfile for Multibranch Pipeline
> -
>
> Key: GORA-668
> URL: https://issues.apache.org/jira/browse/GORA-668
> Project: Apache Gora
> Issue Type: Task
> Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Minor
>
> In order to provide an easy way to setup our builds on Jenkins (aka
> ci-builds.apache.org)
> I would like to commit a {{Jenskinsfile}} in our repository as described in
> [Multibranch Pipeline
> recipes|https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GORA-668) Create a Jenkinsfile for Multibranch Pipeline
Damien Raude-Morvan created GORA-668: Summary: Create a Jenkinsfile for Multibranch Pipeline Key: GORA-668 URL: https://issues.apache.org/jira/browse/GORA-668 Project: Apache Gora Issue Type: Task Components: build process Reporter: Damien Raude-Morvan Assignee: Damien Raude-Morvan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GORA-652) Enable tests by default for redis/couchdb/aerospike datastore
Damien Raude-Morvan created GORA-652:
Summary: Enable tests by default for redis/couchdb/aerospike
datastore
Key: GORA-652
URL: https://issues.apache.org/jira/browse/GORA-652
Project: Apache Gora
Issue Type: Test
Components: gora-aerospike, gora-redis
Affects Versions: 0.9
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
Following my work on GORA-647 (using _testcontainers_ on {{gora-mongodb}}
datastore), I've spotted that at least 3 others gora datastore also use
_testcontainers_.
AFAIK, those modules are :
* gora-aerospike
* gora-couchdb
* gore-redis
I would like to enable tests _*by default*_ on those modules and remove actual
Maven profile(s) needed for now: {{aerospike-with-test}},
{{couchdb-with-test}}, {{redis-with-test}}
IMHO, tests should always be enabled by default during local or CI build of the
GORA's datastore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GORA-647) Use Testcontainers for MongoDB integration tests
[
https://issues.apache.org/jira/browse/GORA-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan resolved GORA-647.
--
Fix Version/s: 1.0
Resolution: Fixed
> Use Testcontainers for MongoDB integration tests
>
>
> Key: GORA-647
> URL: https://issues.apache.org/jira/browse/GORA-647
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Fix For: 1.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It seems that
> [flapdoodle.embed.mongo|https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo]
> artifact actually used for {{gora-mongodb}} integration tests is a bit
> outdated (ie. no support for latest MongoDB 4.2) and have no new commits
> since at least 6 months.
> I would like to align {{gora-mongodb}} integration tests with other Gora
> modules so that we also use [testcontainers|https://www.testcontainers.org/]
> which seems to provide more easier to maintain code (for instance,
> [mongo|https://hub.docker.com/_/mongo] docker container provide
> authentication support!)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GORA-649) Replace usage of deprecated API of MongoDB driver
[
https://issues.apache.org/jira/browse/GORA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan resolved GORA-649.
--
Fix Version/s: 1.0
Resolution: Fixed
> Replace usage of deprecated API of MongoDB driver
> -
>
> Key: GORA-649
> URL: https://issues.apache.org/jira/browse/GORA-649
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-mongodb
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: patch
> Fix For: 1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After upgrade to 3.12 release of {{mongo-java-driver}} (in GORA-645), I've
> identified that we use some deprecated methods. Those methods will be removed
> in next (4.x) release of {{mongo-java-driver}}.
> Here is extract of warnings printed by javac :
> {code:java}
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[75,18]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[80,18]
> [deprecation] Mongo in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[210,11]
> [deprecation]
> MongoClient(List,List,MongoClientOptions) in
> MongoClient has been deprecated
> [WARNING] 15] [deprecation] MONGODB_CR in AuthenticationMechanism has been
> deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[230,34]
> [deprecation] createMongoCRCredential(String,String,char[]) in
> MongoCredential has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[249,54]
> [deprecation] getDB(String) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[292,67]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[313,69]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[338,14]
> [deprecation] fsync(boolean) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,23]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,12]
> [deprecation] addOption(int) in DBCursor has been deprecated{code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (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:all-tabpanel
]
Damien Raude-Morvan resolved GORA-561.
--
Fix Version/s: 1.0
Resolution: Invalid
[~djkevincr] Good catch !
Since we are using {{mongo-java-driver}} 3.12 release, I'm closing this issue
as {{Invalid}} (superceded by GORA-645)
> 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
> Fix For: 1.0
>
>
> current version 3.5.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Damien Raude-Morvan updated GORA-561: - Fix Version/s: (was: 1.0) > 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] [Commented] (GORA-649) Replace usage of deprecated API of MongoDB driver
[
https://issues.apache.org/jira/browse/GORA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065210#comment-17065210
]
Damien Raude-Morvan commented on GORA-649:
--
[https://github.com/apache/gora/pull/207]
* Use new {{MongoDatabase}} and {{MongoCollection}} API as described on
[Databases and
Collections|http://mongodb.github.io/mongo-java-driver/3.12/driver/tutorials/databases-collections/]
* Use [Codec and
CodecRegistry|http://mongodb.github.io/mongo-java-driver/3.12/bson/codecs/]
interface instead of {{DefaultDBEncoder}}
* {{MongoFilterUtil}}: Avoid changing query passed as reference so adapted to
return an {{Optional}} with subfilter to apply
* Use {{org.bson.Document}} as container everywhere (replace {{DBObject}})
* Use
[Filters|http://mongodb.github.io/mongo-java-driver/3.12/builders/filters/] and
[Projections|http://mongodb.github.io/mongo-java-driver/3.12/builders/projections/]
helper methods to facilitate the creation of filter documents
* {{MongoDBResult}}: pass {{cursor}} and {{size}} as constructor args
> Replace usage of deprecated API of MongoDB driver
> -
>
> Key: GORA-649
> URL: https://issues.apache.org/jira/browse/GORA-649
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-mongodb
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: patch
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After upgrade to 3.12 release of {{mongo-java-driver}} (in GORA-645), I've
> identified that we use some deprecated methods. Those methods will be removed
> in next (4.x) release of {{mongo-java-driver}}.
> Here is extract of warnings printed by javac :
> {code:java}
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[75,18]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[80,18]
> [deprecation] Mongo in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[210,11]
> [deprecation]
> MongoClient(List,List,MongoClientOptions) in
> MongoClient has been deprecated
> [WARNING] 15] [deprecation] MONGODB_CR in AuthenticationMechanism has been
> deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[230,34]
> [deprecation] createMongoCRCredential(String,String,char[]) in
> MongoCredential has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[249,54]
> [deprecation] getDB(String) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[292,67]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[313,69]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[338,14]
> [deprecation] fsync(boolean) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,23]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,12]
> [deprecation] addOption(int) in DBCursor has been deprecated{code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-647) Use Testcontainers for MongoDB integration tests
[
https://issues.apache.org/jira/browse/GORA-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065209#comment-17065209
]
Damien Raude-Morvan commented on GORA-647:
--
[https://github.com/apache/gora/pull/206|https://github.com/apache/gora/pull/206]
* Update {{gora-mongodb/pom.xml}} to use testcontainers
** Remove {{de.flapdoodle.embed.mongo}} dependency
** Remove {{mongo.embed.version}} property
** Add {{org.testcontainers}} dependency
* Create {{MongoContainer}} and it as a JUnit {{@ClassRule}}
* Add new test for MongoDB 4.2
* Refactor {{GoraMongodbTestDriver}}
** Provided container (passed in constructor) to configure Gora properties
* Update {{gora-benchmark/pom.xml}} to depends on {{gora-mongodb:test-jar}}
We can import MongoContainer in GoraClientTest
(with fixed MongoDB port on localhost)
* Refactor {{GoraMongodbAuthenticationTestDriver}}
** Use MongoDB docker container feature to initialize superuser (via
environment variables)
** Pass {{--auth}} and {{--setParameter authenticationMechanisms}} as commands
** Use mongo shell CLI - inside container - to execute script
> Use Testcontainers for MongoDB integration tests
>
>
> Key: GORA-647
> URL: https://issues.apache.org/jira/browse/GORA-647
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It seems that
> [flapdoodle.embed.mongo|https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo]
> artifact actually used for {{gora-mongodb}} integration tests is a bit
> outdated (ie. no support for latest MongoDB 4.2) and have no new commits
> since at least 6 months.
> I would like to align {{gora-mongodb}} integration tests with other Gora
> modules so that we also use [testcontainers|https://www.testcontainers.org/]
> which seems to provide more easier to maintain code (for instance,
> [mongo|https://hub.docker.com/_/mongo] docker container provide
> authentication support!)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GORA-649) Replace usage of deprecated API of MongoDB driver
[
https://issues.apache.org/jira/browse/GORA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-649:
-
Labels: patch (was: )
> Replace usage of deprecated API of MongoDB driver
> -
>
> Key: GORA-649
> URL: https://issues.apache.org/jira/browse/GORA-649
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-mongodb
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
> Labels: patch
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After upgrade to 3.12 release of {{mongo-java-driver}} (in GORA-645), I've
> identified that we use some deprecated methods. Those methods will be removed
> in next (4.x) release of {{mongo-java-driver}}.
> Here is extract of warnings printed by javac :
> {code:java}
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[75,18]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[80,18]
> [deprecation] Mongo in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[210,11]
> [deprecation]
> MongoClient(List,List,MongoClientOptions) in
> MongoClient has been deprecated
> [WARNING] 15] [deprecation] MONGODB_CR in AuthenticationMechanism has been
> deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[230,34]
> [deprecation] createMongoCRCredential(String,String,char[]) in
> MongoCredential has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[249,54]
> [deprecation] getDB(String) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[292,67]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[313,69]
> [deprecation] getMongo() in DB has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[338,14]
> [deprecation] fsync(boolean) in Mongo has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,23]
> [deprecation] Bytes in com.mongodb has been deprecated
> [WARNING]
> gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,12]
> [deprecation] addOption(int) in DBCursor has been deprecated{code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GORA-649) Replace usage of deprecated API of MongoDB driver
Damien Raude-Morvan created GORA-649:
Summary: Replace usage of deprecated API of MongoDB driver
Key: GORA-649
URL: https://issues.apache.org/jira/browse/GORA-649
Project: Apache Gora
Issue Type: Improvement
Components: gora-mongodb
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
After upgrade to 3.12 release of {{mongo-java-driver}} (in GORA-645), I've
identified that we use some deprecated methods. Those methods will be removed
in next (4.x) release of {{mongo-java-driver}}.
Here is extract of warnings printed by javac :
{code:java}
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[75,18]
[deprecation] Bytes in com.mongodb has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[80,18]
[deprecation] Mongo in com.mongodb has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[210,11]
[deprecation]
MongoClient(List,List,MongoClientOptions) in
MongoClient has been deprecated
[WARNING] 15] [deprecation] MONGODB_CR in AuthenticationMechanism has been
deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[230,34]
[deprecation] createMongoCRCredential(String,String,char[]) in MongoCredential
has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[249,54]
[deprecation] getDB(String) in Mongo has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[292,67]
[deprecation] getMongo() in DB has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[313,69]
[deprecation] getMongo() in DB has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[338,14]
[deprecation] fsync(boolean) in Mongo has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,23]
[deprecation] Bytes in com.mongodb has been deprecated
[WARNING]
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java:[506,12]
[deprecation] addOption(int) in DBCursor has been deprecated{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GORA-647) Use Testcontainers for MongoDB integration tests
Damien Raude-Morvan created GORA-647:
Summary: Use Testcontainers for MongoDB integration tests
Key: GORA-647
URL: https://issues.apache.org/jira/browse/GORA-647
Project: Apache Gora
Issue Type: Test
Components: gora-mongodb
Affects Versions: 0.9
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
It seems that
[flapdoodle.embed.mongo|https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo]
artifact actually used for {{gora-mongodb}} integration tests is a bit
outdated (ie. no support for latest MongoDB 4.2) and have no new commits since
at least 6 months.
I would like to align {{gora-mongodb}} integration tests with other Gora
modules so that we also use [testcontainers|https://www.testcontainers.org/]
which seems to provide more easier to maintain code (for instance,
[mongo|https://hub.docker.com/_/mongo] docker container provide authentication
support!)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GORA-646) Run integration tests on MongoDB 4.0 and 4.2
[
https://issues.apache.org/jira/browse/GORA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062096#comment-17062096
]
Damien Raude-Morvan commented on GORA-646:
--
_MongoDB_ 4.2 support is [not yet included into
de.flapdoodle.embed.mongo|https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/295]
framework used in {{gora-mongodb}} module.
So, for now, we will not be able to support running integration tests under
MongoDB 4.2
> Run integration tests on MongoDB 4.0 and 4.2
>
>
> Key: GORA-646
> URL: https://issues.apache.org/jira/browse/GORA-646
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
>
> I would like to follow upstream (MongoDB) support policy for *testing* our
> {{gora-mongodb}} module. For reference:
> * [https://www.mongodb.com/support-policy]
> * [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
> My action plan is to:
> # Add new integration tests profiles for MongoDB 3.6, 4.0 and -4.2-
> # Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GORA-646) Run integration tests on MongoDB 3.6 and 4.0
[
https://issues.apache.org/jira/browse/GORA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-646:
-
Summary: Run integration tests on MongoDB 3.6 and 4.0 (was: Run
integration tests on MongoDB 4.0 and 4.2)
> Run integration tests on MongoDB 3.6 and 4.0
>
>
> Key: GORA-646
> URL: https://issues.apache.org/jira/browse/GORA-646
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
>
> I would like to follow upstream (MongoDB) support policy for *testing* our
> {{gora-mongodb}} module. For reference:
> * [https://www.mongodb.com/support-policy]
> * [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
> My action plan is to:
> # Add new integration tests profiles for MongoDB 3.6, 4.0 and -4.2-
> # Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GORA-646) Run integration tests on MongoDB 4.0 and 4.2
[
https://issues.apache.org/jira/browse/GORA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-646:
-
Description:
I would like to follow upstream (MongoDB) support policy for *testing* our
{{gora-mongodb}} module. For reference:
* [https://www.mongodb.com/support-policy]
* [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
My action plan is to:
# Add new integration tests profiles for MongoDB 3.6, 4.0 and -4.2-
# Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
was:
I would like to follow upstream (MongoDB) support policy for *testing* our
{{gora-mongodb}} module. For reference:
* [https://www.mongodb.com/support-policy]
* [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
My action plan is to:
# Add new integration tests profiles for MongoDB 3.6, 4.0 and 4.2
# Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
> Run integration tests on MongoDB 4.0 and 4.2
>
>
> Key: GORA-646
> URL: https://issues.apache.org/jira/browse/GORA-646
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
>
> I would like to follow upstream (MongoDB) support policy for *testing* our
> {{gora-mongodb}} module. For reference:
> * [https://www.mongodb.com/support-policy]
> * [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
> My action plan is to:
> # Add new integration tests profiles for MongoDB 3.6, 4.0 and -4.2-
> # Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GORA-646) Run integration tests on MongoDB 4.0 and 4.2
[
https://issues.apache.org/jira/browse/GORA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-646:
-
Description:
I would like to follow upstream (MongoDB) support policy for *testing* our
{{gora-mongodb}} module. For reference:
* [https://www.mongodb.com/support-policy]
* [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
My action plan is to:
# Add new integration tests profiles for MongoDB 3.6, 4.0 and 4.2
# Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
was:
I would like to follow upstream (MongoDB) support policy for *testing* our
{{gora-mongodb}} module. For reference:
* [https://www.mongodb.com/support-policy]
* [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
My action plan is to:
# Add new integration tests profiles for MongoDB 4.0 and 4.2
# Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
> Run integration tests on MongoDB 4.0 and 4.2
>
>
> Key: GORA-646
> URL: https://issues.apache.org/jira/browse/GORA-646
> Project: Apache Gora
> Issue Type: Test
> Components: gora-mongodb
>Affects Versions: 0.9
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Major
>
> I would like to follow upstream (MongoDB) support policy for *testing* our
> {{gora-mongodb}} module. For reference:
> * [https://www.mongodb.com/support-policy]
> * [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
> My action plan is to:
> # Add new integration tests profiles for MongoDB 3.6, 4.0 and 4.2
> # Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GORA-646) Run integration tests on MongoDB 4.0 and 4.2
Damien Raude-Morvan created GORA-646:
Summary: Run integration tests on MongoDB 4.0 and 4.2
Key: GORA-646
URL: https://issues.apache.org/jira/browse/GORA-646
Project: Apache Gora
Issue Type: Test
Components: gora-mongodb
Affects Versions: 0.9
Reporter: Damien Raude-Morvan
Assignee: Damien Raude-Morvan
I would like to follow upstream (MongoDB) support policy for *testing* our
{{gora-mongodb}} module. For reference:
* [https://www.mongodb.com/support-policy]
* [https://docs.mongodb.com/manual/administration/production-notes/#x86-64]
My action plan is to:
# Add new integration tests profiles for MongoDB 4.0 and 4.2
# Remove old MongoDB 2.6, 3.0 and 3.2 profiles for _unsupported_ releases
--
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 ] Damien Raude-Morvan updated GORA-645: - Component/s: gora-mongodb > 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 > Components: gora-mongodb >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] [Commented] (GORA-448) Upgrade MongoDB Java Driver Version
[ https://issues.apache.org/jira/browse/GORA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091210#comment-15091210 ] Damien Raude-Morvan commented on GORA-448: -- Hi [~lewismc] ! I've opened a PR to upgrade Mongo Java driver to 3.2 If you can have a look, it would be great. I plan to merge this to master during this week. > Upgrade MongoDB Java Driver Version > --- > > Key: GORA-448 > URL: https://issues.apache.org/jira/browse/GORA-448 > Project: Apache Gora > Issue Type: Improvement > Components: gora-mongodb >Reporter: Lewis John McGibbney >Assignee: Damien Raude-Morvan >Priority: Minor > Fix For: 0.7 > > > MongoDB Java driver is now at 3.1.0 > http://search.maven.org/#artifactdetails|org.mongodb|mongo-java-driver|3.1.0|jar > We should upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-448) Upgrade MongoDB Java Driver Version
[ https://issues.apache.org/jira/browse/GORA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998279#comment-14998279 ] Damien Raude-Morvan commented on GORA-448: -- Hi ! I'm currently working on upgrade driver to 3.x release branch. My work is available on https://github.com/Dictanova/gora/tree/GORA-448 You can also compare with apache master : https://github.com/apache/gora/compare/master...Dictanova:GORA-448 Cheers, > Upgrade MongoDB Java Driver Version > --- > > Key: GORA-448 > URL: https://issues.apache.org/jira/browse/GORA-448 > Project: Apache Gora > Issue Type: Improvement > Components: gora-mongodb >Reporter: Lewis John McGibbney >Assignee: Damien Raude-Morvan >Priority: Minor > Fix For: 0.7 > > > MongoDB Java driver is now at 3.1.0 > http://search.maven.org/#artifactdetails|org.mongodb|mongo-java-driver|3.1.0|jar > We should upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-448) Upgrade MongoDB Java Driver Version
[ https://issues.apache.org/jira/browse/GORA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan reassigned GORA-448: Assignee: Damien Raude-Morvan I'll handle this upgrade. > Upgrade MongoDB Java Driver Version > --- > > Key: GORA-448 > URL: https://issues.apache.org/jira/browse/GORA-448 > Project: Apache Gora > Issue Type: Improvement > Components: gora-mongodb >Reporter: Lewis John McGibbney >Assignee: Damien Raude-Morvan >Priority: Minor > Fix For: 0.7 > > > MongoDB Java driver is now at 3.1.0 > http://search.maven.org/#artifactdetails|org.mongodb|mongo-java-driver|3.1.0|jar > We should upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-441) Update build.gradle within gora-gradle-plugin to reference canonical Apache links
[ https://issues.apache.org/jira/browse/GORA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan resolved GORA-441. -- Resolution: Fixed > Update build.gradle within gora-gradle-plugin to reference canonical Apache > links > -- > > Key: GORA-441 > URL: https://issues.apache.org/jira/browse/GORA-441 > Project: Apache Gora > Issue Type: Bug > Components: gora-gradle-plugin >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney > Fix For: 0.7 > > > The build.gradle references some external repositories which should be > changed to point to Apache ones. Additionally the Bintray username and API > key was not being picked up properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-426) MongoDB cursor timeout on long running parse job
[ https://issues.apache.org/jira/browse/GORA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-426: - Fix Version/s: 0.6.1 MongoDB cursor timeout on long running parse job Key: GORA-426 URL: https://issues.apache.org/jira/browse/GORA-426 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.6 Reporter: Alexander Yastrebov Assignee: Damien Raude-Morvan Labels: performance Fix For: 0.6.1 On long running parse job mongodb server may kill cursor by timeout (10 minutes default). We propose to disable server cursor timeout. See pull request https://github.com/apache/gora/pull/27 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-427) Configure MongoDB ReadPreference and WriteConcern
Damien Raude-Morvan created GORA-427: Summary: Configure MongoDB ReadPreference and WriteConcern Key: GORA-427 URL: https://issues.apache.org/jira/browse/GORA-427 Project: Apache Gora Issue Type: Improvement Components: gora-mongodb Affects Versions: 0.6 Reporter: Damien Raude-Morvan Assignee: Damien Raude-Morvan h5. Actual behavior Current MongoStore implementation doesn't allow configuration of [Read Preference|http://docs.mongodb.org/manual/core/read-preference/] and [Write Concern|http://docs.mongodb.org/manual/core/write-concern/] of MongoDB Java Driver h5. Proposed improvement Add gora.mongodb.readpreference and gora.mongodb.writeconcern properties to allow configuration during store initialization Please review PR : https://github.com/apache/gora/pull/28 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-426) MongoDB cursor timeout on long running parse job
[ https://issues.apache.org/jira/browse/GORA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-426: - Labels: performance (was: ) MongoDB cursor timeout on long running parse job Key: GORA-426 URL: https://issues.apache.org/jira/browse/GORA-426 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.6 Reporter: Alexander Yastrebov Assignee: Damien Raude-Morvan Labels: performance On long running parse job mongodb server may kill cursor by timeout (10 minutes default). We propose to disable server cursor timeout. See pull request https://github.com/apache/gora/pull/27 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-426) MongoDB cursor timeout on long running parse job
[ https://issues.apache.org/jira/browse/GORA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan reassigned GORA-426: Assignee: Damien Raude-Morvan MongoDB cursor timeout on long running parse job Key: GORA-426 URL: https://issues.apache.org/jira/browse/GORA-426 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.6 Reporter: Alexander Yastrebov Assignee: Damien Raude-Morvan On long running parse job mongodb server may kill cursor by timeout (10 minutes default). We propose to disable server cursor timeout. See pull request https://github.com/apache/gora/pull/27 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-424) MongoDBResult issues count() request on progress
[ https://issues.apache.org/jira/browse/GORA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-424: - Fix Version/s: 0.6.1 MongoDBResult issues count() request on progress Key: GORA-424 URL: https://issues.apache.org/jira/browse/GORA-424 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.6 Reporter: Alexander Yastrebov Fix For: 0.6.1 MongoDBResult.getProgress calls cursor.size() which in turn issues count request on underlying collection. See pull request https://github.com/apache/gora/pull/26 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-424) MongoDBResult issues count() request on progress
[ https://issues.apache.org/jira/browse/GORA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan resolved GORA-424. -- Resolution: Fixed Assignee: Damien Raude-Morvan Merged into master as bb09d8916736e3e572eef2cb5e79fe11c80ad1de MongoDBResult issues count() request on progress Key: GORA-424 URL: https://issues.apache.org/jira/browse/GORA-424 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.6 Reporter: Alexander Yastrebov Assignee: Damien Raude-Morvan Fix For: 0.6.1 MongoDBResult.getProgress calls cursor.size() which in turn issues count request on underlying collection. See pull request https://github.com/apache/gora/pull/26 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-423) BSONDecorator returns empty string for null field value
[ https://issues.apache.org/jira/browse/GORA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan resolved GORA-423. -- Resolution: Fixed Assignee: Damien Raude-Morvan Merged into master as 903aeb016f1efa6fbd7bc245f849062e10e0bf11 BSONDecorator returns empty string for null field value --- Key: GORA-423 URL: https://issues.apache.org/jira/browse/GORA-423 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Reporter: Alexander Yastrebov Assignee: Damien Raude-Morvan Fix For: 0.6.1 BSONDecorator returns empty string for null field value See pull request https://github.com/apache/gora/pull/25 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-330) gora-gradle-plugin
[ https://issues.apache.org/jira/browse/GORA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan resolved GORA-330. -- Resolution: Fixed gora-gradle-plugin -- Key: GORA-330 URL: https://issues.apache.org/jira/browse/GORA-330 Project: Apache Gora Issue Type: New Feature Components: plugins Reporter: Lewis John McGibbney Assignee: Damien Raude-Morvan Fix For: 0.7 Assigned to Damien for karma :) This issue will track the contribution of the gora-gradle-plugin to our SCM. Thanks [~drazzib], is it possible for you to create a PR adding this as a new module named *gora-gradle*? Thank you very much in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-330) gora-gradle-plugin
[ https://issues.apache.org/jira/browse/GORA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313069#comment-14313069 ] Damien Raude-Morvan commented on GORA-330: -- [~hsaputra], exactly. @Dictanova we use Gradle extensively for all our modules (in-place of Maven). We don't commit geneated files into Git, so I'm using this module to generate - at built time - all needed Java source files from Gora schema files. gora-gradle-plugin -- Key: GORA-330 URL: https://issues.apache.org/jira/browse/GORA-330 Project: Apache Gora Issue Type: New Feature Components: plugins Reporter: Lewis John McGibbney Assignee: Damien Raude-Morvan Fix For: 0.7 Assigned to Damien for karma :) This issue will track the contribution of the gora-gradle-plugin to our SCM. Thanks [~drazzib], is it possible for you to create a PR adding this as a new module named *gora-gradle*? Thank you very much in advance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250064#comment-14250064
]
Damien Raude-Morvan commented on GORA-388:
--
Hi!
I haven't had time to work on this particular issue to improve (generalize on
all Datastore) used approach.
[~lewismc], did you had some time to think about it ? Do you have a clear
overview of needed step to improve UTF8 handling in our Datastore ?
What do you think about commiting my patch as is and latter on provide a better
solution for all Datastore ?
Regards,
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GORA-401) Serialization and deserialization of Persistent does not hold the entity dirty state
[
https://issues.apache.org/jira/browse/GORA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250056#comment-14250056
]
Damien Raude-Morvan commented on GORA-401:
--
Hi,
I have asked a similar question on gora-user mailing list earlier this year :
https://www.mail-archive.com/user@gora.apache.org/msg00339.html
So I'm in favor of restoring PersistentDatumWriter/Reader as you proposed.
Regards,
Serialization and deserialization of Persistent does not hold the entity
dirty state
Key: GORA-401
URL: https://issues.apache.org/jira/browse/GORA-401
Project: Apache Gora
Issue Type: Bug
Components: gora-core
Affects Versions: 0.4, 0.5
Environment: Tested on gora-0.4, but seems logically to hold on
gora-0.5
Reporter: Alfonso Nishikawa
Priority: Critical
Labels: serialization
Original Estimate: 35h
Remaining Estimate: 35h
After removing __g__dirty field in GORA-326, dirty field is not serialized.
In GORA-321
{{[PersistentSerializer|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/mapreduce/PersistentSerializer.java]}}
went from using
{{[PersistentDatumWriter|https://github.com/apache/gora/blob/apache-gora-0.3/gora-core/src/main/java/org/apache/gora/avro/PersistentDatumWriter.java](/Reader)}}
to Avro's {{SpecificDatumWriter}}, delegating the serialization of the dirty
field to Avro (but really not desirable to have that field as a main field in
the entities).
The proposal is to reintroduce the {{PersistentDatumWriter/Reader}} which
will serialize the internal fields of the entities.
This bug affects, for example, Nutch, which loads only some fields in it's
phases, serializes entities (from Map to Reduce), and when deserializes finds
all fields as dirty, independently of what fields were modified in the Map,
and overwrite all data in datastore (deleting much things: downloaded
content, parsed content, etc).
This effect can be seen in
{{TestPersistentSerialization#testSerderEmployeeTwoFields}}, when debuging in
{{TestIOUtils#testSerializeDeserialize}}. Proper breakpoints an inspections
shows that, entities are equal when it's fields are equal. This is fine as
equal definition, but another test must be added to check that
serialization an deserialization keeps the dirty state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GORA-388) MongoStore: Fix handling of Utf8 in filters
Damien Raude-Morvan created GORA-388:
Summary: MongoStore: Fix handling of Utf8 in filters
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to its
local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-388:
-
Attachment: operands_serialization.diff
I'm not complety satisfied with this patch because :
* since method signature is ListObject rawOperands, caller can send
any datatype which might lead to other types of crash
* we have to implement this transformation in each driver (which seems
error prone)
* I'm not sure of use-case of Utf8 as Operand (ie. I'm only using
String type here)
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Attachments: operands_serialization.diff
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-388:
-
Attachment: (was: operands_serialization.diff)
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-388:
-
Comment: was deleted
(was: I'm not complety satisfied with this PR because :
* since method signature is ListObject rawOperands, caller can send
any datatype which might lead to other types of crash
* we have to implement this transformation in each driver (which seems
error prone)
* I'm not sure of use-case of Utf8 as Operand (ie. I'm only using
String type here))
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176351#comment-14176351
]
Damien Raude-Morvan edited comment on GORA-388 at 10/19/14 5:14 PM:
I'm not complety satisfied with this PR because :
* since method signature is ListObject rawOperands, caller can send
any datatype which might lead to other types of crash
* we have to implement this transformation in each driver (which seems
error prone)
* I'm not sure of use-case of Utf8 as Operand (ie. I'm only using
String type here)
was (Author: drazzib):
I'm not complety satisfied with this patch because :
* since method signature is ListObject rawOperands, caller can send
any datatype which might lead to other types of crash
* we have to implement this transformation in each driver (which seems
error prone)
* I'm not sure of use-case of Utf8 as Operand (ie. I'm only using
String type here)
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GORA-388) MongoStore: Fix handling of Utf8 in filters
[
https://issues.apache.org/jira/browse/GORA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176354#comment-14176354
]
Damien Raude-Morvan commented on GORA-388:
--
I'm not complety satisfied with this PR because :
* since method signature is ListObject rawOperands, caller can send
any datatype which might lead to other types of crash
* we have to implement this transformation in each driver (which seems
error prone)
* I'm not sure of use-case of Utf8 as Operand (ie. I'm only using
String type here)
MongoStore: Fix handling of Utf8 in filters
---
Key: GORA-388
URL: https://issues.apache.org/jira/browse/GORA-388
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
Gora 0.5 MongoDB driver fail to properly serialize Utf8 instance passed to
its local filters implementation.
Here is sample code
{noformat}
filter.getOperands().add(new Utf8(batchId));
{noformat}
that will trigger the following exception at runtime
{noformat}
java.lang.IllegalArgumentException: can't serialize class
org.apache.avro.util.Utf8
at org.bson.BasicBSONEncoder._putObjectField(BasicBSONEncoder.java:284)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:185)
at org.bson.BasicBSONEncoder.putObject(BasicBSONEncoder.java:131)
at com.mongodb.DefaultDBEncoder.writeObject(DefaultDBEncoder.java:33)
at com.mongodb.OutMessage.putObject(OutMessage.java:289)
at com.mongodb.OutMessage.writeQuery(OutMessage.java:211)
at com.mongodb.OutMessage.query(OutMessage.java:86)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:81)
at com.mongodb.DBCollectionImpl.find(DBCollectionImpl.java:66)
at com.mongodb.DBCursor._check(DBCursor.java:458)
at com.mongodb.DBCursor._hasNext(DBCursor.java:546)
at com.mongodb.DBCursor.hasNext(DBCursor.java:571)
at
org.apache.gora.mongodb.query.MongoDBResult.nextInner(MongoDBResult.java:69)
at org.apache.gora.query.impl.ResultBase.next(ResultBase.java:114)
at
org.apache.gora.mapreduce.GoraRecordReader.nextKeyValue(GoraRecordReader.java:119)
at
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:531)
at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:364)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:223)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
This pattern is extensively used by Apache Nutch :
*
[FetcherJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java#L218]
*
[ParserJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/parse/ParserJob.java#L274]
*
[DbUpdaterJob|https://github.com/apache/nutch/blob/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java#L128]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GORA-389) MongoStore: Document or List mapping change cause NPE in clearDirty()
Damien Raude-Morvan created GORA-389:
Summary: MongoStore: Document or List mapping change cause NPE in
clearDirty()
Key: GORA-389
URL: https://issues.apache.org/jira/browse/GORA-389
Project: Apache Gora
Issue Type: Bug
Components: gora-mongodb
Affects Versions: 0.5
Reporter: Damien Raude-Morvan
I've found an issue in current implementation of MongoStore on [Document or
List|http://gora.apache.org/current/gora-mongodb.html] mapping type handling.
If your schema contains a field like this :
{noformat}
{ name: keywords,
type: { type: array, items: string},
default: null
}
{noformat}
If you choose to latter defaults to an empty array instead of null value like
this
{noformat}
{ name: keywords,
type: { type: array, items: string},
default: []
}
{noformat}
loading old data will fail because of clearDirty method will try to also clear
a null object.
{code}
persistent.clearDirty();
{code}
I implemented and tested a fix which always return a DirtyListWrapper or
DirtyMapWrapper instead of previous null value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GORA-373) Failing TestQueryBase with JDK8
Damien Raude-Morvan created GORA-373: Summary: Failing TestQueryBase with JDK8 Key: GORA-373 URL: https://issues.apache.org/jira/browse/GORA-373 Project: Apache Gora Issue Type: Bug Components: gora-core Affects Versions: 0.5 Environment: Java 8 OpenJDK 8u40~b04-2 (Debian package) Reporter: Damien Raude-Morvan Priority: Minor Hi, Got a test failure under JDK8 in TestQueryBase I haven't yet had time to check details but got EOFException : java.io.EOFException at org.apache.avro.util.ByteBufferInputStream.getBuffer(ByteBufferInputStream.java:86) at org.apache.avro.util.ByteBufferInputStream.read(ByteBufferInputStream.java:48) at java.io.DataInputStream.readFully(DataInputStream.java:195) at org.apache.hadoop.io.Text.readString(Text.java:402) at org.apache.gora.mapreduce.StringSerialization$1.deserialize(StringSerialization.java:55) at org.apache.gora.mapreduce.StringSerialization$1.deserialize(StringSerialization.java:40) at org.apache.gora.util.IOUtils.deserialize(IOUtils.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-335) Create site documentation for gora-mongodb
[ https://issues.apache.org/jira/browse/GORA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-335: - Attachment: GORA_335_v1.diff Create site documentation for gora-mongodb -- Key: GORA-335 URL: https://issues.apache.org/jira/browse/GORA-335 Project: Apache Gora Issue Type: Improvement Components: documentation, gora-mongodb Reporter: Lewis John McGibbney Assignee: Damien Raude-Morvan Fix For: 0.6 Attachments: GORA_335_v1.diff We should associate up-to-date documentation with the newly committed mongodb module. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-335) Create site documentation for gora-mongodb
[ https://issues.apache.org/jira/browse/GORA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14031862#comment-14031862 ] Damien Raude-Morvan commented on GORA-335: -- Is there a specific how-to contribute on Gora website ? I would like to help creating documentation about mongo on official Gora website. Create site documentation for gora-mongodb -- Key: GORA-335 URL: https://issues.apache.org/jira/browse/GORA-335 Project: Apache Gora Issue Type: Improvement Components: documentation, gora-mongodb Reporter: Lewis John McGibbney Fix For: 0.5 We should associate up-to-date documentation with the newly committed mongodb module. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-330) gora-gradle-plugin
[ https://issues.apache.org/jira/browse/GORA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14031864#comment-14031864 ] Damien Raude-Morvan commented on GORA-330: -- Hi, My actual gora-gradle plugin is built using gradle itself (dogfooding) so I'm looking for appropriate integration. Do you want to build plugin inside main gora buildsystem ? Regards, gora-gradle-plugin -- Key: GORA-330 URL: https://issues.apache.org/jira/browse/GORA-330 Project: Apache Gora Issue Type: New Feature Components: plugins Reporter: Lewis John McGibbney Assignee: Damien Raude-Morvan Fix For: 0.5 Assigned to Damien for karma :) This issue will track the contribution of the gora-gradle-plugin to our SCM. Thanks [~drazzib], is it possible for you to create a PR adding this as a new module named *gora-gradle*? Thank you very much in advance. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (GORA-336) MongoFilterUtil: missing ref link when creating new instance of factory
Damien Raude-Morvan created GORA-336: Summary: MongoFilterUtil: missing ref link when creating new instance of factory Key: GORA-336 URL: https://issues.apache.org/jira/browse/GORA-336 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.5 Reporter: Damien Raude-Morvan There is a small issue inside MongoFilterUtil handling of FilterList When creating a factory (subclass of FilterFactory) it won't call #setFilterUtil method. So that, when caller provide a FilterList which will then call back MongoFilterUtil for each sub-filter in list it will crash with a NullPointerException. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (GORA-336) MongoFilterUtil: missing ref link when creating new instance of factory
[ https://issues.apache.org/jira/browse/GORA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-336: - Attachment: MongoStore__fix_missing_link_to_MongoFilterUtil.patch MongoFilterUtil: missing ref link when creating new instance of factory --- Key: GORA-336 URL: https://issues.apache.org/jira/browse/GORA-336 Project: Apache Gora Issue Type: Bug Components: gora-mongodb Affects Versions: 0.5 Reporter: Damien Raude-Morvan Labels: patch Attachments: MongoStore__fix_missing_link_to_MongoFilterUtil.patch There is a small issue inside MongoFilterUtil handling of FilterList When creating a factory (subclass of FilterFactory) it won't call #setFilterUtil method. So that, when caller provide a FilterList which will then call back MongoFilterUtil for each sub-filter in list it will crash with a NullPointerException. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-332) Gora 0.4 compiler generate invalid Java code
[
https://issues.apache.org/jira/browse/GORA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018569#comment-14018569
]
Damien Raude-Morvan commented on GORA-332:
--
I've prepared a PR (on GitHub) to fix this issue.
https://github.com/apache/gora/pull/1
[Is that okay for you to use GitHub features for PR ?]
It simply rename _deepCopyToWriteOnlyBuffer_ to _deepCopyToReadOnlyBuffer_
which expected method name in generated java code when schema
contains a **bytes** field type.
Gora 0.4 compiler generate invalid Java code
Key: GORA-332
URL: https://issues.apache.org/jira/browse/GORA-332
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Fix For: 0.5
Pursuing my journey on GORA-199 I've detected another issue with Gora
compiler.if there is a bytes type field inside a record.
{noformat}
{
name: RecordWityBytes,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyData,
type: bytes
}
}
]
}
{noformat}
Gora 0.4 will generate java code without crashing but if you try to compile
generated code with javac, you'll get the following error :
{noformat}
$ ./bin/gora goracompiler record_with_bytes.avsc test/
Compiling: /home/drazzib/incoming/apache-gora-0.4/record_with_bytes.avsc
Compiled into: /home/drazzib/incoming/apache-gora-0.4/test
Compiler executed SUCCESSFULL.
$ find test/ -name *.java | xargs javac -cp
gora-core/target/classes/:gora-core/lib/avro-1.7.4.jar:gora-core/lib/jackson-core-asl-1.6.9.jar
-d test/
test/com/drazzib/com/RecordWityBytes.java:92: error: cannot find symbol
this.type = deepCopyToReadOnlyBuffer(value);
^
symbol: method deepCopyToReadOnlyBuffer(ByteBuffer)
location: class RecordWityBytes
1 error
{noformat}
You can clone this gist
[https://gist.github.com/drazzib/263da2ec0dc46afac0d0] to easily reproduce
this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (GORA-331) Gora 0.4 compiler crash with enum type
[
https://issues.apache.org/jira/browse/GORA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-331:
-
Labels: patch (was: )
Gora 0.4 compiler crash with enum type
Key: GORA-331
URL: https://issues.apache.org/jira/browse/GORA-331
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Labels: patch
Fix For: 0.5
As part of my work on GORA-199 I've updated some Dictanova projects to 0.4
release (more precisly to 0.5-SNAPSHOT) for testing.
Unfortunelly, I've detected that Gora Compiler crash if there is an enum
type field inside a record.
{noformat}
{
name: RecordWithEnum,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyEnum,
type: enum,
symbols: [
PERIOD,
INSTANT
]
}
}
]
}
{noformat}
If you try to compile this schema with Gora 0.4, you'll get the following
error :
{noformat}
/bin/gora goracompiler record_with_enum.avsc test/
Compiling: record_with_enum.avsc
74 [main] ERROR AvroVelocityLogChute - ResourceManager : unable to find
resource '/org/apache/gora/compiler/templates/enum.vm' in any resource loader.
Exception in thread main java.lang.RuntimeException:
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:329)
at
org.apache.avro.compiler.specific.SpecificCompiler.compile(SpecificCompiler.java:371)
at
org.apache.avro.compiler.specific.SpecificCompiler.compileToDestination(SpecificCompiler.java:316)
at
org.apache.gora.compiler.GoraCompiler.compileSchema(GoraCompiler.java:65)
at
org.apache.gora.compiler.cli.GoraCompilerCLI.main(GoraCompilerCLI.java:56)
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to
find resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:352)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1533)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1514)
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:373)
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:327)
... 4 more
{noformat}
I've managed to workaround this problem by simply dropping avro enum.vm
inside gora source.
You can easily clone this gist
[https://gist.github.com/drazzib/35e504e6e689f96dae8f] so that you can
reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (GORA-332) Gora 0.4 compiler generate invalid Java code
[
https://issues.apache.org/jira/browse/GORA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Raude-Morvan updated GORA-332:
-
Labels: patch (was: )
Gora 0.4 compiler generate invalid Java code
Key: GORA-332
URL: https://issues.apache.org/jira/browse/GORA-332
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Labels: patch
Fix For: 0.5
Pursuing my journey on GORA-199 I've detected another issue with Gora
compiler.if there is a bytes type field inside a record.
{noformat}
{
name: RecordWityBytes,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyData,
type: bytes
}
}
]
}
{noformat}
Gora 0.4 will generate java code without crashing but if you try to compile
generated code with javac, you'll get the following error :
{noformat}
$ ./bin/gora goracompiler record_with_bytes.avsc test/
Compiling: /home/drazzib/incoming/apache-gora-0.4/record_with_bytes.avsc
Compiled into: /home/drazzib/incoming/apache-gora-0.4/test
Compiler executed SUCCESSFULL.
$ find test/ -name *.java | xargs javac -cp
gora-core/target/classes/:gora-core/lib/avro-1.7.4.jar:gora-core/lib/jackson-core-asl-1.6.9.jar
-d test/
test/com/drazzib/com/RecordWityBytes.java:92: error: cannot find symbol
this.type = deepCopyToReadOnlyBuffer(value);
^
symbol: method deepCopyToReadOnlyBuffer(ByteBuffer)
location: class RecordWityBytes
1 error
{noformat}
You can clone this gist
[https://gist.github.com/drazzib/263da2ec0dc46afac0d0] to easily reproduce
this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (GORA-331) Gora 0.4 compiler crash with enum type
[
https://issues.apache.org/jira/browse/GORA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018570#comment-14018570
]
Damien Raude-Morvan commented on GORA-331:
--
I've prepared a PR (on GitHub) to fix this issue.
https://github.com/apache/gora/pull/2
I've imported _enum.vm_ template from Avro compiler source code (as-is) to fix
GoraCompiler
crash in case schema contains an enum field type.
Gora 0.4 compiler crash with enum type
Key: GORA-331
URL: https://issues.apache.org/jira/browse/GORA-331
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Labels: patch
Fix For: 0.5
As part of my work on GORA-199 I've updated some Dictanova projects to 0.4
release (more precisly to 0.5-SNAPSHOT) for testing.
Unfortunelly, I've detected that Gora Compiler crash if there is an enum
type field inside a record.
{noformat}
{
name: RecordWithEnum,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyEnum,
type: enum,
symbols: [
PERIOD,
INSTANT
]
}
}
]
}
{noformat}
If you try to compile this schema with Gora 0.4, you'll get the following
error :
{noformat}
/bin/gora goracompiler record_with_enum.avsc test/
Compiling: record_with_enum.avsc
74 [main] ERROR AvroVelocityLogChute - ResourceManager : unable to find
resource '/org/apache/gora/compiler/templates/enum.vm' in any resource loader.
Exception in thread main java.lang.RuntimeException:
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:329)
at
org.apache.avro.compiler.specific.SpecificCompiler.compile(SpecificCompiler.java:371)
at
org.apache.avro.compiler.specific.SpecificCompiler.compileToDestination(SpecificCompiler.java:316)
at
org.apache.gora.compiler.GoraCompiler.compileSchema(GoraCompiler.java:65)
at
org.apache.gora.compiler.cli.GoraCompilerCLI.main(GoraCompilerCLI.java:56)
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to
find resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:352)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1533)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1514)
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:373)
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:327)
... 4 more
{noformat}
I've managed to workaround this problem by simply dropping avro enum.vm
inside gora source.
You can easily clone this gist
[https://gist.github.com/drazzib/35e504e6e689f96dae8f] so that you can
reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (GORA-331) Gora 0.4 compiler crash with enum type
[
https://issues.apache.org/jira/browse/GORA-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019179#comment-14019179
]
Damien Raude-Morvan commented on GORA-331:
--
Hi [~hsaputra],
AFAIK, this is a limitation of Avro SpecificCompiler which doesn't support
multiple template directories.
= GoraCompiler override templateDir to
/org/apache/gora/compiler/templates/ which doesn't contains enum.vm
Maybe we should open a feature request in Avro to support multiple template
directories.
In the meantime, I think we could just duplicate missing templates to fix this
crash.
Regards,
Gora 0.4 compiler crash with enum type
Key: GORA-331
URL: https://issues.apache.org/jira/browse/GORA-331
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Labels: patch
Fix For: 0.5
As part of my work on GORA-199 I've updated some Dictanova projects to 0.4
release (more precisly to 0.5-SNAPSHOT) for testing.
Unfortunelly, I've detected that Gora Compiler crash if there is an enum
type field inside a record.
{noformat}
{
name: RecordWithEnum,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyEnum,
type: enum,
symbols: [
PERIOD,
INSTANT
]
}
}
]
}
{noformat}
If you try to compile this schema with Gora 0.4, you'll get the following
error :
{noformat}
/bin/gora goracompiler record_with_enum.avsc test/
Compiling: record_with_enum.avsc
74 [main] ERROR AvroVelocityLogChute - ResourceManager : unable to find
resource '/org/apache/gora/compiler/templates/enum.vm' in any resource loader.
Exception in thread main java.lang.RuntimeException:
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:329)
at
org.apache.avro.compiler.specific.SpecificCompiler.compile(SpecificCompiler.java:371)
at
org.apache.avro.compiler.specific.SpecificCompiler.compileToDestination(SpecificCompiler.java:316)
at
org.apache.gora.compiler.GoraCompiler.compileSchema(GoraCompiler.java:65)
at
org.apache.gora.compiler.cli.GoraCompilerCLI.main(GoraCompilerCLI.java:56)
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to
find resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:352)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1533)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1514)
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:373)
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:327)
... 4 more
{noformat}
I've managed to workaround this problem by simply dropping avro enum.vm
inside gora source.
You can easily clone this gist
[https://gist.github.com/drazzib/35e504e6e689f96dae8f] so that you can
reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018304#comment-14018304 ] Damien Raude-Morvan commented on GORA-199: -- HI [~lewismc] and [~hsaputra] ! Thank you all for your help on getting this properly integrated into Gora! I hope to be able to improve this support in coming weeks/months. Regards, Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: gora-mongodb, storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.5 Attachments: GORA-119-trunk.patch, GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-332) Gora 0.4 compiler generate invalid Java code
[
https://issues.apache.org/jira/browse/GORA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009639#comment-14009639
]
Damien Raude-Morvan commented on GORA-332:
--
Hi [~renato2099],
- At first, my test folder is absolutly empty.
This test directory is just created to allow goracompiler to generate
Java source code from avsc schema.
- I've extracted this minimal classpath (gore-core + avro + jackson) for
purpose of this bugreport :)
YMMV, but I prefer submitting the easiest test case for my bug report to
avoid any side effect.
I've reproduced the very same issue using full classpath as defined inside
gora pom.xml so I do not think classpath is related
Regards,
Gora 0.4 compiler generate invalid Java code
Key: GORA-332
URL: https://issues.apache.org/jira/browse/GORA-332
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Pursuing my journey on GORA-199 I've detected another issue with Gora
compiler.if there is a bytes type field inside a record.
{noformat}
{
name: RecordWityBytes,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyData,
type: bytes
}
}
]
}
{noformat}
Gora 0.4 will generate java code without crashing but if you try to compile
generated code with javac, you'll get the following error :
{noformat}
$ ./bin/gora goracompiler record_with_bytes.avsc test/
Compiling: /home/drazzib/incoming/apache-gora-0.4/record_with_bytes.avsc
Compiled into: /home/drazzib/incoming/apache-gora-0.4/test
Compiler executed SUCCESSFULL.
$ find test/ -name *.java | xargs javac -cp
gora-core/target/classes/:gora-core/lib/avro-1.7.4.jar:gora-core/lib/jackson-core-asl-1.6.9.jar
-d test/
test/com/drazzib/com/RecordWityBytes.java:92: error: cannot find symbol
this.type = deepCopyToReadOnlyBuffer(value);
^
symbol: method deepCopyToReadOnlyBuffer(ByteBuffer)
location: class RecordWityBytes
1 error
{noformat}
You can clone this gist
[https://gist.github.com/drazzib/263da2ec0dc46afac0d0] to easily reproduce
this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (GORA-332) Gora 0.4 compiler generate invalid Java code
Damien Raude-Morvan created GORA-332:
Summary: Gora 0.4 compiler generate invalid Java code
Key: GORA-332
URL: https://issues.apache.org/jira/browse/GORA-332
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
Pursuing my journey on GORA-199 I've detected another issue with Gora
compiler.if there is a bytes type field inside a record.
{noformat}
{
name: RecordWityBytes,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyData,
type: bytes
}
}
]
}
{noformat}
Gora 0.4 will generate java code without crashing but if you try to compile
generated code with javac, you'll get the following error :
{noformat}
$ ./bin/gora goracompiler record_with_bytes.avsc test/
Compiling: /home/drazzib/incoming/apache-gora-0.4/record_with_bytes.avsc
Compiled into: /home/drazzib/incoming/apache-gora-0.4/test
Compiler executed SUCCESSFULL.
$ find test/ -name *.java | xargs javac -cp
gora-core/target/classes/:gora-core/lib/avro-1.7.4.jar:gora-core/lib/jackson-core-asl-1.6.9.jar
-d test/
test/com/drazzib/com/RecordWityBytes.java:92: error: cannot find symbol
this.type = deepCopyToReadOnlyBuffer(value);
^
symbol: method deepCopyToReadOnlyBuffer(ByteBuffer)
location: class RecordWityBytes
1 error
{noformat}
You can clone this gist [https://gist.github.com/drazzib/263da2ec0dc46afac0d0]
to easily reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (GORA-331) Gora 0.4 compiler crash with enum type
Damien Raude-Morvan created GORA-331:
Summary: Gora 0.4 compiler crash with enum type
Key: GORA-331
URL: https://issues.apache.org/jira/browse/GORA-331
Project: Apache Gora
Issue Type: Bug
Components: gora-compiler
Affects Versions: 0.4, 0.5
Reporter: Damien Raude-Morvan
As part of my work on GORA-199 I've updated some Dictanova projects to 0.4
release (more precisly to 0.5-SNAPSHOT) for testing.
Unfortunelly, I've detected that Gora Compiler crash if there is an enum type
field inside a record.
{noformat}
{
name: RecordWithEnum,
namespace: com.drazzib.com,
type: record,
fields: [
{
name: type,
type: {
name: MyEnum,
type: enum,
symbols: [
PERIOD,
INSTANT
]
}
}
]
}
{noformat}
If you try to compile this schema with Gora 0.4, you'll get the following error
:
{noformat}
/bin/gora goracompiler record_with_enum.avsc test/
Compiling: record_with_enum.avsc
74 [main] ERROR AvroVelocityLogChute - ResourceManager : unable to find
resource '/org/apache/gora/compiler/templates/enum.vm' in any resource loader.
Exception in thread main java.lang.RuntimeException:
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:329)
at
org.apache.avro.compiler.specific.SpecificCompiler.compile(SpecificCompiler.java:371)
at
org.apache.avro.compiler.specific.SpecificCompiler.compileToDestination(SpecificCompiler.java:316)
at
org.apache.gora.compiler.GoraCompiler.compileSchema(GoraCompiler.java:65)
at
org.apache.gora.compiler.cli.GoraCompilerCLI.main(GoraCompilerCLI.java:56)
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to
find resource '/org/apache/gora/compiler/templates/enum.vm'
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:352)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1533)
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1514)
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:373)
at
org.apache.avro.compiler.specific.SpecificCompiler.renderTemplate(SpecificCompiler.java:327)
... 4 more
{noformat}
I've managed to workaround this problem by simply dropping avro enum.vm inside
gora source.
You can easily clone this gist
[https://gist.github.com/drazzib/35e504e6e689f96dae8f] so that you can
reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000903#comment-14000903 ] Damien Raude-Morvan commented on GORA-199: -- Hi [~lewismc], * I've updated version in GoraMongodbTestDriver to use latest PRODUCTION release * I've removed reference to Nutch stuff for my branch * Could you please provide a template for code formating (for Eclipse or IntelliJ IDEA maybe ?) * TestMongoStore: references to StateManager are in comments but yeah, I need to work a bit on this one to update it for trunk Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.5 Attachments: GORA-119-trunk.patch, GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000904#comment-14000904 ] Damien Raude-Morvan edited comment on GORA-277 at 5/17/14 10:18 PM: Yes, we could like to contribute this to Apache ! You to you want to integrate this patch ? Is there some kind of contrib module where we can host a non-maven project like this ? was (Author: drazzib): Yes, we could like to contribute this to Apache ? You to you want to integrate this patch ? Is there a contrib module where we can host a non-maven project like this ? Create gora-maven-plugin Key: GORA-277 URL: https://issues.apache.org/jira/browse/GORA-277 Project: Apache Gora Issue Type: Improvement Components: gora-compiler Reporter: Lewis John McGibbney Fix For: 0.5 Recently the motivation for this one came when I used the avro-maven-plugin but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes using the GoraCompiler a piece of cake and really lowers the barrier to generating Gora compliant Java beans. Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000904#comment-14000904 ] Damien Raude-Morvan commented on GORA-277: -- Yes, we could like to contribute this to Apache ? You to you want to integrate this patch ? Is there a contrib module where we can host a non-maven project like this ? Create gora-maven-plugin Key: GORA-277 URL: https://issues.apache.org/jira/browse/GORA-277 Project: Apache Gora Issue Type: Improvement Components: gora-compiler Reporter: Lewis John McGibbney Fix For: 0.5 Recently the motivation for this one came when I used the avro-maven-plugin but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes using the GoraCompiler a piece of cake and really lowers the barrier to generating Gora compliant Java beans. Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998909#comment-13998909 ] Damien Raude-Morvan commented on GORA-199: -- Okay, so I'll try to finalize a proper patch during this evening and submit it to this JIRA issue. Cheers, Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.5 Attachments: GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998115#comment-13998115 ] Damien Raude-Morvan commented on GORA-199: -- Hi [~hsaputra] and [~lewismc], If possible, I would like to avoid exchanging patch (ie. exporting git without prefix) but if you prefer to work with patch I'll try to adapt :) I'll postpone filter enabled scan to a latter release I think. So only blocking issue is to get UNION support fixed (I've already worked in it previously to GORA_94 merge) I've added link to my Gora Gradle Plugin as a comment in [GORA-277]. Cheers, Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.5 Attachments: GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998102#comment-13998102 ] Damien Raude-Morvan commented on GORA-277: -- Hi there, You can find my Gradle plugin for Gora here : https://github.com/Dictanova/gora-gradle-plugin Create gora-maven-plugin Key: GORA-277 URL: https://issues.apache.org/jira/browse/GORA-277 Project: Apache Gora Issue Type: Improvement Components: gora-compiler Reporter: Lewis John McGibbney Fix For: 0.5 Recently the motivation for this one came when I used the avro-maven-plugin but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes using the GoraCompiler a piece of cake and really lowers the barrier to generating Gora compliant Java beans. Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: (was: GORA-199.patch) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib Fix For: 0.4 Attachments: GORA-199.patch, GORA-199v2.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: (was: 0001-GORA-199-MongoDB-Support-in-Gora.patch) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib Fix For: 0.4 Attachments: GORA-199.patch, GORA-199v2.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: (was: GORA-199v3.patch) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib Fix For: 0.4 Attachments: GORA-199.patch, GORA-199v2.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Labels: contrib patch (was: contrib) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.4 Attachments: GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: (was: GORA-199v3.patch) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Assignee: Damien Raude-Morvan Priority: Minor Labels: contrib, patch Fix For: 0.4 Attachments: GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (GORA-275) Update Gora stores to pass conf when creating instance of PartitionQueryImpl
[ https://issues.apache.org/jira/browse/GORA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-275: - Attachment: 0001-GORA-275-Update-Gora-stores-to-pass-conf-when-creati.patch Update Gora stores to pass conf when creating instance of PartitionQueryImpl Key: GORA-275 URL: https://issues.apache.org/jira/browse/GORA-275 Project: Apache Gora Issue Type: Bug Components: gora-accumulo, gora-cassandra, gora-core, gora-hbase Reporter: Henry Saputra Assignee: Damien Raude-Morvan Labels: patch Fix For: 0.4 Attachments: 0001-GORA-275-Update-Gora-stores-to-pass-conf-when-creati.patch This is needed as part of fix for GORA-270 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-270) IOUtils static SerializationFactory field
[ https://issues.apache.org/jira/browse/GORA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-270: - Attachment: 0001-GORA-270-remove-static-reference-to-SerializationFac.patch IOUtils static SerializationFactory field - Key: GORA-270 URL: https://issues.apache.org/jira/browse/GORA-270 Project: Apache Gora Issue Type: Bug Components: gora-core Reporter: Damien Raude-Morvan Assignee: Damien Raude-Morvan Labels: mapreduce Attachments: 0001-GORA-270-remove-static-reference-to-SerializationFac.patch (From http://mail-archives.apache.org/mod_mbox/gora-dev/201308.mbox/%3CCAG50ZE_poN4C%2B%2B8t2xLZ3MoJVDMRo6nfW_Wygd%3D%3DeteF3jyLrw%40mail.gmail.com%3E) Right now, IOUtils keep a *static* reference to an SerializationFactory which is initialized on first call to writeObject() with a Configuration instance. Given Configuration is also stored in a static field of same class for latter usage. But in fact each call to IOUtils.writeObject() can have a different Configuration instance than previous one. In my personnal use case, I've multiple M/R jobs which use Gora M/R feature to process Persistent object but each job can work with a different datastore configuration (for instance, name of table/collection/colum family). If we keep a static reference to SerializationFactory (and so its Configuration reference), QueryBase#readFields will then create a DataStore with wrong Configuration (ie. using first DataStore/Configuration instead of new one) I've started working on this issue, and come up with a possible fix : https://github.com/drazzib/gora/compare/apache-gora-0.2.1...ioutils_static_conf - remove static SerializationFactory from IOUtils (will recreate it every time) - in PartitionQueryImpl and QueryBase now send *current* configuration to deserialize One linked fix, is that gora drivers needs to be updated to define Configuration instance in PartitionQueryImpl (like this https://github.com/drazzib/gora/commit/395f2e2ad50d524f42ecc563104c165fa0fa6f39 ). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-270) IOUtils static SerializationFactory field
[ https://issues.apache.org/jira/browse/GORA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741499#comment-13741499 ] Damien Raude-Morvan commented on GORA-270: -- Hi Henri, Yeah, I would like to try fixing this one. I've already a working patch for 0.2.1 release, I just need to rebase it on trunk. PS: I've already other contributions waiting :) I'm working gora-mongodb (see GORA-199). IOUtils static SerializationFactory field - Key: GORA-270 URL: https://issues.apache.org/jira/browse/GORA-270 Project: Apache Gora Issue Type: Bug Components: gora-core Reporter: Damien Raude-Morvan Labels: mapreduce (From http://mail-archives.apache.org/mod_mbox/gora-dev/201308.mbox/%3CCAG50ZE_poN4C%2B%2B8t2xLZ3MoJVDMRo6nfW_Wygd%3D%3DeteF3jyLrw%40mail.gmail.com%3E) Right now, IOUtils keep a *static* reference to an SerializationFactory which is initialized on first call to writeObject() with a Configuration instance. Given Configuration is also stored in a static field of same class for latter usage. But in fact each call to IOUtils.writeObject() can have a different Configuration instance than previous one. In my personnal use case, I've multiple M/R jobs which use Gora M/R feature to process Persistent object but each job can work with a different datastore configuration (for instance, name of table/collection/colum family). If we keep a static reference to SerializationFactory (and so its Configuration reference), QueryBase#readFields will then create a DataStore with wrong Configuration (ie. using first DataStore/Configuration instead of new one) I've started working on this issue, and come up with a possible fix : https://github.com/drazzib/gora/compare/apache-gora-0.2.1...ioutils_static_conf - remove static SerializationFactory from IOUtils (will recreate it every time) - in PartitionQueryImpl and QueryBase now send *current* configuration to deserialize One linked fix, is that gora drivers needs to be updated to define Configuration instance in PartitionQueryImpl (like this https://github.com/drazzib/gora/commit/395f2e2ad50d524f42ecc563104c165fa0fa6f39 ). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707285#comment-13707285 ] Damien Raude-Morvan commented on GORA-199: -- For the record, my current work is visible on Github : https://github.com/drazzib/gora/compare/apache:trunk...GORA_199 I've fixed another batch of issues, and now : --- Tests run: 39, Failures: 5, Errors: 4, Skipped: 0 --- Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Priority: Minor Labels: contrib Fix For: 0.4 Attachments: 0001-GORA-199-MongoDB-Support-in-Gora.patch, GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz, org.apache.gora.mongodb.store.TestMongoStore.txt Support 10gen MongoDB datastore in GORA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: GORA-199v3.patch Hi, I've updated gora-mongodb patch with somes fixes : - Add missing src/test/conf/gora.properties to avoid NullPointerException - Avoid crash in MongoDBQuery if missing fields - Start support of UNION (very early stage) - Fix behavior of schemaExists / schemaCreate Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Priority: Minor Labels: contrib Fix For: 0.4 Attachments: 0001-GORA-199-MongoDB-Support-in-Gora.patch, GORA-199.patch, GORA-199v2.patch, GORA-199v3.patch, gora-mongodb-src.tar.gz Support 10gen MongoDB datastore in GORA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: 0001-GORA-199-MongoDB-Support-in-Gora.patch Use git format-patch -1 --no-prefix to export patch from Git. Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Priority: Minor Labels: contrib Fix For: 0.4 Attachments: 0001-GORA-199-MongoDB-Support-in-Gora.patch, gora-mongodb-src.tar.gz Support 10gen MongoDB datastore in GORA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: (was: 0001-GORA-199-MongoDB-Support-in-Gora.patch) Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Priority: Minor Labels: contrib Fix For: 0.4 Attachments: 0001-GORA-199-MongoDB-Support-in-Gora.patch, gora-mongodb-src.tar.gz Support 10gen MongoDB datastore in GORA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien Raude-Morvan updated GORA-199: - Attachment: 0001-GORA-199-MongoDB-Support-in-Gora.patch Support for MongoDB in Gora Support MongoDB in GORA --- Key: GORA-199 URL: https://issues.apache.org/jira/browse/GORA-199 Project: Apache Gora Issue Type: New Feature Components: storage Affects Versions: 0.2.1 Reporter: Fabien Poulard Priority: Minor Labels: contrib Fix For: 0.4 Attachments: 0001-GORA-199-MongoDB-Support-in-Gora.patch, gora-mongodb-src.tar.gz Support 10gen MongoDB datastore in GORA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
