[jira] [Assigned] (GORA-112) Support Cascading

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-112:
--

Assignee: (was: Alfonso Nishikawa)

> Support Cascading
> -
>
> Key: GORA-112
> URL: https://issues.apache.org/jira/browse/GORA-112
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: storage
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Priority: Major
>  Labels: gsoc2013
> Fix For: 1.0
>
>
> It has been a long term goal for Gora to support tools which enable easier 
> data processing workflow implementations across Hadoop. Cascading is one of 
> the processing API's which has been on the radar for Gora from inception into 
> the Apache Incubator and would be an excellent addition to the project, 
> carving the way for adoption of Pig etc. Although it is obviously beneficial 
> to be able to think MapReduce, tools like Cascading are key to lowering the 
> barrier to adoption for Gora users who wish to utilise MR through the Gora 
> API.  
> Interested Mentors
> lewis john mcgibbney: lewismc at apache dot or
> interested students
> student name: student email



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (GORA-391) Arrays persisted in HBase don't shrink automatically

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-391:
---
Reporter: Alfonso Nishikawa Muñumer  (was: Alfonso Nishikawa)

> Arrays persisted in HBase don't shrink automatically
> 
>
> Key: GORA-391
> URL: https://issues.apache.org/jira/browse/GORA-391
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-hbase
>Affects Versions: 0.4, 0.5
>Reporter: Alfonso Nishikawa Muñumer
>Priority: Minor
>  Labels: arrays, maps
> Fix For: 1.0
>
>
> Fields defined as arrays can grow and be updated, but don't shrink when an 
> element is deleted.
> See the code involved: 
> [https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L312]
> The workaround is:
> # Define the field as a nullable array: ['null', ...array...]
> # Set the field to null and persist  -> the array will be deleted
> # Set the field to the new array and persist -> the array will be persisted 
> with the new size
> Comment from Renato:
> bq.You are right, the array can not be shrinked at the moment and yes, it is 
> wrong having to write the whole array back if you just want to change a 
> single element. The column qualifier used for each item is the original index 
> that means if your original array had 10 elements, then you'd have 10 column 
> qualfiers to store those 10 items. But if then you delete the third element, 
> Gora will end up with 9 actual elements (without the third), but there will 
> be a 10th element inside HBase :( and when modifying a specific element, we 
> will end up rewriting all of the elements :( Maybe we should do the same 
> thing, we do with the maps and rewrite them all into HBase. At least it will 
> work correctly.
> Maybe the best solution would be an adaptative persistency: if a big 
> percentage of the field is persisted, overwrite everything. If a small 
> percentage of the field is persisted, update in a diff maner (addings, 
> deletions, updates). This proposed approach seems too much complex, so the 
> solution to implement is the one found in maps: delete all elements and write 
> them again.
> {panel:bgColor=#CE} (!) This will be horrible with arrays with big 
> elements and only one update, but it is the same as it is being done by now. 
> Same for maps. {panel}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (GORA-391) Arrays persisted in HBase don't shrink automatically

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-391:
--

Assignee: (was: Alfonso Nishikawa)

> Arrays persisted in HBase don't shrink automatically
> 
>
> Key: GORA-391
> URL: https://issues.apache.org/jira/browse/GORA-391
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-hbase
>Affects Versions: 0.4, 0.5
>Reporter: Alfonso Nishikawa
>Priority: Minor
>  Labels: arrays, maps
> Fix For: 1.0
>
>
> Fields defined as arrays can grow and be updated, but don't shrink when an 
> element is deleted.
> See the code involved: 
> [https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L312]
> The workaround is:
> # Define the field as a nullable array: ['null', ...array...]
> # Set the field to null and persist  -> the array will be deleted
> # Set the field to the new array and persist -> the array will be persisted 
> with the new size
> Comment from Renato:
> bq.You are right, the array can not be shrinked at the moment and yes, it is 
> wrong having to write the whole array back if you just want to change a 
> single element. The column qualifier used for each item is the original index 
> that means if your original array had 10 elements, then you'd have 10 column 
> qualfiers to store those 10 items. But if then you delete the third element, 
> Gora will end up with 9 actual elements (without the third), but there will 
> be a 10th element inside HBase :( and when modifying a specific element, we 
> will end up rewriting all of the elements :( Maybe we should do the same 
> thing, we do with the maps and rewrite them all into HBase. At least it will 
> work correctly.
> Maybe the best solution would be an adaptative persistency: if a big 
> percentage of the field is persisted, overwrite everything. If a small 
> percentage of the field is persisted, update in a diff maner (addings, 
> deletions, updates). This proposed approach seems too much complex, so the 
> solution to implement is the one found in maps: delete all elements and write 
> them again.
> {panel:bgColor=#CE} (!) This will be horrible with arrays with big 
> elements and only one update, but it is the same as it is being done by now. 
> Same for maps. {panel}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Deleted] (GORA-695) MTGUIDE is

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa deleted GORA-695:
---


> MTGUIDE is
> --
>
> Key: GORA-695
> URL: https://issues.apache.org/jira/browse/GORA-695
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: mtgcommunity
>Priority: Major
>
> Hello, this is the best eat-and-dry verification company that strives for the 
> safety of our members.
>  
> 먹튀가이드 - [먹튀검증|https://mt-guide01.com], 먹튀검증 커뮤니티, 먹튀
>  
> You can join the safe Toto site through the eating guide. Our food guide 
> confirms the safety of the site to members by checking the details of reports 
> from members and incidents that occur in the industry. Take advantage of the 
> eat-and-run guide, the leader of the eat-and-run verification community! 
> Highly recommended!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-669:


Great, [~drazzib]! Thank you very much!! :D

> 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
>  Labels: github-pullrequest
> Fix For: 1.0
>
> Attachments: image-2020-10-30-22-40-24-419.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-669:


Hi, Damien.

Great job! :)
I think maybe would be good to create some Jira issue for the ignored tests?

About the pull request, +1 to merge it :) Thank you!!!
(sorry for the late response! :S)

> 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
>  Labels: github-pullrequest
> 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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-669:


Just sharing: at build #9 we have the MongoDB problem of this issue and 
afterwards we hit:

```
2020-10-31 18:52:10,773  DEBUG [jetty.server.HttpChannel] [qtp1413378318-37] 
REQUEST for 
//localhost:9876/solr/Employee/get?qt=%2Fget=name%2CdateOfBirth%2Cssn%2Csalary%2Cboss%2CRecording
 test results
FATAL: Failed to save the JUnit test result
java.io.IOException: No space left on device
```

> 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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-669:


Hi, [~drazzib]! Thank you! I tried to reproduce it locally from all the build 
and I got:

```---
Test set: org.apache.gora.infinispan.store.InfinispanStoreTest
---
Tests run: 46, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.918 s <<< 
FAILURE! - in org.apache.gora.infinispan.store.InfinispanStoreTest
testGetPartitions(org.apache.gora.infinispan.store.InfinispanStoreTest)  Time 
elapsed: 0.063 s  <<< ERROR!
java.lang.ClassCastException: org.apache.avro.util.Utf8 cannot be cast to 
java.lang.String
```

So I am taking a look too to all :S

> 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-666) Add support for the Kudu datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-666:


Merged https://github.com/apache/gora/pull/232 to master. Thank you, 
[~arqgabyortiz]!

> Add support for the Kudu datastore in GoraExplorer
> --
>
> Key: GORA-666
> URL: https://issues.apache.org/jira/browse/GORA-666
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>
> Add support for the Kudu datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Resolved] (GORA-666) Add support for the Kudu datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-666.

Resolution: Fixed

> Add support for the Kudu datastore in GoraExplorer
> --
>
> Key: GORA-666
> URL: https://issues.apache.org/jira/browse/GORA-666
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>
> Add support for the Kudu datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Updated] (GORA-666) Add support for the Kudu datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-666:
---
Fix Version/s: 1.0

> Add support for the Kudu datastore in GoraExplorer
> --
>
> Key: GORA-666
> URL: https://issues.apache.org/jira/browse/GORA-666
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>
> Add support for the Kudu datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Commented] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-455:


Merged [~arqgabyortiz]'s https://github.com/apache/gora/pull/227 implementing 
the XSD and validation (opt-in with gora.xsd_validation property) for 
gora-lucene.
(we will have to remember to update Gora's documentation once all datastores 
have the feature)

> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Resolved] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-557.

Resolution: Fixed

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Commented] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-557:


Merged https://github.com/apache/gora/pull/231 to master. Thank you, 
[~mariia.podorvanova]!

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Updated] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-557:
---
Fix Version/s: 1.0

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Commented] (GORA-199) Support MongoDB in GORA

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-199:


Hi, [~drazzib]. Noticed now that the "OBJECT_ID" type is written in the 
mappings as "OBJECTID". Is there a reason behind, is it a typo, or MongoDB 
changed the type name?
Thank you!!

> 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
(v8.3.4#803005)

[jira] [Updated] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-669:
---
Description: 
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! 

  was:
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 millenia, 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! 


> 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
>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] [Updated] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-669:
---
Description: 
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 millenia, 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! 

  was:
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.

 !image-2020-10-30-22-40-24-419.png|thumbnail! 


> 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
>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 millenia, 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] [Created] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gests stuck never ending

[Alfonso Nishikawa (Jira)]

Alfonso Nishikawa created GORA-669:
--

 Summary: MongoDB SCRAM_SHA_1_AuthenticationTest gests 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
 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.

 !image-2020-10-30-22-40-24-419.png|thumbnail! 



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

[jira] [Updated] (GORA-669) MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-669:
---
Summary: MongoDB SCRAM_SHA_1_AuthenticationTest gets stuck never ending  
(was: MongoDB SCRAM_SHA_1_AuthenticationTest gests stuck never ending)

> 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
>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.
>  !image-2020-10-30-22-40-24-419.png|thumbnail! 



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

[jira] [Commented] (GORA-665) Add support for the Ignite datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-665:


Merged to master. Thank you, [~arqgabyortiz]!

> Add support for the Ignite datastore in GoraExplorer
> 
>
> Key: GORA-665
> URL: https://issues.apache.org/jira/browse/GORA-665
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add support for the Ignite datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Resolved] (GORA-665) Add support for the Ignite datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-665.

Resolution: Fixed

> Add support for the Ignite datastore in GoraExplorer
> 
>
> Key: GORA-665
> URL: https://issues.apache.org/jira/browse/GORA-665
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add support for the Ignite datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Updated] (GORA-665) Add support for the Ignite datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-665:
---
Fix Version/s: 1.0

> Add support for the Ignite datastore in GoraExplorer
> 
>
> Key: GORA-665
> URL: https://issues.apache.org/jira/browse/GORA-665
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add support for the Ignite datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Resolved] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-667.

Resolution: Fixed

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Updated] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-667:
---
Fix Version/s: 1.0

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Commented] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-667:


Merged. Thank you, [~mariia.podorvanova]!

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Commented] (GORA-430) Address use of deprecated API's

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-430:


This issue seems merged. I will close it.

[~milorodrigues97]: you have to write to dev@gora.apache.org

> Address use of deprecated API's
> ---
>
> Key: GORA-430
> URL: https://issues.apache.org/jira/browse/GORA-430
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process
>Affects Versions: 0.6.1
>Reporter: Lewis John McGibbney
>Assignee: Mariia Podorvanova
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> We use deprecated API's in a number of places. Maven highlights this and it 
> is present in the build output.
> We could address this in the 0.7 development drive.



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

[jira] [Resolved] (GORA-430) Address use of deprecated API's

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-430.

Resolution: Fixed

> Address use of deprecated API's
> ---
>
> Key: GORA-430
> URL: https://issues.apache.org/jira/browse/GORA-430
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process
>Affects Versions: 0.6.1
>Reporter: Lewis John McGibbney
>Assignee: Mariia Podorvanova
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> We use deprecated API's in a number of places. Maven highlights this and it 
> is present in the build output.
> We could address this in the 0.7 development drive.



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

[jira] [Assigned] (GORA-430) Address use of deprecated API's

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-430:
--

Assignee: Mariia Podorvanova

> Address use of deprecated API's
> ---
>
> Key: GORA-430
> URL: https://issues.apache.org/jira/browse/GORA-430
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process
>Affects Versions: 0.6.1
>Reporter: Lewis John McGibbney
>Assignee: Mariia Podorvanova
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> We use deprecated API's in a number of places. Maven highlights this and it 
> is present in the build output.
> We could address this in the 0.7 development drive.



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

[jira] [Assigned] (GORA-665) Add support for the Ignite datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-665:
--

Assignee: Gaby Ortiz

> Add support for the Ignite datastore in GoraExplorer
> 
>
> Key: GORA-665
> URL: https://issues.apache.org/jira/browse/GORA-665
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add support for the Ignite datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-562:
--

Assignee: Nilothpal Pillai

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



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

[jira] [Assigned] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-455:
--

Assignee: Gaby Ortiz

> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Assignee: Gaby Ortiz
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Assigned] (GORA-338) Complete site documentation for gora-dynamodb

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-338:
--

Assignee: Nilothpal Pillai

> Complete site documentation for gora-dynamodb
> -
>
> Key: GORA-338
> URL: https://issues.apache.org/jira/browse/GORA-338
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation, gora-dynamodb
>Affects Versions: 0.4
>Reporter: Lewis John McGibbney
>Assignee: Nilothpal Pillai
>Priority: Major
> Fix For: 1.0
>
> Attachments: dynamodb-backend.patch
>
>
> We need to substantiate the site docs which currently reside at 
> http://gora.apache.org/current/gora-dynamodb.html
> We should most likely also provide a page for dynamodb compiler



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

[jira] [Assigned] (GORA-666) Add support for the Kudu datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-666:
--

Assignee: Gaby Ortiz

> Add support for the Kudu datastore in GoraExplorer
> --
>
> Key: GORA-666
> URL: https://issues.apache.org/jira/browse/GORA-666
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Assignee: Gaby Ortiz
>Priority: Major
>
> Add support for the Kudu datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Commented] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-557:


Hi, [~mariia.podorvanova].

Here is some documentation about the metadata analyzer: 
https://translate.google.com/translate?sl=es=en=https://redmine.nishilua.com/projects/goraexplorer/wiki/Obtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas
 (I Googletranslated it from Spanish).
One of the constructors of DataStoreMetadataFactory receives a Properties 
(that, probably, will be gora.properties or set by code), and as you say, 
DataStoreMetadataAnalyzer does not seems to have that field. Probably you have 
a good reason to add that field at DataStoreMetadataAnalyzer and populate it 
when the factory instantiates a MongoDB analyzer :)


> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Commented] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-557:


Hi, [~mariia.podorvanova].

What do you refer exactly as "the second task of the ticket"? The second bullet 
point or "A plus would be implement the support in GoraExplorer so it will be 
possible to manage MongoDB data visually"?

If it is the "blahblahblah data visually", when creating a connection there is 
a "hadoop configuration" option that you can ignore. It is there because HBase 
uses a file hbase-site.xml configuration that is hadoop-style, but if mongodb 
only needs gora.properties, that is configured when creating a connection too.

The issue is that GoraExplorer does not support mongodb.
If you want to implement that part, you can take a look at what [~arqgabyortiz] 
has been doing: 
https://bitbucket.org/alfonsonishikawa/goraexplorer/pull-requests/1/add-support-for-the-ignite-datastore-in/diff#comment-184402931

Here is how to prepare the development environment: 
https://bitbucket.org/alfonsonishikawa/goraexplorer/wiki/Building
Here is a video list on what is GoraExplorer (development): 
https://www.youtube.com/watch?v=TTtoRh5aaDI=PLfaBSywymrO86u9SOqRCwGB6bz5ru1al7
And here is a live demo of the application: 
https://www.goraexplorer.com/livedemo/

Know that GoraExplorer is an independen project different from Apache Gora!


> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Resolved] (GORA-338) Complete site documentation for gora-dynamodb

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-338.

Resolution: Fixed

> Complete site documentation for gora-dynamodb
> -
>
> Key: GORA-338
> URL: https://issues.apache.org/jira/browse/GORA-338
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation, gora-dynamodb
>Affects Versions: 0.4
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
> Attachments: dynamodb-backend.patch
>
>
> We need to substantiate the site docs which currently reside at 
> http://gora.apache.org/current/gora-dynamodb.html
> We should most likely also provide a page for dynamodb compiler



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

[jira] [Assigned] (GORA-338) Complete site documentation for gora-dynamodb

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-338:
--

Assignee: (was: Lewis John McGibbney)

> Complete site documentation for gora-dynamodb
> -
>
> Key: GORA-338
> URL: https://issues.apache.org/jira/browse/GORA-338
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation, gora-dynamodb
>Affects Versions: 0.4
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
> Attachments: dynamodb-backend.patch
>
>
> We need to substantiate the site docs which currently reside at 
> http://gora.apache.org/current/gora-dynamodb.html
> We should most likely also provide a page for dynamodb compiler



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

[jira] [Commented] (GORA-338) Complete site documentation for gora-dynamodb

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-338:


Commited the patch with the documentation for gora-dynamodb. The updated page 
can be seen at http://gora.apache.org/current/gora-dynamodb.html
Thanks [~Nilo] for the patch.

> Complete site documentation for gora-dynamodb
> -
>
> Key: GORA-338
> URL: https://issues.apache.org/jira/browse/GORA-338
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation, gora-dynamodb
>Affects Versions: 0.4
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
> Attachments: dynamodb-backend.patch
>
>
> We need to substantiate the site docs which currently reside at 
> http://gora.apache.org/current/gora-dynamodb.html
> We should most likely also provide a page for dynamodb compiler



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

[jira] [Commented] (GORA-666) Add support for the Kudu datastore in GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-666:


Hi, [~arqgabyortiz].
Yes, there are something missing for Gora Kudu support. There are some classes 
that retrieve native information from the underlying datastore that at this 
moment only is implemented for HBase. Kudu is missing that feature.
GoraExplorer uses that native information to help creating mappings with a 
Wizard (and it is specific for each datastore).
Here is some documentation about it: 
https://redmine.nishilua.com/projects/goraexplorer/wiki/Obtenci%C3%B3n_de_metadatos_de_las_BBDD_nativas
 (it is in spanish, but I suspect you won't have any issue with it ;P)
Probably it is not the best design :( I made it in quite a hurry. If you see 
anything improvable, let me know :)

> Add support for the Kudu datastore in GoraExplorer
> --
>
> Key: GORA-666
> URL: https://issues.apache.org/jira/browse/GORA-666
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: John Mora
>Priority: Major
>
> Add support for the Kudu datastore in GoraExplorer - 
> https://www.goraexplorer.com/



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

[jira] [Commented] (GORA-338) Complete site documentation for gora-dynamodb

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-338:


Hi, [~Nilo]. I don't know much about gora-dynamodb, so I would be grateful if 
someone could review your documentation proposal. My memory says me that maybe 
[~rmarroquin] | [~renato2099] can review it.
In any case I will try tomorrow to take a look at it.
Thank you!

> Complete site documentation for gora-dynamodb
> -
>
> Key: GORA-338
> URL: https://issues.apache.org/jira/browse/GORA-338
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation, gora-dynamodb
>Affects Versions: 0.4
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
> Attachments: dynamodb-backend.patch
>
>
> We need to substantiate the site docs which currently reside at 
> http://gora.apache.org/current/gora-dynamodb.html
> We should most likely also provide a page for dynamodb compiler



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

[jira] [Commented] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-455:


Hi, [~arqgabyortiz]. Your approach seems good too, then :)
About the local loading, I really don't know what [~lewismc] had in mind when 
he created the issue (if any deeper idea), but I believe that it could be 
important to make opt-in/out configuration options when the validation could 
affect the performance or halt completely a computation on internet 
failure/indisponibility if the XSDs are referenced by URI and stored in gora 
website. I am not much into XSD, so Iet's see what [~lewismc] comments about 
the URI's :)

> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Commented] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-455:


Hi, Gaby.

I don't really know much about this issue, but in order to accept a pull 
request it should be a completed feature :)

I have some questions too (and some maybe [~lewismc] can answer them):

- What happens when a validation fails? Does it throws a Runtime Exception? 
Then that should be wrapped in a GoraException
- What happens if there is no internet connection to download the XSD? Or what 
happens if there is a firewall dropping the requests and the validation have to 
wait for a timeout? A server probably can't wait forever or several minutes for 
a validation if it has some jobs queued...
- Should the validation be enabled/disabled on demand?
- From where can the XSD be loaded? Only from a URI or from resources too as in 
the test?

Thank you! :)

> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Commented] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-455:


[~baibask]: Hi, Baiba. Are you talking about this specific task, GORA-455? 
Otherwise you have to write to dev@gora.apache.org :)

> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Commented] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-667:


Hi, [~Nilo]. Thank you for confirming it is failing!

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Commented] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-667:


Hi, [~mariia.podorvanova],
I was working on it but infinispan tests doesn't pass to me (not related to the 
fix) :(
Of course, you can fix it, maybe the tests work for you :) I asssign the issue 
to you. Thank you!! :)

Let us know if you face any problem (maybe gora-hive tests don't pass either).

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
>Priority: Minor
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Assigned] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-667:
--

Assignee: Mariia Podorvanova  (was: Alfonso Nishikawa)

> Revert GORA-271 changes in hbase-store that disabled the mapping loading from 
> configuration
> ---
>
> Key: GORA-667
> URL: https://issues.apache.org/jira/browse/GORA-667
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>
> The pull request information and comment is here: 
> https://github.com/apache/gora/pull/170



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

[jira] [Created] (GORA-667) Revert GORA-271 changes in hbase-store that disabled the mapping loading from configuration

[Alfonso Nishikawa (Jira)]

Alfonso Nishikawa created GORA-667:
--

 Summary: Revert GORA-271 changes in hbase-store that disabled the 
mapping loading from configuration
 Key: GORA-667
 URL: https://issues.apache.org/jira/browse/GORA-667
 Project: Apache Gora
  Issue Type: Bug
Reporter: Alfonso Nishikawa
Assignee: Alfonso Nishikawa


The pull request information and comment is here: 
https://github.com/apache/gora/pull/170



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

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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa edited comment on GORA-562 at 10/19/20, 7:30 PM:
---

Hi, [~Nilo].
I see your failing PR at https://github.com/apache/gora/pull/225
First, though unrelated to failing, is that you have to put {{gora.bat}} in 
{{/bin}}.

One personal question I have is what is the difference between {{.bat}} and 
{{.cmd}}? Is one more suitable or interesting than the other? (I am not a 
Windows user).

The failing in compiling doesn't look to be related to you, but to gora-hive 
(not related to you):

{noformat}
2020-10-19T07:18:28.0988578Z [INFO] 

2020-10-19T07:18:28.0990012Z [INFO] Reactor Summary for Apache Gora 
1.0-SNAPSHOT:
2020-10-19T07:18:28.0990641Z [INFO] 
2020-10-19T07:18:28.0991093Z [INFO] Apache Gora 
 SUCCESS [ 10.543 s]
2020-10-19T07:18:28.0992012Z [INFO] Apache Gora :: Compiler 
 SUCCESS [  3.023 s]
2020-10-19T07:18:28.0993140Z [INFO] Apache Gora :: Compiler-CLI 
 SUCCESS [  1.250 s]
2020-10-19T07:18:28.0993832Z [INFO] Apache Gora :: Core 
 SUCCESS [01:35 min]
2020-10-19T07:18:28.0994366Z [INFO] Apache Gora :: Pig 
. SUCCESS [  5.308 s]
2020-10-19T07:18:28.0994944Z [INFO] Apache Gora :: Accumulo 
 SUCCESS [07:42 min]
2020-10-19T07:18:28.0995538Z [INFO] Apache Gora :: HBase 
... SUCCESS [03:56 min]
2020-10-19T07:18:28.0996537Z [INFO] Apache Gora :: Cassandra - CQL 
. SUCCESS [01:46 min]
2020-10-19T07:18:28.0997545Z [INFO] Apache Gora :: GoraCI 
.. SUCCESS [ 26.665 s]
2020-10-19T07:18:28.0998148Z [INFO] Apache Gora :: Infinispan 
.. SUCCESS [01:32 min]
2020-10-19T07:18:28.0998748Z [INFO] Apache Gora :: JCache 
.. SUCCESS [01:12 min]
2020-10-19T07:18:28.0999344Z [INFO] Apache Gora :: OrientDB 
 SUCCESS [02:19 min]
2020-10-19T07:18:28.040Z [INFO] Apache Gora :: Lucene 
.. SUCCESS [ 11.040 s]
2020-10-19T07:18:28.1000518Z [INFO] Apache Gora :: Dynamodb 
 SUCCESS [ 10.157 s]
2020-10-19T07:18:28.1001108Z [INFO] Apache Gora :: CouchDB 
. SUCCESS [ 47.071 s]
2020-10-19T07:18:28.1001696Z [INFO] Apache Gora :: Maven Plugin 
 SUCCESS [  5.059 s]
2020-10-19T07:18:28.1002283Z [INFO] Apache Gora :: MongoDB 
. SUCCESS [02:15 min]
2020-10-19T07:18:28.1002929Z [INFO] Apache Gora :: Solr 
 SUCCESS [07:10 min]
2020-10-19T07:18:28.1003518Z [INFO] Apache Gora :: Aerospike 
... SUCCESS [  4.917 s]
2020-10-19T07:18:28.1004104Z [INFO] Apache Gora :: Ignite 
.. SUCCESS [01:18 min]
2020-10-19T07:18:28.1004667Z [INFO] Apache Gora :: Kudu 
 SUCCESS [  6.873 s]
2020-10-19T07:18:28.1005580Z [INFO] Apache Gora :: Hive 
 FAILURE [15:36 min]
2020-10-19T07:18:28.1007085Z [INFO] Apache Gora :: Redis 
... SKIPPED
2020-10-19T07:18:28.1007504Z [INFO] Apache Gora :: Jet 
. SKIPPED
2020-10-19T07:18:28.1007944Z [INFO] Apache Gora :: RethinkDB 
... SKIPPED
2020-10-19T07:18:28.1008401Z [INFO] Apache Gora :: Tutorial 
 SKIPPED
2020-10-19T07:18:28.1008882Z [INFO] Apache Gora Benchamark Module 
.. SKIPPED
2020-10-19T07:18:28.1009938Z [INFO] Apache Gora :: Sources-Dist 
 SKIPPED
2020-10-19T07:18:28.1010533Z [INFO] 

2020-10-19T07:18:28.1010839Z [INFO] BUILD FAILURE
2020-10-19T07:18:28.1011330Z [INFO] 



2020-10-19T07:18:27.5767403Z [ERROR] 
testPutArray(org.apache.gora.hive.store.TestHiveStore)  Time elapsed: 0.483 s  
<<< ERROR!
{noformat}

In fact, merged GORA-655 is failing 
(https://github.com/apache/gora/commit/dff7b93dc68bf9cfaeb1296135eaf3a862117384 
[~Madhawa Gunasekara]), so gora master is broken too, not you :)





was (Author: alfonso.nishikawa):
Hi, [~Nilo].
I see your failing PR at https://github.com/apache/gora/pull/225
First, though unrelated to failing, is that you have to put {{gora.bat}} in 
{{/bin}}.

One personal question I have is what is the difference between {{.bat}} and 
{{.cmd}}? Is one more suitable or interesting than the other? (I am not a 
Windows user).

The failing in compiling doesn't look to be related 

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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-562:


Hi, [~Nilo].
I see your failing PR at https://github.com/apache/gora/pull/225
First, though unrelated to failing, is that you have to put {{gora.bat}} in 
{{/bin}}.

One personal question I have is what is the difference between {{.bat}} and 
{{.cmd}}? Is one more suitable or interesting than the other? (I am not a 
Windows user).

The failing in compiling doesn't look to be related to you, but to gora-hive 
(not related to you):

{noformat}
2020-10-19T07:18:28.0988578Z [INFO] 

2020-10-19T07:18:28.0990012Z [INFO] Reactor Summary for Apache Gora 
1.0-SNAPSHOT:
2020-10-19T07:18:28.0990641Z [INFO] 
2020-10-19T07:18:28.0991093Z [INFO] Apache Gora 
 SUCCESS [ 10.543 s]
2020-10-19T07:18:28.0992012Z [INFO] Apache Gora :: Compiler 
 SUCCESS [  3.023 s]
2020-10-19T07:18:28.0993140Z [INFO] Apache Gora :: Compiler-CLI 
 SUCCESS [  1.250 s]
2020-10-19T07:18:28.0993832Z [INFO] Apache Gora :: Core 
 SUCCESS [01:35 min]
2020-10-19T07:18:28.0994366Z [INFO] Apache Gora :: Pig 
. SUCCESS [  5.308 s]
2020-10-19T07:18:28.0994944Z [INFO] Apache Gora :: Accumulo 
 SUCCESS [07:42 min]
2020-10-19T07:18:28.0995538Z [INFO] Apache Gora :: HBase 
... SUCCESS [03:56 min]
2020-10-19T07:18:28.0996537Z [INFO] Apache Gora :: Cassandra - CQL 
. SUCCESS [01:46 min]
2020-10-19T07:18:28.0997545Z [INFO] Apache Gora :: GoraCI 
.. SUCCESS [ 26.665 s]
2020-10-19T07:18:28.0998148Z [INFO] Apache Gora :: Infinispan 
.. SUCCESS [01:32 min]
2020-10-19T07:18:28.0998748Z [INFO] Apache Gora :: JCache 
.. SUCCESS [01:12 min]
2020-10-19T07:18:28.0999344Z [INFO] Apache Gora :: OrientDB 
 SUCCESS [02:19 min]
2020-10-19T07:18:28.040Z [INFO] Apache Gora :: Lucene 
.. SUCCESS [ 11.040 s]
2020-10-19T07:18:28.1000518Z [INFO] Apache Gora :: Dynamodb 
 SUCCESS [ 10.157 s]
2020-10-19T07:18:28.1001108Z [INFO] Apache Gora :: CouchDB 
. SUCCESS [ 47.071 s]
2020-10-19T07:18:28.1001696Z [INFO] Apache Gora :: Maven Plugin 
 SUCCESS [  5.059 s]
2020-10-19T07:18:28.1002283Z [INFO] Apache Gora :: MongoDB 
. SUCCESS [02:15 min]
2020-10-19T07:18:28.1002929Z [INFO] Apache Gora :: Solr 
 SUCCESS [07:10 min]
2020-10-19T07:18:28.1003518Z [INFO] Apache Gora :: Aerospike 
... SUCCESS [  4.917 s]
2020-10-19T07:18:28.1004104Z [INFO] Apache Gora :: Ignite 
.. SUCCESS [01:18 min]
2020-10-19T07:18:28.1004667Z [INFO] Apache Gora :: Kudu 
 SUCCESS [  6.873 s]
2020-10-19T07:18:28.1005580Z [INFO] Apache Gora :: Hive 
 FAILURE [15:36 min]
2020-10-19T07:18:28.1007085Z [INFO] Apache Gora :: Redis 
... SKIPPED
2020-10-19T07:18:28.1007504Z [INFO] Apache Gora :: Jet 
. SKIPPED
2020-10-19T07:18:28.1007944Z [INFO] Apache Gora :: RethinkDB 
... SKIPPED
2020-10-19T07:18:28.1008401Z [INFO] Apache Gora :: Tutorial 
 SKIPPED
2020-10-19T07:18:28.1008882Z [INFO] Apache Gora Benchamark Module 
.. SKIPPED
2020-10-19T07:18:28.1009938Z [INFO] Apache Gora :: Sources-Dist 
 SKIPPED
2020-10-19T07:18:28.1010533Z [INFO] 

2020-10-19T07:18:28.1010839Z [INFO] BUILD FAILURE
2020-10-19T07:18:28.1011330Z [INFO] 



2020-10-19T07:18:27.5767403Z [ERROR] 
testPutArray(org.apache.gora.hive.store.TestHiveStore)  Time elapsed: 0.483 s  
<<< ERROR!
{noformat}

In fact, meged GORA-655 is failing 
(https://github.com/apache/gora/commit/dff7b93dc68bf9cfaeb1296135eaf3a862117384 
[~Madhawa Gunasekara]), so gora master is broken too, not you :)




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

[jira] [Commented] (GORA-455) Create XSD's for all datastore xml mapping files

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-455:


Hi,

As I see the XML mappings, they are the connection point between the abstract 
data model and the specific database implementation, so it needs to have the 
details of the DB underneath.
For that, each DB mapping should have its own tags. Of course all the common 
features should be the same, but what in one DB is a "column" in other could be 
called a "field", or some DBs  have some optional configurations.
So, I would say that should be created one XSD per DB.

Regards,

Alfonso Nishikawa


> Create XSD's for all datastore xml mapping files
> 
>
> Key: GORA-455
> URL: https://issues.apache.org/jira/browse/GORA-455
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: schema
>Affects Versions: 0.7
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> When creating new mappings it would be great to have XSD's to comply with. If 
> our XSD's also had URI's then it would be very easy to streamline the 
> generation of XML mappings.



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

[jira] [Commented] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-557:


Hi, [~mariia.podorvanova]. Thank you for noticing it. I believe there was some 
misunderstanding in GORA-271. Let's put this on hold until we clarify it.

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Commented] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-557:


Hi, Maria! Great! Thank you very much and welcome!

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

[jira] [Assigned] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa reassigned GORA-557:
--

Assignee: Mariia Podorvanova

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Assignee: Mariia Podorvanova
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



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

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

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-562:


Hi, [~Nilo]!
Welcome :)
I don't know why I can't assing the issue to you :/ [~djkevincr], can you 
assign this issue?
I created the issue because someone talked about this, but you are right: it is 
about creating the gora.bat and/or gora.cmd and assure it works :) Try 
compiling Gora in Windows and afterwards compile an avro schema into a 
Persistent entity (like the ones in the tutorial).
I have no much information since I am not a Windows user n_nU

Thanks to you :)

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



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

[jira] [Resolved] (GORA-636) Kudu unit tests are failing on Jenkins build

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-636.

Resolution: Fixed

> Kudu unit tests are failing on Jenkins build
> 
>
> Key: GORA-636
> URL: https://issues.apache.org/jira/browse/GORA-636
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>
> [INFO] -< org.apache.gora:gora-kudu 
> >--
> [INFO] Building Apache Gora :: Kudu 1.0-SNAPSHOT
> [21/24]
> [INFO] ---[ bundle 
> ]---
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
>  (3.1 kB at 32 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
>  (3.8 kB at 180 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
>  (777 B at 9.2 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
>  (1.9 kB at 117 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
>  (18 kB at 502 kB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
>  (9.8 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
>  (10 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
>  (23 MB at 18 MB/s)
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-kudu ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.7:add-source (default) @ gora-kudu ---
> [INFO] Source directory: 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/examples/java 
> added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/main/resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/test-classes
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ gora-kudu ---
> [WARNING] The parameter forkMode is deprecated since version 2.14. Use 
> forkCount and reuseForks instead.
> [INFO] 
> [INFO] 

[jira] [Commented] (GORA-636) Kudu unit tests are failing on Jenkins build

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-636:


Chrony installe on the Jenkins nodes with Ubuntu 18.04. It seems Ubuntu changed 
something about ntp, like in my  personal 18.04.
The error should not keep happening :)

> Kudu unit tests are failing on Jenkins build
> 
>
> Key: GORA-636
> URL: https://issues.apache.org/jira/browse/GORA-636
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>
> [INFO] -< org.apache.gora:gora-kudu 
> >--
> [INFO] Building Apache Gora :: Kudu 1.0-SNAPSHOT
> [21/24]
> [INFO] ---[ bundle 
> ]---
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
>  (3.1 kB at 32 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
>  (3.8 kB at 180 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
>  (777 B at 9.2 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
>  (1.9 kB at 117 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
>  (18 kB at 502 kB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
>  (9.8 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
>  (10 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
>  (23 MB at 18 MB/s)
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-kudu ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.7:add-source (default) @ gora-kudu ---
> [INFO] Source directory: 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/examples/java 
> added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/main/resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/test-classes
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ 

[jira] [Commented] (GORA-635) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-635:


Hi, Clayson.
Would be great if you detail a more your fixing steps. Thank you!

> Gora - Main Build problem
> -
>
> Key: GORA-635
> URL: https://issues.apache.org/jira/browse/GORA-635
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process, gora-compiler
>Affects Versions: 0.8
> Environment: Lunix Debina 9  updated to last release before version 
> 10 all stable, 
> Java, Maven, Git all in place. 
>Reporter: Cleyson Barros
>Priority: Blocker
>
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# ls
> bin gora-accumulo gora-cassandra-cql gora-core gora-goraci gora-infinispan 
> gora-mongodb gora-solr-5 KEYS pom.xml release.properties
> CHANGES.md gora-aerospike gora-compiler gora-couchdb gora-gradle-plugin 
> gora-jcache gora-orientdb gora-sql LICENSE.md pom.xml.releaseBackup 
> sources-dist
> conf gora-cassandra gora-compiler-cli gora-dynamodb gora-hbase 
> gora-maven-plugin gora-solr gora-tutorial NOTICE.md README.md
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.8
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
>  (13 KB at 8.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
>  (11 KB at 71.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
>  (63 KB at 428.3 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
>  (20 KB at 215.5 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
>  (13 KB at 141.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
>  (112 KB at 905.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
>  (5 KB at 58.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
>  (13 KB at 154.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar
> Downloaded: 
> 

[jira] [Resolved] (GORA-634) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-634.

Resolution: Incomplete

> Gora - Main Build problem
> -
>
> Key: GORA-634
> URL: https://issues.apache.org/jira/browse/GORA-634
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-compiler
>Affects Versions: 0.9
> Environment: Debian 9 updated to last build before version 10
> Observation, GIT, MVN and all requirements are in place.  
>Reporter: Cleyson Barros
>Priority: Blocker
>  Labels: build
> Attachments: Gora9-Trap Compilation.txt
>
>
> root@hgclusterambari00:/home/ambari/gora# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Pig
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Lucene
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Ignite
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora ---
> [INFO] Deleting /home/ambari/gora/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ gora 
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora ---
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ gora 
> ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ 
> gora ---
> [INFO] No site descriptor found: nothing to attach.
> [INFO]
> [INFO] --- maven-dependency-plugin:2.9:copy-dependencies (copy) @ gora ---
> [INFO]
> [INFO] --- forbiddenapis:2.0:check (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- forbiddenapis:2.0:testCheck (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ gora ---
> [INFO] Installing /home/ambari/gora/pom.xml to 
> /root/.m2/repository/org/apache/gora/gora/0.9/gora-0.9.pom
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora :: Compiler 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-compiler ---
> [INFO] Deleting /home/ambari/gora/gora-compiler/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-compiler ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-compiler ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-compiler ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> gora-compiler ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to 
> /home/ambari/gora/gora-compiler/target/classes
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the 
> environment.
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Gora  SUCCESS [ 9.093 s]
> [INFO] Apache Gora :: Compiler  FAILURE [ 2.237 s]
> [INFO] Apache Gora :: Compiler-CLI  SKIPPED
> [INFO] Apache Gora :: Core  SKIPPED
> [INFO] Apache Gora :: Pig . SKIPPED
> [INFO] Apache Gora :: Accumulo  SKIPPED
> [INFO] Apache Gora :: HBase ... SKIPPED
> [INFO] Apache Gora :: Cassandra - CQL . SKIPPED
> [INFO] Apache Gora :: GoraCI 

[jira] [Commented] (GORA-636) Kudu unit tests are failing on Jenkins build

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-636:


I opened the issue INFRA-18995 to see if they can address it.

> Kudu unit tests are failing on Jenkins build
> 
>
> Key: GORA-636
> URL: https://issues.apache.org/jira/browse/GORA-636
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>
> [INFO] -< org.apache.gora:gora-kudu 
> >--
> [INFO] Building Apache Gora :: Kudu 1.0-SNAPSHOT
> [21/24]
> [INFO] ---[ bundle 
> ]---
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
>  (3.1 kB at 32 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
>  (3.8 kB at 180 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
>  (777 B at 9.2 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
>  (1.9 kB at 117 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
>  (18 kB at 502 kB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
>  (9.8 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
>  (10 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
>  (23 MB at 18 MB/s)
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-kudu ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.7:add-source (default) @ gora-kudu ---
> [INFO] Source directory: 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/examples/java 
> added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/main/resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/test-classes
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ gora-kudu ---
> [WARNING] The parameter forkMode is deprecated since version 2.14. Use 
> forkCount and reuseForks 

[jira] [Commented] (GORA-636) Kudu unit tests are failing on Jenkins build

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-636:


Something alike happened to me on my own computer. I had to execute on Ubuntu:

{code:java}
sudo apt-get install chrony
systemctl enable chrony
{code}

I guess maybe the Jenkins machines don't have that package installed.

> Kudu unit tests are failing on Jenkins build
> 
>
> Key: GORA-636
> URL: https://issues.apache.org/jira/browse/GORA-636
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Reporter: Kevin Ratnasekera
>Priority: Major
> Fix For: 1.0
>
>
> [INFO] -< org.apache.gora:gora-kudu 
> >--
> [INFO] Building Apache Gora :: Kudu 1.0-SNAPSHOT
> [21/24]
> [INFO] ---[ bundle 
> ]---
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.pom
>  (3.1 kB at 32 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.pom
>  (3.8 kB at 180 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0.pom
>  (777 B at 9.2 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.pom
>  (1.9 kB at 117 kB/s)
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
> [INFO] Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/com/stumbleupon/async/1.4.1/async-1.4.1.jar
>  (18 kB at 502 kB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-client/1.9.0/kudu-client-1.9.0.jar
>  (9.8 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-test-utils/1.9.0/kudu-test-utils-1.9.0.jar
>  (10 MB at 17 MB/s)
> [INFO] Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/kudu/kudu-binary/1.9.0/kudu-binary-1.9.0-linux-x86_64.jar
>  (23 MB at 18 MB/s)
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-kudu ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.7:add-source (default) @ gora-kudu ---
> [INFO] Source directory: 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/examples/java 
> added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-kudu ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/src/main/resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ gora-kudu ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> gora-kudu ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-kudu/target/test-classes
> [INFO] 
> [INFO] --- 

[jira] [Resolved] (GORA-635) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-635.

Resolution: Duplicate

Sees to be duplicated of GORA-634, although different "Affects Version", proven 
to fail with Gora 0.9 in GORA-634.

> Gora - Main Build problem
> -
>
> Key: GORA-635
> URL: https://issues.apache.org/jira/browse/GORA-635
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process, gora-compiler
>Affects Versions: 0.8
> Environment: Lunix Debina 9  updated to last release before version 
> 10 all stable, 
> Java, Maven, Git all in place. 
>Reporter: Cleyson Barros
>Priority: Blocker
>
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# ls
> bin gora-accumulo gora-cassandra-cql gora-core gora-goraci gora-infinispan 
> gora-mongodb gora-solr-5 KEYS pom.xml release.properties
> CHANGES.md gora-aerospike gora-compiler gora-couchdb gora-gradle-plugin 
> gora-jcache gora-orientdb gora-sql LICENSE.md pom.xml.releaseBackup 
> sources-dist
> conf gora-cassandra gora-compiler-cli gora-dynamodb gora-hbase 
> gora-maven-plugin gora-solr gora-tutorial NOTICE.md README.md
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.8
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
>  (13 KB at 8.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
>  (11 KB at 71.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
>  (63 KB at 428.3 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
>  (20 KB at 215.5 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
>  (13 KB at 141.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
>  (112 KB at 905.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
>  (5 KB at 58.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
>  (13 KB at 154.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar
> Downloaded: 
> 

[jira] [Commented] (GORA-635) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-635:


Hi, [~eurocley]. No need to recreate the issue since it happens to you too with 
gora 0.9 and it is the same error. Please paste the output of executing {{javac 
-version}}. I will close this issue as duplicate by now (later, if it is not, 
we reopen it). Thank you!


> Gora - Main Build problem
> -
>
> Key: GORA-635
> URL: https://issues.apache.org/jira/browse/GORA-635
> Project: Apache Gora
>  Issue Type: Bug
>  Components: build process, gora-compiler
>Affects Versions: 0.8
> Environment: Lunix Debina 9  updated to last release before version 
> 10 all stable, 
> Java, Maven, Git all in place. 
>Reporter: Cleyson Barros
>Priority: Blocker
>
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# ls
> bin gora-accumulo gora-cassandra-cql gora-core gora-goraci gora-infinispan 
> gora-mongodb gora-solr-5 KEYS pom.xml release.properties
> CHANGES.md gora-aerospike gora-compiler gora-couchdb gora-gradle-plugin 
> gora-jcache gora-orientdb gora-sql LICENSE.md pom.xml.releaseBackup 
> sources-dist
> conf gora-cassandra gora-compiler-cli gora-dynamodb gora-hbase 
> gora-maven-plugin gora-solr gora-tutorial NOTICE.md README.md
> root@hgclusterambari00:/home/ambari/gora/apache-gora-0.8# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.8
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.pom
>  (13 KB at 8.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/19/maven-plugins-19.pom
>  (11 KB at 71.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.2.1/maven-remote-resources-plugin-1.2.1.jar
>  (63 KB at 428.3 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.pom
>  (20 KB at 215.5 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/21/maven-plugins-21.pom
>  (13 KB at 141.7 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
>  (112 KB at 905.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
>  (5 KB at 58.9 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom
>  (13 KB at 154.8 KB/sec)
> Downloading: 
> 

[jira] [Commented] (GORA-634) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-634:


Hi, [~eurocley]. You pasted the result from {{java -version}}, but I asked for 
{{javac -version}}. Can you paste the result of that other command? Thank you! 
:)

> Gora - Main Build problem
> -
>
> Key: GORA-634
> URL: https://issues.apache.org/jira/browse/GORA-634
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-compiler
>Affects Versions: 0.9
> Environment: Debian 9 updated to last build before version 10
> Observation, GIT, MVN and all requirements are in place.  
>Reporter: Cleyson Barros
>Priority: Blocker
>  Labels: build
> Attachments: Gora9-Trap Compilation.txt
>
>
> root@hgclusterambari00:/home/ambari/gora# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Pig
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Lucene
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Ignite
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora ---
> [INFO] Deleting /home/ambari/gora/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ gora 
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora ---
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ gora 
> ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ 
> gora ---
> [INFO] No site descriptor found: nothing to attach.
> [INFO]
> [INFO] --- maven-dependency-plugin:2.9:copy-dependencies (copy) @ gora ---
> [INFO]
> [INFO] --- forbiddenapis:2.0:check (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- forbiddenapis:2.0:testCheck (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ gora ---
> [INFO] Installing /home/ambari/gora/pom.xml to 
> /root/.m2/repository/org/apache/gora/gora/0.9/gora-0.9.pom
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora :: Compiler 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-compiler ---
> [INFO] Deleting /home/ambari/gora/gora-compiler/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-compiler ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-compiler ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-compiler ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> gora-compiler ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to 
> /home/ambari/gora/gora-compiler/target/classes
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the 
> environment.
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Gora  SUCCESS [ 9.093 s]
> [INFO] Apache Gora :: Compiler  FAILURE [ 2.237 s]
> [INFO] Apache Gora :: Compiler-CLI  SKIPPED
> [INFO] Apache Gora :: Core  SKIPPED
> [INFO] Apache Gora :: Pig . SKIPPED
> [INFO] Apache Gora :: Accumulo  SKIPPED
> [INFO] 

[jira] [Commented] (GORA-634) Gora - Main Build problem

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-634:


Hi, [~eurocley]. Just to check everything because sadly there is not error 
information, please show us the output of `javac -version`.
Thank you!

> Gora - Main Build problem
> -
>
> Key: GORA-634
> URL: https://issues.apache.org/jira/browse/GORA-634
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-compiler
>Affects Versions: 0.9
> Environment: Debian 9 updated to last build before version 10
> Observation, GIT, MVN and all requirements are in place.  
>Reporter: Cleyson Barros
>Priority: Blocker
>  Labels: build
>
> root@hgclusterambari00:/home/ambari/gora# mvn clean install
> Warning: JAVA_HOME environment variable is not set.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Gora
> [INFO] Apache Gora :: Compiler
> [INFO] Apache Gora :: Compiler-CLI
> [INFO] Apache Gora :: Core
> [INFO] Apache Gora :: Pig
> [INFO] Apache Gora :: Accumulo
> [INFO] Apache Gora :: HBase
> [INFO] Apache Gora :: Cassandra - CQL
> [INFO] Apache Gora :: GoraCI
> [INFO] Apache Gora :: Infinispan
> [INFO] Apache Gora :: JCache
> [INFO] Apache Gora :: OrientDB
> [INFO] Apache Gora :: Lucene
> [INFO] Apache Gora :: Dynamodb
> [INFO] Apache Gora :: CouchDB
> [INFO] Apache Gora :: Maven Plugin
> [INFO] Apache Gora :: MongoDB
> [INFO] Apache Gora :: Solr
> [INFO] Apache Gora :: Aerospike
> [INFO] Apache Gora :: Ignite
> [INFO] Apache Gora :: Tutorial
> [INFO] Apache Gora :: Sources-Dist
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora ---
> [INFO] Deleting /home/ambari/gora/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ gora 
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora ---
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ gora 
> ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ 
> gora ---
> [INFO] No site descriptor found: nothing to attach.
> [INFO]
> [INFO] --- maven-dependency-plugin:2.9:copy-dependencies (copy) @ gora ---
> [INFO]
> [INFO] --- forbiddenapis:2.0:check (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- forbiddenapis:2.0:testCheck (default) @ gora ---
> [INFO] Skipping execution for packaging "pom"
> [INFO]
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ gora ---
> [INFO] Installing /home/ambari/gora/pom.xml to 
> /root/.m2/repository/org/apache/gora/gora/0.9/gora-0.9.pom
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Gora :: Compiler 0.9
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gora-compiler ---
> [INFO] Deleting /home/ambari/gora/gora-compiler/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
> gora-compiler ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process 
> (process-resource-bundles) @ gora-compiler ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> gora-compiler ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> gora-compiler ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to 
> /home/ambari/gora/gora-compiler/target/classes
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the 
> environment.
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Gora  SUCCESS [ 9.093 s]
> [INFO] Apache Gora :: Compiler  FAILURE [ 2.237 s]
> [INFO] Apache Gora :: Compiler-CLI  SKIPPED
> [INFO] Apache Gora :: Core  SKIPPED
> [INFO] Apache Gora :: Pig . SKIPPED
> [INFO] Apache Gora :: Accumulo  SKIPPED
> [INFO] Apache Gora :: HBase ... SKIPPED
> [INFO] 

[jira] [Updated] (GORA-633) Make KuduSession thread safe for KuduStore

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-633:
---
Description: 
As per the docs KuduSession is not thread safe - 
https://kudu.apache.org/apidocs/org/apache/kudu/client/KuduSession.html
This variable is a shared variable and instantiated at class level. I noticed 
there are multiple operations you do on top of KuduSession instance. These can 
possibly fail at concurrency. You may need to create new session per each these 
operations you do on top it in datastore methods or add some pooling mechanism 
from your code. Please check on this whether we have complication at 
concurrency.

https://github.com/apache/gora/blob/master/gora-kudu/src/main/java/org/apache/gora/kudu/store/KuduStore.java#L85

See complete thread at: 
https://github.com/apache/gora/pull/178#discussion_r316540236

Kudu list messages: 
https://lists.apache.org/thread.html/6d3d62ebc7ee2d76cc63e6f3c0d58fcd4addfedc7435e69519b5c447@%3Cuser.kudu.apache.org%3E

  was:
As per the docs KuduSession is not thread safe - 
https://kudu.apache.org/apidocs/org/apache/kudu/client/KuduSession.html
This variable is a shared variable and instantiated at class level. I noticed 
there are multiple operations you do on top of KuduSession instance. These can 
possibly fail at concurrency. You may need to create new session per each these 
operations you do on top it in datastore methods or add some pooling mechanism 
from your code. Please check on this whether we have complication at 
concurrency.

https://github.com/apache/gora/blob/master/gora-kudu/src/main/java/org/apache/gora/kudu/store/KuduStore.java#L85

See complete thread at: 
https://github.com/apache/gora/pull/178#discussion_r316540236


> Make KuduSession thread safe for KuduStore
> --
>
> Key: GORA-633
> URL: https://issues.apache.org/jira/browse/GORA-633
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-kudu
>Affects Versions: 1.0
>Reporter: Alfonso Nishikawa
>Priority: Minor
>  Labels: gora-kudu
>
> As per the docs KuduSession is not thread safe - 
> https://kudu.apache.org/apidocs/org/apache/kudu/client/KuduSession.html
> This variable is a shared variable and instantiated at class level. I noticed 
> there are multiple operations you do on top of KuduSession instance. These 
> can possibly fail at concurrency. You may need to create new session per each 
> these operations you do on top it in datastore methods or add some pooling 
> mechanism from your code. Please check on this whether we have complication 
> at concurrency.
> https://github.com/apache/gora/blob/master/gora-kudu/src/main/java/org/apache/gora/kudu/store/KuduStore.java#L85
> See complete thread at: 
> https://github.com/apache/gora/pull/178#discussion_r316540236
> Kudu list messages: 
> https://lists.apache.org/thread.html/6d3d62ebc7ee2d76cc63e6f3c0d58fcd4addfedc7435e69519b5c447@%3Cuser.kudu.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (GORA-633) Make KuduSession thread safe for KuduStore

[Alfonso Nishikawa (Jira)]

Alfonso Nishikawa created GORA-633:
--

 Summary: Make KuduSession thread safe for KuduStore
 Key: GORA-633
 URL: https://issues.apache.org/jira/browse/GORA-633
 Project: Apache Gora
  Issue Type: Improvement
Affects Versions: 1.0
Reporter: Alfonso Nishikawa


As per the docs KuduSession is not thread safe - 
https://kudu.apache.org/apidocs/org/apache/kudu/client/KuduSession.html
This variable is a shared variable and instantiated at class level. I noticed 
there are multiple operations you do on top of KuduSession instance. These can 
possibly fail at concurrency. You may need to create new session per each these 
operations you do on top it in datastore methods or add some pooling mechanism 
from your code. Please check on this whether we have complication at 
concurrency.

https://github.com/apache/gora/blob/master/gora-kudu/src/main/java/org/apache/gora/kudu/store/KuduStore.java#L85

See complete thread at: 
https://github.com/apache/gora/pull/178#discussion_r316540236



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (GORA-485) Apache Kudu datastore for Gora

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-485.

  Assignee: John Mora  (was: Cihad Guzel)
Resolution: Fixed

> Apache Kudu datastore for Gora
> --
>
> Key: GORA-485
> URL: https://issues.apache.org/jira/browse/GORA-485
> Project: Apache Gora
>  Issue Type: New Feature
>Affects Versions: 0.8
>Reporter: Kevin Ratnasekera
>Assignee: John Mora
>Priority: Major
>  Labels: gora-kudu, gsoc2017, gsoc2019
> Fix For: 1.0
>
>  Time Spent: 13h 50m
>  Remaining Estimate: 0h
>
> Apache Kudu is getting lot of attention. Kudu is a key/value store optimized 
> for analytic workloads. [1] 
> [1] 
> https://blog.cloudera.com/blog/2015/09/kudu-new-apache-hadoop-storage-for-fast-analytics-on-fast-data/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (GORA-485) Apache Kudu datastore for Gora

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-485:


Merged. Thank you, [~jhnmora000]!

> Apache Kudu datastore for Gora
> --
>
> Key: GORA-485
> URL: https://issues.apache.org/jira/browse/GORA-485
> Project: Apache Gora
>  Issue Type: New Feature
>Affects Versions: 0.8
>Reporter: Kevin Ratnasekera
>Assignee: Cihad Guzel
>Priority: Major
>  Labels: gora-kudu, gsoc2017, gsoc2019
> Fix For: 1.0
>
>  Time Spent: 13h 50m
>  Remaining Estimate: 0h
>
> Apache Kudu is getting lot of attention. Kudu is a key/value store optimized 
> for analytic workloads. [1] 
> [1] 
> https://blog.cloudera.com/blog/2015/09/kudu-new-apache-hadoop-storage-for-fast-analytics-on-fast-data/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (GORA-625) Add documentation for the Kudu DataStore

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa updated GORA-625:
---
Fix Version/s: 1.0

> Add documentation for the Kudu DataStore
> 
>
> Key: GORA-625
> URL: https://issues.apache.org/jira/browse/GORA-625
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: documentation
>Affects Versions: 1.0
>Reporter: John Mora
>Assignee: John Mora
>Priority: Minor
>  Labels: patch
> Fix For: 1.0
>
> Attachments: kudu-backend.patch
>
>
> Documentation for the Kudu backend, as a patch for the gora website.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (GORA-625) Add documentation for the Kudu DataStore

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa resolved GORA-625.

Resolution: Fixed

> Add documentation for the Kudu DataStore
> 
>
> Key: GORA-625
> URL: https://issues.apache.org/jira/browse/GORA-625
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: documentation
>Affects Versions: 1.0
>Reporter: John Mora
>Assignee: John Mora
>Priority: Minor
>  Labels: patch
> Fix For: 1.0
>
> Attachments: kudu-backend.patch
>
>
> Documentation for the Kudu backend, as a patch for the gora website.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (GORA-625) Add documentation for the Kudu DataStore

[Alfonso Nishikawa (Jira)]

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

Alfonso Nishikawa commented on GORA-625:


Updated the documentation. Thank you,  [~jhnmora000]!

> Add documentation for the Kudu DataStore
> 
>
> Key: GORA-625
> URL: https://issues.apache.org/jira/browse/GORA-625
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: documentation
>Affects Versions: 1.0
>Reporter: John Mora
>Assignee: John Mora
>Priority: Minor
>  Labels: patch
> Attachments: kudu-backend.patch
>
>
> Documentation for the Kudu backend, as a patch for the gora website.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Closed] (GORA-393) bin/compile-examples.sh should do a touch on source files before compiling

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa closed GORA-393.
--

> bin/compile-examples.sh should do a touch on source files before compiling
> --
>
> Key: GORA-393
> URL: https://issues.apache.org/jira/browse/GORA-393
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.3, 0.4, 0.5
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
>Priority: Trivial
>  Labels: compiler
> Fix For: 0.9
>
>
> {{bin/compile-examples.sh}} is used to regenerate the examples entities after 
> modifying the compiler.
> When the schemas are not modified, avro compiler don't overwrite the 
> destination .java classes.
> If we 'touch' the source files we will force the regeneration of the entities 
> always. Just a convenience modification.
> (I noticed now a typo in that script. In [line 
> 41|https://github.com/apache/gora/blob/master/bin/compile-examples.sh#L41] 
> must be used the command {{goracompiler}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GORA-393) bin/compile-examples.sh should do a touch on source files before compiling

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-393.

   Resolution: Fixed
 Assignee: Alfonso Nishikawa
Fix Version/s: (was: 1.0)
   0.9

> bin/compile-examples.sh should do a touch on source files before compiling
> --
>
> Key: GORA-393
> URL: https://issues.apache.org/jira/browse/GORA-393
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.3, 0.4, 0.5
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
>Priority: Trivial
>  Labels: compiler
> Fix For: 0.9
>
>
> {{bin/compile-examples.sh}} is used to regenerate the examples entities after 
> modifying the compiler.
> When the schemas are not modified, avro compiler don't overwrite the 
> destination .java classes.
> If we 'touch' the source files we will force the regeneration of the entities 
> always. Just a convenience modification.
> (I noticed now a typo in that script. In [line 
> 41|https://github.com/apache/gora/blob/master/bin/compile-examples.sh#L41] 
> must be used the command {{goracompiler}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-393) bin/compile-examples.sh should do a touch on source files before compiling

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-393:


Hi, [~jhnmora000].
I completely forgot about this issue. Is was fixed inside [Pull request 
135|https://github.com/alfonsonishikawa/gora/commit/09981b81a46ad43379b7f9fc9d8463c8954094ff].
I will close it :)
Thank you!!

> bin/compile-examples.sh should do a touch on source files before compiling
> --
>
> Key: GORA-393
> URL: https://issues.apache.org/jira/browse/GORA-393
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.3, 0.4, 0.5
>Reporter: Alfonso Nishikawa
>Priority: Trivial
>  Labels: compiler
> Fix For: 1.0
>
>
> {{bin/compile-examples.sh}} is used to regenerate the examples entities after 
> modifying the compiler.
> When the schemas are not modified, avro compiler don't overwrite the 
> destination .java classes.
> If we 'touch' the source files we will force the regeneration of the entities 
> always. Just a convenience modification.
> (I noticed now a typo in that script. In [line 
> 41|https://github.com/apache/gora/blob/master/bin/compile-examples.sh#L41] 
> must be used the command {{goracompiler}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-411) Add exists(key) to DataStore interface

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-411:


[~jhnmora000], Hi!

Looks good to me too. Just remember to add the test to 
`org.apache.gora.store.DataStoreTestBase` and the code you wrote to 
`org.apache.gora.store.DataStoreTestUtil` (maybe this is what you did). I can't 
think about any other test.

My +1. Create a pull request with this in github and we will review it :)

> Add exists(key) to DataStore interface
> --
>
> Key: GORA-411
> URL: https://issues.apache.org/jira/browse/GORA-411
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-core, storage
>Reporter: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> NUTCH-1679 need to check if there exists some rows and they are proposing to 
> use {{store.get(TableUtil.reverseUrl(url)))}}.
> This will have a considerably impact on performance since every column will 
> be fetched.
> Some datastores implements a call to just check if a row exists (like HBase) 
> so no data is transfered by network.
> If a datastore can't handle an "exists" call, can default to a get.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-563) Support Hadoop Combiner

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-563:
--

 Summary: Support Hadoop Combiner
 Key: GORA-563
 URL: https://issues.apache.org/jira/browse/GORA-563
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-core
Affects Versions: 0.9
Reporter: Alfonso Nishikawa


It seems the reducer class is not being used as a Combiner. It would be good to 
have that feature.

[From this StackOverflow 
question|https://stackoverflow.com/questions/54003803/combiner-function-in-apache-hadoop-with-gora].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-562:
--

 Summary: Add a bin/gora command script for Windows
 Key: GORA-562
 URL: https://issues.apache.org/jira/browse/GORA-562
 Project: Apache Gora
  Issue Type: Improvement
Affects Versions: 0.9
Reporter: Alfonso Nishikawa


We would need a bin/gora.bat executable (or gora.cmd or alike) to compile 
schemas under Windows.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-559) Improve gora-pig's GoraStorage with pushdown filters

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-559:
--

 Summary: Improve gora-pig's GoraStorage with pushdown filters
 Key: GORA-559
 URL: https://issues.apache.org/jira/browse/GORA-559
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-pig
Reporter: Alfonso Nishikawa


The aim is analyze and implement (if the conclusion is that it is possible) the 
pushdown filter functionality for the Pig connector. When in a script there is 
a "FILTER" command, the condition has to be passed to the datastore so the LOAD 
instruction does not load all the data. For example, HBase would only accept 
key range filters at this moment, but this will be a great improvement in 
performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GORA-530) Reinstate exception throwing at Query#execute()

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-530.

Resolution: Fixed

> Reinstate exception throwing at Query#execute()
> ---
>
> Key: GORA-530
> URL: https://issues.apache.org/jira/browse/GORA-530
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-core
>Affects Versions: 0.8
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
>Priority: Minor
>  Labels: query
> Fix For: 0.9
>
>
> When executing a query, the exceptions are being shadowed and the execution 
> returns {{null}}.
> This makes any client to be ignorant of the cause, because it is only logged 
> into the server.
> The objective is to reinstate the exception throwing, where the interface 
> throws GoraException to make any client aware of the underlying problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa updated GORA-557:
---
Issue Type: Improvement  (was: New Feature)

> Add support for MongoDB to GoraExplorer
> ---
>
> Key: GORA-557
> URL: https://issues.apache.org/jira/browse/GORA-557
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Alfonso Nishikawa
>Priority: Minor
>  Labels: gsoc2019
>
> After merging GoraExplorer interfaces and methods for the core, MongoDB 
> module has to be updated with the following:
> - Allow to load mappings from properties instead only from files. [Example at 
> HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
>  (where the static final constant much probably will have to be refactorized).
> - Implement the retrieval of native information from MongoDB. ([Technical 
> details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])
> A plus would be implement the support in 
> [GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
> MongoDB data visually.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-558) Add support for Cassandra to GoraExplorer

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-558:
--

 Summary: Add support for Cassandra to GoraExplorer
 Key: GORA-558
 URL: https://issues.apache.org/jira/browse/GORA-558
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-cassandra
Reporter: Alfonso Nishikawa


After merging GoraExplorer interfaces and methods for the core, Cassandra 
module has to be updated with the following:

- Allow to load mappings from properties instead only from files. [Example at 
HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
 (where the static final constant much probably will have to be refactorized).
- Implement the retrieval of native information from Cassandra. ([Technical 
details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])

A plus would be implement the support in 
[GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
Cassandra's data visually.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-557) Add support for MongoDB to GoraExplorer

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-557:
--

 Summary: Add support for MongoDB to GoraExplorer
 Key: GORA-557
 URL: https://issues.apache.org/jira/browse/GORA-557
 Project: Apache Gora
  Issue Type: New Feature
  Components: gora-mongodb
Reporter: Alfonso Nishikawa


After merging GoraExplorer interfaces and methods for the core, MongoDB module 
has to be updated with the following:

- Allow to load mappings from properties instead only from files. [Example at 
HBaseStore|https://github.com/apache/gora/blob/6ce47dcdea60e4b0d3abe03ddac01a65716cc173/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L145]
 (where the static final constant much probably will have to be refactorized).
- Implement the retrieval of native information from MongoDB. ([Technical 
details|https://translate.google.es/translate?sl=es=en=y=_t=es=UTF-8=http%3A%2F%2Fredmine.nishilua.com%2Fprojects%2Fgoraexplorer%2Fwiki%2FObtenci%25C3%25B3n_de_metadatos_de_las_BBDD_nativas=])

A plus would be implement the support in 
[GoraExplorer|https://www.goraexplorer.com] so it will be possible to manage 
MongoDB data visually.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-556) Implement tests for gora-pig under HBase 2.x

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-556:
--

 Summary: Implement tests for gora-pig under HBase 2.x
 Key: GORA-556
 URL: https://issues.apache.org/jira/browse/GORA-556
 Project: Apache Gora
  Issue Type: Task
  Components: gora-pig
Affects Versions: 0.9
Reporter: Alfonso Nishikawa


Under HBase 1.x it was not possible to implement gora-pig tests because 
HBaseTestingUtility spawned a Hadoop 1.x cluster. Now, after upgrading to HBase 
2.2.1, maybe it will be possible to implement JUnit tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-109.

Resolution: Fixed

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-109:


I close this issue because the pig adapter has been merged with the [pull 
#135|https://github.com/apache/gora/pull/135].
The problem with the tests under HBase 2.2.1 will be faced in another issue.

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GORA-550) Update POM for the move to gitbox.

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-550.

   Resolution: Fixed
Fix Version/s: 0.9

> Update POM for the move to gitbox.
> --
>
> Key: GORA-550
> URL: https://issues.apache.org/jira/browse/GORA-550
> Project: Apache Gora
>  Issue Type: Task
>  Components: build process
>Affects Versions: 0.8
>Reporter: Kevin Ratnasekera
>Assignee: Kevin Ratnasekera
>Priority: Critical
> Fix For: 0.9
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The  section, and the project reports  need updating for the move 
> to gitbox.apache.org.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-109:


Hi, I updated some documentation at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html]

Source code at this branch: 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

Since that branch has more changes related to GoraExplorer needs, I am thinking 
about creating a new issue that covers this one and more.

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa edited comment on GORA-109 at 5/3/18 6:43 PM:


Hi, Pals.

It has been a lot of time since this issue. I finally got a _quite_-successful 
implementation of a GoraStorage for Apache Pig. At this moment it is in my own 
branch since I impemented it for my degree project. 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

It allows to load data from -any- HBase (I can only claim this) through Gora in 
Pig scripts like:
{code:java}
set job.name 'GoraPig LOAD test';
register gora/*.jar;
webpage = LOAD '.' USING org.apache.gora.pig.GoraStorage('{
    "persistentClass": "admin.WebPage",
    "fields": "baseUrl,contentType"
}') ;
DUMP webpage;
{code}
I will update my page at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html] with details in the 
incoming days (the speed depends on my spare time), but please, ask me in 
advance the first questions you have so I can write a FAQ too. If I have to 
write by my own ideas, I tend to write EVERYTHING and I end NEVER :)

If anyone is a Pig user and wants to test it ask too. Questions priotize what I 
explain :)

I am thinking about some Nutch jobs in Pig :P

 

Sorry for the inmense delay :(. Just know that this _"complete"_ implementation 
(actually nothing ever is complete) took me more than 300 hours :(. It has much 
details everywhere.


was (Author: alfonso.nishikawa):
Hi, Pals.

It has been a lot of time since this issue. I finally got a _quite_-successful 
implementation of a GoraStorage for Apache Pig. At this moment it is in my own 
branch since I impemented it for my degree proyect. 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

It allows to load data from -any- HBase (I can only claim this) through Gora in 
Pig scripts like:
{code:java}
set job.name 'GoraPig LOAD test';
register gora/*.jar;
webpage = LOAD '.' USING org.apache.gora.pig.GoraStorage('{
    "persistentClass": "admin.WebPage",
    "fields": "baseUrl,contentType"
}') ;
DUMP webpage;
{code}
I will update my page at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html] with details in the 
incoming days (the speed depends on my spare time), but please, ask me in 
advance the first questions you have so I can write a FAQ too. If I have to 
write by my own ideas, I tend to write EVERYTHING and I end NEVER :)

If anyone is a Pig user and wants to test it ask too. Questions priotize what I 
explain :)

I am thinking about some Nutch jobs in Pig :P

 

Sorry for the inmense delay :(. Just know that this _"complete"_ implementation 
(actually nothing ever is complete) took me more than 300 hours :(. It has much 
details everywhere.

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa edited comment on GORA-109 at 5/3/18 6:40 PM:


Hi, Pals.

It has been a lot of time since this issue. I finally got a _quite_-successful 
implementation of a GoraStorage for Apache Pig. At this moment it is in my own 
branch since I impemented it for my degree proyect. 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

It allows to load data from -any- HBase (I can only claim this) through Gora in 
Pig scripts like:
{code:java}
set job.name 'GoraPig LOAD test';
register gora/*.jar;
webpage = LOAD '.' USING org.apache.gora.pig.GoraStorage('{
    "persistentClass": "admin.WebPage",
    "fields": "baseUrl,contentType"
}') ;
DUMP webpage;
{code}
I will update my page at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html] with details in the 
incoming days (the speed depends on my spare time), but please, ask me in 
advance the first questions you have so I can write a FAQ too. If I have to 
write by my own ideas, I tend to write EVERYTHING and I end NEVER :)

If anyone is a Pig user and wants to test it ask too. Questions priotize what I 
explain :)

I am thinking about some Nutch jobs in Pig :P

 

Sorry for the inmense delay :(. Just know that this _"complete"_ implementation 
(actually nothing ever is complete) took me more than 300 hours :(. It has much 
details everywhere.


was (Author: alfonso.nishikawa):
Hi, Pals.

It has been a lot of time since this issue. I finally got a _quite_-successful 
implementation of a GoraStorage for Apache Pig. At this moment it is in my own 
branch since I impemented it for my degree proyect. 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

It allows to load data from -any- HBase (I can only claim this) through Gora in 
Pig scripts like:
{code:java}
set job.name 'GoraPig LOAD test';
register gora/*.jar;
webpage = LOAD '.' USING org.apache.gora.pig.GoraStorage('{
    "persistentClass": "admin.WebPage",
    "fields": "baseUrl,contentType"
}') ;
DUMP webpage;
{code}
I will update my page at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html] with details in the 
incoming days (the speed depends on my spare time), but please, ask me in 
advance the first questions you have so I can write a FAQ too. If I have to 
write by my own ideas, I tend to write EVERYTHING and I end NEVER :)

I anyone is a Pig user and wants to test it ask too. Questions priotize what I 
explain :)

I am thinking about some Nutch jobs in Pig :P

 

Sorry for the inmense delay :(. Just know that this _"complete"_ implementation 
(actually nothing ever is complete) took me more than 300 hours :(. It has much 
details everywhere.

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GORA-109) Pig Adapter for Gora

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-109:


Hi, Pals.

It has been a lot of time since this issue. I finally got a _quite_-successful 
implementation of a GoraStorage for Apache Pig. At this moment it is in my own 
branch since I impemented it for my degree proyect. 
[https://github.com/alfonsonishikawa/gora/tree/goraexplorer/gora-pig]

It allows to load data from -any- HBase (I can only claim this) through Gora in 
Pig scripts like:
{code:java}
set job.name 'GoraPig LOAD test';
register gora/*.jar;
webpage = LOAD '.' USING org.apache.gora.pig.GoraStorage('{
    "persistentClass": "admin.WebPage",
    "fields": "baseUrl,contentType"
}') ;
DUMP webpage;
{code}
I will update my page at 
[http://people.apache.org/~alfonsonishikawa/gora-109.html] with details in the 
incoming days (the speed depends on my spare time), but please, ask me in 
advance the first questions you have so I can write a FAQ too. If I have to 
write by my own ideas, I tend to write EVERYTHING and I end NEVER :)

I anyone is a Pig user and wants to test it ask too. Questions priotize what I 
explain :)

I am thinking about some Nutch jobs in Pig :P

 

Sorry for the inmense delay :(. Just know that this _"complete"_ implementation 
(actually nothing ever is complete) took me more than 300 hours :(. It has much 
details everywhere.

> Pig Adapter for Gora
> 
>
> Key: GORA-109
> URL: https://issues.apache.org/jira/browse/GORA-109
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-pig
>Affects Versions: 0.2
>Reporter: Lewis John McGibbney
>Assignee: Alfonso Nishikawa
>Priority: Minor
> Fix For: 0.9
>
>
> This has been on the agenda from the start and I suppose will be purely use 
> case driven. Persoanlly I haven't touched Pig as I don't have a use-case 
> driven requirement to do so, however there is no harm in this being logged if 
> in the future it attracts interest.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GORA-421) PersistentBase#setDirty() does not set dirty

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-421.

Resolution: Fixed

> PersistentBase#setDirty() does not set dirty
> 
>
> Key: GORA-421
> URL: https://issues.apache.org/jira/browse/GORA-421
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-core
>Affects Versions: 0.4, 0.5, 0.6
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
>Priority: Major
> Fix For: 0.9
>
>
> {{PersistentBase#setDirty()}} sets [dirty with value -128 = 
> 1000|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/persistency/impl/PersistentBase.java#L164],
>  when should be -1=
> Will be desirable some tests too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GORA-530) Reinstate exception throwing at Query#execute()

[Alfonso Nishikawa (JIRA)]

Alfonso Nishikawa created GORA-530:
--

 Summary: Reinstate exception throwing at Query#execute()
 Key: GORA-530
 URL: https://issues.apache.org/jira/browse/GORA-530
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-core
Affects Versions: 0.8
Reporter: Alfonso Nishikawa
Assignee: Alfonso Nishikawa
Priority: Minor
 Fix For: 0.9


When executing a query, the exceptions are being shadowed and the execution 
returns {{null}}.
This makes any client to be ignorant of the cause, because it is only logged 
into the server.

The objective is to reinstate the exception throwing, where the interface 
throws GoraException to make any client aware of the underlying problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GORA-421) PersistentBase#setDirty() does not set dirty

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa reassigned GORA-421:
--

Assignee: Alfonso Nishikawa

> PersistentBase#setDirty() does not set dirty
> 
>
> Key: GORA-421
> URL: https://issues.apache.org/jira/browse/GORA-421
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-core
>Affects Versions: 0.4, 0.5, 0.6
>Reporter: Alfonso Nishikawa
>Assignee: Alfonso Nishikawa
> Fix For: 0.9
>
>
> {{PersistentBase#setDirty()}} sets [dirty with value -128 = 
> 1000|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/persistency/impl/PersistentBase.java#L164],
>  when should be -1=
> Will be desirable some tests too.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GORA-476) Nutch 2.X GeneratorJob creates NullPointerException when using DataFileAvroStore

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-476:


Am I wrong or DataFileAvroStore is not suitable to be used with Nutch?

[DataFileAvroStore|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/store/DataFileAvroStore.java#L58]
 does not write the keys when saving, and thus, retrieves them as 'null' and 
{{#unreverseUrl(key)}} fails with NullPointerException)
[Here|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/query/AvroResult.java#L56]
 it can be seen that when retrieven the next record at a scan, it only fills 
the "persistent" information (not the key).

DataFileAvroStore does not support indexed (by key) access because there are no 
keys.

I don't know if Avro supports any type of indexed writes when writing, nor how 
to add gracefully the keys to the written information.



> Nutch 2.X GeneratorJob creates NullPointerException when using 
> DataFileAvroStore
> 
>
> Key: GORA-476
> URL: https://issues.apache.org/jira/browse/GORA-476
> Project: Apache Gora
>  Issue Type: Bug
>  Components: avro, gora-core
>Affects Versions: 0.6.1
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.9
>
>
> When running the Nuth 2.X GeneratorJob I get the following
> {code}
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: starting
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: filtering: 
> false
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: normalizing: 
> false
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: topN: 5
> 2016-05-12 17:27:30,319 WARN  util.NativeCodeLoader - Unable to load 
> native-hadoop library for your platform... using builtin-java classes where 
> applicable
> 2016-05-12 17:27:30,333 INFO  crawl.FetchScheduleFactory - Using 
> FetchSchedule impl: org.apache.nutch.crawl.DefaultFetchSchedule
> 2016-05-12 17:27:30,334 INFO  crawl.AbstractFetchSchedule - 
> defaultInterval=2592000
> 2016-05-12 17:27:30,334 INFO  crawl.AbstractFetchSchedule - 
> maxInterval=7776000
> 2016-05-12 17:27:31,012 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/staging/lmcgibbn997854508/.staging/job_local997854508_0001/job.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.retry.interval;  Ignoring.
> 2016-05-12 17:27:31,014 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/staging/lmcgibbn997854508/.staging/job_local997854508_0001/job.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.attempts;  Ignoring.
> 2016-05-12 17:27:31,091 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/local/localRunner/lmcgibbn/job_local997854508_0001/job_local997854508_0001.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.retry.interval;  Ignoring.
> 2016-05-12 17:27:31,094 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/local/localRunner/lmcgibbn/job_local997854508_0001/job_local997854508_0001.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.attempts;  Ignoring.
> 2016-05-12 17:27:31,309 INFO  crawl.FetchScheduleFactory - Using 
> FetchSchedule impl: org.apache.nutch.crawl.DefaultFetchSchedule
> 2016-05-12 17:27:31,309 INFO  crawl.AbstractFetchSchedule - 
> defaultInterval=2592000
> 2016-05-12 17:27:31,309 INFO  crawl.AbstractFetchSchedule - 
> maxInterval=7776000
> 2016-05-12 17:27:31,381 WARN  mapred.LocalJobRunner - job_local997854508_0001
> java.lang.Exception: java.lang.NullPointerException
>   at 
> org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:462)
>   at 
> org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:522)
> Caused by: java.lang.NullPointerException
>   at org.apache.nutch.util.TableUtil.unreverseUrl(TableUtil.java:88)
>   at org.apache.nutch.crawl.GeneratorMapper.map(GeneratorMapper.java:51)
>   at org.apache.nutch.crawl.GeneratorMapper.map(GeneratorMapper.java:1)
>   at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:145)
>   at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:340)
>   at 
> org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:243)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> 

[jira] [Comment Edited] (GORA-476) Nutch 2.X GeneratorJob creates NullPointerException when using DataFileAvroStore

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa edited comment on GORA-476 at 12/21/17 9:22 AM:
--

Am I wrong or DataFileAvroStore is not suitable to be used with Nutch?

[DataFileAvroStore|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/store/DataFileAvroStore.java#L58]
 does not write the keys when saving, and thus, retrieves them as 'null' and 
{{#unreverseUrl(key)}} fails with NullPointerException.
[Here|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/query/AvroResult.java#L56]
 it can be seen that when retrieven the next record at a scan, it only fills 
the "persistent" information (not the key).

DataFileAvroStore does not support indexed (by key) access because there are no 
keys.

I don't know if Avro supports any type of indexed writes when writing, nor how 
to add gracefully the keys to the written information.




was (Author: alfonso.nishikawa):
Am I wrong or DataFileAvroStore is not suitable to be used with Nutch?

[DataFileAvroStore|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/store/DataFileAvroStore.java#L58]
 does not write the keys when saving, and thus, retrieves them as 'null' and 
{{#unreverseUrl(key)}} fails with NullPointerException)
[Here|https://github.com/apache/gora/blob/master/gora-core/src/main/java/org/apache/gora/avro/query/AvroResult.java#L56]
 it can be seen that when retrieven the next record at a scan, it only fills 
the "persistent" information (not the key).

DataFileAvroStore does not support indexed (by key) access because there are no 
keys.

I don't know if Avro supports any type of indexed writes when writing, nor how 
to add gracefully the keys to the written information.



> Nutch 2.X GeneratorJob creates NullPointerException when using 
> DataFileAvroStore
> 
>
> Key: GORA-476
> URL: https://issues.apache.org/jira/browse/GORA-476
> Project: Apache Gora
>  Issue Type: Bug
>  Components: avro, gora-core
>Affects Versions: 0.6.1
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.9
>
>
> When running the Nuth 2.X GeneratorJob I get the following
> {code}
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: starting
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: filtering: 
> false
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: normalizing: 
> false
> 2016-05-12 17:27:30,191 INFO  crawl.GeneratorJob - GeneratorJob: topN: 5
> 2016-05-12 17:27:30,319 WARN  util.NativeCodeLoader - Unable to load 
> native-hadoop library for your platform... using builtin-java classes where 
> applicable
> 2016-05-12 17:27:30,333 INFO  crawl.FetchScheduleFactory - Using 
> FetchSchedule impl: org.apache.nutch.crawl.DefaultFetchSchedule
> 2016-05-12 17:27:30,334 INFO  crawl.AbstractFetchSchedule - 
> defaultInterval=2592000
> 2016-05-12 17:27:30,334 INFO  crawl.AbstractFetchSchedule - 
> maxInterval=7776000
> 2016-05-12 17:27:31,012 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/staging/lmcgibbn997854508/.staging/job_local997854508_0001/job.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.retry.interval;  Ignoring.
> 2016-05-12 17:27:31,014 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/staging/lmcgibbn997854508/.staging/job_local997854508_0001/job.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.attempts;  Ignoring.
> 2016-05-12 17:27:31,091 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/local/localRunner/lmcgibbn/job_local997854508_0001/job_local997854508_0001.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.retry.interval;  Ignoring.
> 2016-05-12 17:27:31,094 WARN  conf.Configuration - 
> file:/tmp/hadoop-lmcgibbn/mapred/local/localRunner/lmcgibbn/job_local997854508_0001/job_local997854508_0001.xml:an
>  attempt to override final parameter: 
> mapreduce.job.end-notification.max.attempts;  Ignoring.
> 2016-05-12 17:27:31,309 INFO  crawl.FetchScheduleFactory - Using 
> FetchSchedule impl: org.apache.nutch.crawl.DefaultFetchSchedule
> 2016-05-12 17:27:31,309 INFO  crawl.AbstractFetchSchedule - 
> defaultInterval=2592000
> 2016-05-12 17:27:31,309 INFO  crawl.AbstractFetchSchedule - 
> maxInterval=7776000
> 2016-05-12 17:27:31,381 WARN  mapred.LocalJobRunner - job_local997854508_0001
> java.lang.Exception: java.lang.NullPointerException
>   at 
> org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:462)
>   at 
> 

[jira] [Commented] (GORA-514) Scan of a single key with a limit clears the persistent instance when iterating results

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa commented on GORA-514:


I have been digging, and maybe I am wrong.

I was thinking that result#get() should return a not-reused instance as happens 
in HBase, but maybe it is HBase which is wrong? result#get() reuses the 
instance?
The sourcecode in some way suggest that [1], but I did not find any 
documentation where it is specified. Anyone knows?

If this is the case, then it is HBaseStore which is returning new instances and 
the only thing to do in this issue is to write somewhere in the javadoc that 
the instance returned by #get() _could be_ one being reused and should be 
cloned if necessary.

What do you think? I now feel quite confident about that the only need is the 
explanation somewhere :)

[1] 
https://github.com/apache/gora/blob/apache-gora-0.7/gora-core/src/main/java/org/apache/gora/query/impl/ResultBase.java#L103

> Scan of a single key with a limit clears the persistent instance when 
> iterating results
> ---
>
> Key: GORA-514
> URL: https://issues.apache.org/jira/browse/GORA-514
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-accumulo, gora-cassandra, gora-core, gora-hbase, 
> gora-jcache, gora-mongodb, gora-solr
>Affects Versions: 0.7, 0.8
>Reporter: Alfonso Nishikawa
>Priority: Minor
> Attachments: GORA-514-Example-Test.diff
>
>
> To put in context, I am just doing a scan where the start key, end key and 
> limit are configurable:
> {code:java}
> Query dataQuery = dataStore.newQuery() ;
> if (startKey != null && !startKey.equals("")) {
> dataQuery.setStartKey(startKey);
> }
> if (endKey != null && !endKey.equals("")) {
> dataQuery.setEndKey(endKey);
> }
> dataQuery.setLimit(limit);
> Result result = dataQuery.execute();
> while (result.next()) {
> results.put(result.getKey(), result.get()) ;
> }
> {code}
> When the start key is equal to end key, and the limit is configured to a 
> value >= 2 (the default value is -1), the second call to result.next() in the 
> while bucle clears the instance previously returned by result.get().
> We could think that this would be an expected behaviour since result.get() 
> -especifically for HBase- is a reusable instance when performing a Get 
> operation, but this clashes with the actual expected general behaviour in the 
> usual Scan operation shown in the former code example.
> This is: next() and get() when performing a scan should behave the same no 
> matter what initial/end keys you configure, and what maximum number of 
> results you want.
> I implemented a test than shows the issue affecting Accumulo, Cassandra, 
> HBase, JCache, MongoDB and Solr, probably because it is some issue in the 
> core.
> To see the error, you can apply the attached patch with the tests example and 
> execute:
> {code}
> mvn -Dtest=#testScanSingleResultWithLimit -fn -DfailIfNoTests=false test
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GORA-514) Scan of a single key with a limit clears the persistent instance when iterating results

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa updated GORA-514:
---
Description: 
To put in context, I am just doing a scan where the start key, end key and 
limit are configurable:


{code:java}
Query dataQuery = dataStore.newQuery() ;
if (startKey != null && !startKey.equals("")) {
dataQuery.setStartKey(startKey);
}
if (endKey != null && !endKey.equals("")) {
dataQuery.setEndKey(endKey);
}
dataQuery.setLimit(limit);
Result result = dataQuery.execute();

while (result.next()) {
results.put(result.getKey(), result.get()) ;
}
{code}

When the start key is equal to end key, and the limit is configured to a value 
>= 2 (the default value is -1), the second call to result.next() in the while 
bucle clears the instance previously returned by result.get().

We could think that this would be an expected behaviour since result.get() 
-especifically for HBase- is a reusable instance when performing a Get 
operation, but this clashes with the actual expected general behaviour in the 
usual Scan operation shown in the former code example.

This is: next() and get() when performing a scan should behave the same no 
matter what initial/end keys you configure, and what maximum number of results 
you want.

I implemented a test than shows the issue affecting Accumulo, Cassandra, HBase, 
JCache, MongoDB and Solr, probably because it is some issue in the core.
To see the error, you can apply the attached patch with the tests example and 
execute:

{code}
mvn -Dtest=#testScanSingleResultWithLimit -fn -DfailIfNoTests=false test
{code}

  was:
To put in context, I am just doing a scan where the start key, end key and 
limit are configurable:


{code:java}
Query dataQuery = dataStore.newQuery() ;
if (startKey != null && !startKey.equals("")) {
dataQuery.setStartKey(startKey);
}
if (endKey != null && !endKey.equals("")) {
dataQuery.setEndKey(endKey);
}
dataQuery.setLimit(limit);
Result result = dataQuery.execute();

while (result.next()) {
results.put(result.getKey(), result.get()) ;
}
{code}

When the start key is equal to end key, and the limit is configured to a value 
>= 2 (the default value is -1), the second call to result.next() in the while 
bucle clears the instance previously returned by result.get().

We could think that this would be an expected behaviour since result.get() 
-especifically for HBase- is a reusable instance when performing a Get 
operation, but this clashes with the actual expected general behaviour in the 
usual Scan operation shown in the former code example.

This is: next() and get() when performing a scan should behave the same no 
matter what initial/end keys you configure, and what maximum number of results 
you want.

I implemented a test than shows the issue affecting Accumulo, Cassandra, HBase, 
JCache, MongoDB and Solr, probably because it is some issue in the core.
To see the error, you can apply the attached patch with the tests example and 
execute:

{code:sh}
mvn -Dtest=#testScanSingleResultWithLimit -fn -DfailIfNoTests=false test
{code}


> Scan of a single key with a limit clears the persistent instance when 
> iterating results
> ---
>
> Key: GORA-514
> URL: https://issues.apache.org/jira/browse/GORA-514
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-accumulo, gora-cassandra, gora-core, gora-hbase, 
> gora-jcache, gora-mongodb, gora-solr
>Affects Versions: 0.7, 0.8
>Reporter: Alfonso Nishikawa
>Priority: Minor
> Attachments: GORA-514-Example-Test.diff
>
>
> To put in context, I am just doing a scan where the start key, end key and 
> limit are configurable:
> {code:java}
> Query dataQuery = dataStore.newQuery() ;
> if (startKey != null && !startKey.equals("")) {
> dataQuery.setStartKey(startKey);
> }
> if (endKey != null && !endKey.equals("")) {
> dataQuery.setEndKey(endKey);
> }
> dataQuery.setLimit(limit);
> Result result = dataQuery.execute();
> while (result.next()) {
> results.put(result.getKey(), result.get()) ;
> }
> {code}
> When the start key is equal to end key, and the limit is configured to a 
> value >= 2 (the default value is -1), the second call to result.next() in the 
> while bucle clears the instance previously returned by result.get().
> We could think that this would be an expected behaviour since result.get() 
> -especifically for HBase- is a reusable instance when performing a Get 
> operation, but this clashes with the actual expected general behaviour in the 
> usual Scan operation shown in the former code example.
> This is: next() and get() when performing a scan should behave the same no 
> matter what initial/end keys you configure, and 

[jira] [Updated] (GORA-514) Scan of a single key with a limit clears the persistent instance when iterating results

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa updated GORA-514:
---
Description: 
To put in context, I am just doing a scan where the start key, end key and 
limit are configurable:


{code:java}
Query dataQuery = dataStore.newQuery() ;
if (startKey != null && !startKey.equals("")) {
dataQuery.setStartKey(startKey);
}
if (endKey != null && !endKey.equals("")) {
dataQuery.setEndKey(endKey);
}
dataQuery.setLimit(limit);
Result result = dataQuery.execute();

while (result.next()) {
results.put(result.getKey(), result.get()) ;
}
{code}

When the start key is equal to end key, and the limit is configured to a value 
>= 2 (the default value is -1), the second call to result.next() in the while 
bucle clears the instance previously returned by result.get().

We could think that this would be an expected behaviour since result.get() 
-especifically for HBase- is a reusable instance when performing a Get 
operation, but this clashes with the actual expected general behaviour in the 
usual Scan operation shown in the former code example.

This is: next() and get() when performing a scan should behave the same no 
matter what initial/end keys you configure, and what maximum number of results 
you want.

I implemented a test than shows the issue affecting Accumulo, Cassandra, HBase, 
JCache, MongoDB and Solr, probably because it is some issue in the core.
To see the error, you can apply the attached patch with the tests example and 
execute:

{code:sh}
mvn -Dtest=#testScanSingleResultWithLimit -fn -DfailIfNoTests=false test
{code}

  was:
To put in context, I am just doing a scan where the start key, end key and 
limit are configurable:


{code:java}
Query dataQuery = dataStore.newQuery() ;
if (startKey != null && !startKey.equals("")) {
dataQuery.setStartKey(startKey);
}
if (endKey != null && !endKey.equals("")) {
dataQuery.setEndKey(endKey);
}
dataQuery.setLimit(limit);
Result result = dataQuery.execute();

while (result.next()) {
results.put(result.getKey(), result.get()) ;
}
{code}

When the start key is equal to end key, and the limit is configured to a value 
>= (the default value is -1), the second call to result.next() in the while 
bucle clears the instance previously returned by result.get().

We could think that this would be an expected behaviour since result.get() 
-especifically for HBase- is a reusable instance when performing a Get 
operation, but this clashes with the actual expected general behaviour in the 
usual Scan operation shown in the former code example.

This is: next() and get() when performing a scan should behave the same no 
matter what initial/end keys you configure, and what maximum number of results 
you want.

I implemented a test than shows the issue affecting Accumulo, Cassandra, HBase, 
JCache, MongoDB and Solr, probably because it is some issue in the core.
To see the error, you can apply the attached patch with the tests example and 
execute:

{code:sh}
mvn -Dtest=#testScanSingleResultWithLimit -fn -DfailIfNoTests=false test
{code}


> Scan of a single key with a limit clears the persistent instance when 
> iterating results
> ---
>
> Key: GORA-514
> URL: https://issues.apache.org/jira/browse/GORA-514
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-accumulo, gora-cassandra, gora-core, gora-hbase, 
> gora-jcache, gora-mongodb, gora-solr
>Affects Versions: 0.7, 0.8
>Reporter: Alfonso Nishikawa
>Priority: Minor
> Attachments: GORA-514-Example-Test.diff
>
>
> To put in context, I am just doing a scan where the start key, end key and 
> limit are configurable:
> {code:java}
> Query dataQuery = dataStore.newQuery() ;
> if (startKey != null && !startKey.equals("")) {
> dataQuery.setStartKey(startKey);
> }
> if (endKey != null && !endKey.equals("")) {
> dataQuery.setEndKey(endKey);
> }
> dataQuery.setLimit(limit);
> Result result = dataQuery.execute();
> while (result.next()) {
> results.put(result.getKey(), result.get()) ;
> }
> {code}
> When the start key is equal to end key, and the limit is configured to a 
> value >= 2 (the default value is -1), the second call to result.next() in the 
> while bucle clears the instance previously returned by result.get().
> We could think that this would be an expected behaviour since result.get() 
> -especifically for HBase- is a reusable instance when performing a Get 
> operation, but this clashes with the actual expected general behaviour in the 
> usual Scan operation shown in the former code example.
> This is: next() and 

[jira] [Resolved] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

[Alfonso Nishikawa (JIRA)]

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

Alfonso Nishikawa resolved GORA-512.

   Resolution: Fixed
Fix Version/s: 0.8

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not 
> the same as the one in the data bean
> ---
>
> Key: GORA-512
> URL: https://issues.apache.org/jira/browse/GORA-512
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Nishadi Kirielle
>Assignee: Nishadi Kirielle
>Priority: Minor
> Fix For: 0.8
>
>
> In the current implementation, when reading the HBase mapping file, if the 
> HBase mapping file does not have a matching key class and name to the data 
> bean, it only logs that information.[1] It does not fail at the time of 
> detecting it. It fails only at the time of building the mapper [2] when it 
> detects the table name is null. It will be better if it can fail at the time 
> of detecting that mapping file is missing the corresponding class. 
> [1]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. 
> https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)