Re: [DISCUSS] Interest in rolling a release

[lewis john mcgibbney]

Thanks Kevin. I have a few items in the backlog and will tackle those tests
when I come back to it.
lewismc

On Tue, Apr 9, 2024 at 05:43 Kevin Ratnasekera 
wrote:

> Thank you for taking the initiative Lewis. +1 I think we can go ahead with
> 1.0. Last time when I checked the main branch had one test failure and
> maybe we should fix that before the release.
>
> On Sat, Apr 6, 2024 at 2:39 AM lewis john mcgibbney 
> wrote:
>
>> Hi dev@,
>> What is the current status of Gora with regards to rolling a 0.10? Or
>> Maybe
>> a 1.0?
>> Thanks
>> lewismc
>>
>> --
>> http://home.apache.org/~lewismc/
>> http://people.apache.org/keys/committer/lewismc
>>
>

[DISCUSS] Interest in rolling a release

[lewis john mcgibbney]

Hi dev@,
What is the current status of Gora with regards to rolling a 0.10? Or Maybe
a 1.0?
Thanks
lewismc

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Commented] (GORA-405) Create Gora OpenAPI specification

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-405:
---

Hi Kevin, please ping me if you would like input on this. Thanks

> Create Gora OpenAPI specification
> -
>
> Key: GORA-405
> URL: https://issues.apache.org/jira/browse/GORA-405
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-compiler, gora-core
>Reporter: Udesh Liyanaarachchi
>Assignee: Udesh Liyanaarachchi
>Priority: Minor
>  Labels: gsoc2019, outreachy2021
> Fix For: 1.0
>
>
> As to the discussion [~lewismc]  initiated in the 
> [mail list 
> thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we 
> need to implement a REST API for GORA.
> This is the initial proposal documentation for the [GORA REST 
> API|http://docs.apachegoraapi.apiary.io/].
> The plan will be to implement the API with  [Apache CXF 
> |http://cxf.apache.org] using [CXF's JAXRS 
> |http://cxf.apache.org/docs/jax-rs.html] implementation.



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

[jira] [Commented] (GORA-405) Create Gora REST API

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-405:
---

Hi Kevin,
This can be renamed to “Create Gora OpenAPI specification”

On Wed, Oct 6, 2021 at 09:12 Kevin Ratnasekera (Jira) 

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc


> Create Gora REST API
> 
>
> Key: GORA-405
> URL: https://issues.apache.org/jira/browse/GORA-405
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-compiler, gora-core
>Reporter: Udesh Liyanaarachchi
>Assignee: Udesh Liyanaarachchi
>Priority: Minor
>  Labels: gsoc2019, outreachy2021
> Fix For: 1.0
>
>
> As to the discussion [~lewismc]  initiated in the 
> [mail list 
> thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we 
> need to implement a REST API for GORA.
> This is the initial proposal documentation for the [GORA REST 
> API|http://docs.apachegoraapi.apiary.io/].
> The plan will be to implement the API with  [Apache CXF 
> |http://cxf.apache.org] using [CXF's JAXRS 
> |http://cxf.apache.org/docs/jax-rs.html] implementation.



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

[jira] [Resolved] (GORA-679) Restlet JARs and third party dependencies aren’t available in the main public Maven repository

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-679.
---
Resolution: Fixed

This fixed the build. Good job folks. 

> Restlet JARs and third party dependencies aren’t available in the main public 
> Maven repository
> --
>
> Key: GORA-679
> URL: https://issues.apache.org/jira/browse/GORA-679
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Assignee: Kevin Ratnasekera
>Priority: Blocker
> Fix For: 1.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The CI process complains about the following issue which ultimately fails the 
> builds
> {code:bash}
> Error:  Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-default-http-blocker 
> (http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet 
> (http://maven.restlet.org, default, releases+snapshots), apache.snapshots 
> (http://repository.apache.org/snapshots, default, disabled)] -> [Help 1]
> {code}
> I took at look at the [Restlet 
> website|https://restlet.talend.com/downloads/current/] and discovered the 
> following
> {quote}The Maven repository for Restlet is accessible from 
> https://maven.restlet.talend.com and contains all Restlet JARs and third 
> party dependencies that aren’t available in the main public Maven repository. 
> It is automatically refreshed once a day if the build succeeds.{quote}
> So it looks like we need to update the Maven configuration to accommodate the 
> change...



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

[jira] [Assigned] (GORA-679) Restlet JARs and third party dependencies aren’t available in the main public Maven repository

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney reassigned GORA-679:
-

Assignee: Kevin Ratnasekera

> Restlet JARs and third party dependencies aren’t available in the main public 
> Maven repository
> --
>
> Key: GORA-679
> URL: https://issues.apache.org/jira/browse/GORA-679
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Assignee: Kevin Ratnasekera
>Priority: Blocker
> Fix For: 1.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The CI process complains about the following issue which ultimately fails the 
> builds
> {code:bash}
> Error:  Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-default-http-blocker 
> (http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet 
> (http://maven.restlet.org, default, releases+snapshots), apache.snapshots 
> (http://repository.apache.org/snapshots, default, disabled)] -> [Help 1]
> {code}
> I took at look at the [Restlet 
> website|https://restlet.talend.com/downloads/current/] and discovered the 
> following
> {quote}The Maven repository for Restlet is accessible from 
> https://maven.restlet.talend.com and contains all Restlet JARs and third 
> party dependencies that aren’t available in the main public Maven repository. 
> It is automatically refreshed once a day if the build succeeds.{quote}
> So it looks like we need to update the Maven configuration to accommodate the 
> change...



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

[jira] [Commented] (GORA-678) Upgrade to JDK11

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-678:
---

I'm still working this issue folks. Just slowly making my way through the 
Javadoc issues... there are lots of them :P

> Upgrade to JDK11
> 
>
> Key: GORA-678
> URL: https://issues.apache.org/jira/browse/GORA-678
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Context is at the following mailing list thread
> https://lists.apache.org/list.html?dev@gora.apache.org
> I cannot build Gora under the following environment
> {code:bash}
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
> 2018-10-24T11:41:47-07:00)
> Maven home: /usr/local/Cellar/maven/3.6.0/libexec
> Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"
> {code}



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

[jira] [Resolved] (GORA-457) Implement Normalized Discounted Cumulative Gain (nDCG) as an Example

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-457.
---
Resolution: Won't Fix

> Implement Normalized Discounted Cumulative Gain (nDCG) as an Example 
> -
>
> Key: GORA-457
> URL: https://issues.apache.org/jira/browse/GORA-457
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-tutorial
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> I have been very interested in the [Normalized Discounted Cumulative 
> Gain|https://en.wikipedia.org/wiki/Discounted_cumulative_gain] (nDCG) 
> algorithm for addressing problems within the domain of federated web search. 
> I am very keen to get a working example/tutorial and implement nDCG within 
> Gora which would extend the work I did on using Gora as a query broking 
> device. 
> This issue will implement a tutorial for ... using Gora as a query broker 
> within a federated search scenario with the emphasis being on utilization of 
> our FilterList API's.



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

[jira] [Resolved] (GORA-236) Implement a JSON/Java-to-XML mapping tool to auto-generate gora-*-mapping.xml files

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-236.
---
Resolution: Won't Fix

> Implement a JSON/Java-to-XML mapping tool to auto-generate gora-*-mapping.xml 
> files
> ---
>
> Key: GORA-236
> URL: https://issues.apache.org/jira/browse/GORA-236
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: avro, build process, gora-core, maven, schema
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.0
>
>
> The idea here is to lower the barrier for entry for folks wishing to get up 
> and running with Gora.
> Currently when pulling Gora Maven artifacts, the confiuguration process is 
> 'usually' as follows
> * write your gora.properties file
> * write your .avsc which effectively determines your data and persistence 
> model and storage characteristics
> * generate your data store specific 
> gora-${insert_data_store_here}-mapping.xml file
> I think it would be real nice if we could provide a data modelling tool which 
> effectively can run within the GoraCompiler phase of the data modelling and 
> persistent code generation phase of the Gora lifecycle.
> Effectively what this would require is some tool which would compliment the 
> GoraCompiler and would auto generate a template for your mapping file with 
> default attributes, values, etc.
> I think (and hope) that such a tool would enable us to lower the barrier 
> further for new folk wish to use Gora within their pipeline to persist data 
> somewhere.
> On my travels, I came across Xstream [0], which (AFAIK) reads JSON and 
> produces XML. Maybe this could be utilized to achieve the above.  
> [0] http://xstream.codehaus.org/



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

[jira] [Resolved] (GORA-382) Create a datastore for OPeNDAP

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-382.
---
Resolution: Won't Fix

> Create a datastore for OPeNDAP
> --
>
> Key: GORA-382
> URL: https://issues.apache.org/jira/browse/GORA-382
> Project: Apache Gora
>  Issue Type: New Feature
>        Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.0
>
>
> A while ago I logged GORA-342.
> I recently logged CLIMATE-522 which would enable Apache Open Climate 
> Workbench to hook up with many more datastores than it currently does.
> If we open up Gora to scientific datasets then we can increase our user base.
> I propose that this issue tracks the development of a datastore for OPeNDAP 
> [0] which utilizes the Java API [1] to interact with the data access protocol.
> As part of this issue, hopefully I can get someone excited about GORA-342 :)
> [0] http://www.opendap.org/
> [1] https://github.com/Unidata/thredds/tree/5.0.0/opendap



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

[jira] [Updated] (GORA-382) Create a datastore for OPeNDAP

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-382:
--
Issue Type: New Feature  (was: Bug)

> Create a datastore for OPeNDAP
> --
>
> Key: GORA-382
> URL: https://issues.apache.org/jira/browse/GORA-382
> Project: Apache Gora
>  Issue Type: New Feature
>        Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.0
>
>
> A while ago I logged GORA-342.
> I recently logged CLIMATE-522 which would enable Apache Open Climate 
> Workbench to hook up with many more datastores than it currently does.
> If we open up Gora to scientific datasets then we can increase our user base.
> I propose that this issue tracks the development of a datastore for OPeNDAP 
> [0] which utilizes the Java API [1] to interact with the data access protocol.
> As part of this issue, hopefully I can get someone excited about GORA-342 :)
> [0] http://www.opendap.org/
> [1] https://github.com/Unidata/thredds/tree/5.0.0/opendap



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

[jira] [Commented] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-672:
---

Yes [~LutzWeischerFujitsu] the following works just fine

{code:bash}
mvn -pl '!gora-kudu' install
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Gora[pom]
[INFO] Apache Gora :: Compiler [bundle]
[INFO] Apache Gora :: Compiler-CLI [bundle]
[INFO] Apache Gora :: Core [bundle]
[INFO] Apache Gora :: Pig  [bundle]
[INFO] Apache Gora :: Accumulo [bundle]
[INFO] Apache Gora :: HBase[bundle]
[INFO] Apache Gora :: Cassandra - CQL  [bundle]
[INFO] Apache Gora :: GoraCI  [jar]
[INFO] Apache Gora :: Infinispan   [bundle]
[INFO] Apache Gora :: JCache   [bundle]
[INFO] Apache Gora :: OrientDB [bundle]
[INFO] Apache Gora :: Lucene   [bundle]
[INFO] Apache Gora :: Dynamodb [bundle]
[INFO] Apache Gora :: CouchDB  [bundle]
[INFO] Apache Gora :: Maven Plugin [bundle]
[INFO] Apache Gora :: MongoDB  [bundle]
[INFO] Apache Gora :: Solr [bundle]
[INFO] Apache Gora :: Aerospike[bundle]
[INFO] Apache Gora :: Ignite   [bundle]
[INFO] Apache Gora :: Hive [bundle]
[INFO] Apache Gora :: Redis[bundle]
[INFO] Apache Gora :: Jet  [bundle]
[INFO] Apache Gora :: RethinkDB[bundle]
[INFO] Apache Gora :: Tutorial [bundle]
[INFO] Apache Gora Benchamark Module  [jar]
[INFO] Apache Gora :: Sources-Dist[jar]
...
{code}


> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Affects Versions: 1.0
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ..

[jira] [Commented] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-672:
---

You can try this

https://stackoverflow.com/questions/8304110/skip-a-submodule-during-a-maven-build#27177197

Make the substitution for the ‘gora-kudu’ module.

I also got lots of feedback on the thread I created in the Kudu mailing
list so please check that out.
Thank you


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc


> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Affects Versions: 1.0
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using t

[jira] [Updated] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-672:
--
Affects Version/s: 1.0

> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :gora-solr
> (base) [jw@cn06 gora]$ 



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

[jira] [Commented] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-672:
---

I also went ahead and started the following thread
https://lists.apache.org/thread.html/r097d20f284c5d8736c92b0ad66e6ab057393bbb860c390759924de90%40%3Cuser.kudu.apache.org%3E
[~LutzWeischerFujitsu]

> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :gora-solr
> (base) [jw@cn06 gora]$ 



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

[jira] [Updated] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-672:
--
Component/s: gora-kudu

> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-kudu
>Affects Versions: 1.0
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :gora-solr
> (base) [jw@cn06 gora]$ 



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

[jira] [Commented] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-672:
---

Hi [~LutzWeischerFujitsu] here are some of my thoughts
1. Clearly the *org.apache.kudu:kudu-binary:jar:linux-aarch_64:1.9.0* artifact 
does not exist... we could possibly approach the kudu project and notify them 
about this... but that is outside of my wheelhouse as I have never used kudu 
before...
2. As a workaround, you could [comment out the gora-kudu module in 
pom.xml|https://github.com/apache/gora/blob/master/pom.xml#L802]
In the short term could you please try #2 and maybe consider #1?

> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the err

[jira] [Commented] (GORA-682) gora-hbase The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, no dependency information available

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-682:
---

https://stackoverflow.com/questions/51403167/repository-version-policy-ignore-missing-poms

> gora-hbase The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> 
>
> Key: GORA-682
> URL: https://issues.apache.org/jira/browse/GORA-682
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> {code:bash}
>  Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b11-SNAPSHOT is 
> missing, no dependency information available
> {code}



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

[jira] [Commented] (GORA-664) Add datastore for Elasticsearch

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-664:
---

https://github.com/apache/gora/pull/234

> Add datastore for Elasticsearch
> ---
>
> Key: GORA-664
> URL: https://issues.apache.org/jira/browse/GORA-664
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Carlos Muñoz
>Assignee: Mariia Podorvanova
>Priority: Major
>  Labels: outreachy2020
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Elasticsearch is a Lucene-based search engine that primarily focuses on 
> distribution and availability. It could be a good alternative for the 
> gora-solr module.
>  
> [https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html] 



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

[jira] [Commented] (GORA-672) build failed on AArch64, Fedora 33

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-672:
---

[~LutzWeischerFujitsu] can you please try this again against master branch?

> build failed on AArch64, Fedora 33 
> ---
>
> Key: GORA-672
> URL: https://issues.apache.org/jira/browse/GORA-672
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: Lutz Weischer
>Priority: Major
>
> (base) [jw@cn06 gora]$ mvn install -DskipTests
> ...
> [INFO] 
> 
> [INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Gora  SUCCESS [  5.448 
> s]
> [INFO] Apache Gora :: Compiler  SUCCESS [  3.258 
> s]
> [INFO] Apache Gora :: Compiler-CLI  SUCCESS [  1.181 
> s]
> [INFO] Apache Gora :: Core  SUCCESS [ 19.240 
> s]
> [INFO] Apache Gora :: Pig . SUCCESS [  7.219 
> s]
> [INFO] Apache Gora :: Accumulo  SUCCESS [ 11.858 
> s]
> [INFO] Apache Gora :: HBase ... SUCCESS [ 13.320 
> s]
> [INFO] Apache Gora :: Cassandra - CQL . SUCCESS [ 15.044 
> s]
> [INFO] Apache Gora :: GoraCI .. SUCCESS [ 10.230 
> s]
> [INFO] Apache Gora :: Infinispan .. SUCCESS [ 10.865 
> s]
> [INFO] Apache Gora :: JCache .. SUCCESS [  8.791 
> s]
> [INFO] Apache Gora :: OrientDB  SUCCESS [ 10.989 
> s]
> [INFO] Apache Gora :: Lucene .. SUCCESS [  8.872 
> s]
> [INFO] Apache Gora :: Dynamodb  SUCCESS [ 11.817 
> s]
> [INFO] Apache Gora :: CouchDB . SUCCESS [ 11.528 
> s]
> [INFO] Apache Gora :: Maven Plugin  SUCCESS [  8.989 
> s]
> [INFO] Apache Gora :: MongoDB . SUCCESS [ 10.383 
> s]
> [INFO] Apache Gora :: Solr  FAILURE [  2.257 
> s]
> [INFO] Apache Gora :: Aerospike ... SKIPPED
> [INFO] Apache Gora :: Ignite .. SKIPPED
> [INFO] Apache Gora :: Kudu  SKIPPED
> [INFO] Apache Gora :: Hive  SKIPPED
> [INFO] Apache Gora :: Redis ... SKIPPED
> [INFO] Apache Gora :: Jet . SKIPPED
> [INFO] Apache Gora :: RethinkDB ... SKIPPED
> [INFO] Apache Gora :: Tutorial  SKIPPED
> [INFO] Apache Gora Benchamark Module .. SKIPPED
> [INFO] Apache Gora :: Sources-Dist  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  02:54 min
> [INFO] Finished at: 2021-03-26T11:04:19+01:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-restlet 
> (https://maven.restlet.org): transfer failed for 
> https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.1/org.restlet-2.3.1.pom,
>  proxy: ProxyInfo{host='', userName='null', port=, 
> type='https', nonProxyHosts='null'}: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed: 
> NotAfter: Wed Jan 13 14:46:20 CET 2021 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :gora-solr
> (base) [jw@cn06 gora]$ 



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

[jira] [Resolved] (GORA-686) Add .asf.yaml file to Gora repository

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-686.
---
Resolution: Fixed

> Add .asf.yaml file to Gora repository
> -
>
> Key: GORA-686
> URL: https://issues.apache.org/jira/browse/GORA-686
> Project: Apache Gora
>  Issue Type: Improvement
>        Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Trivial
> Fix For: 1.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Will improve integration between JIRA and Github
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features



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

[jira] [Created] (GORA-686) Add .asf.yaml files to Gora repository

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-686:
-

 Summary: Add .asf.yaml files to Gora repository
 Key: GORA-686
 URL: https://issues.apache.org/jira/browse/GORA-686
 Project: Apache Gora
  Issue Type: Improvement
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
 Fix For: 1.0


Will improve integration between JIRA and Github
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features



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

[jira] [Updated] (GORA-678) Upgrade to JDK11

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-678:
--
Description: 
Context is at the following mailing list thread

https://lists.apache.org/list.html?dev@gora.apache.org

I cannot build Gora under the following environment

{code:bash}
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T11:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"
{code}


  was:
Context is at the following mailing list thread

https://lists.apache.org/list.html?dev@gora.apache.org

I cannot build Gora under the following environment

Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T11:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"


> Upgrade to JDK11
> 
>
> Key: GORA-678
> URL: https://issues.apache.org/jira/browse/GORA-678
> Project: Apache Gora
>      Issue Type: Improvement
>  Components: build process
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Context is at the following mailing list thread
> https://lists.apache.org/list.html?dev@gora.apache.org
> I cannot build Gora under the following environment
> {code:bash}
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
> 2018-10-24T11:41:47-07:00)
> Maven home: /usr/local/Cellar/maven/3.6.0/libexec
> Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"
> {code}



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

[jira] [Updated] (GORA-681) Address use of deprectated APIs in gora-pig

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-681:
--
Parent: GORA-678
Issue Type: Sub-task  (was: Improvement)

> Address use of deprectated APIs in gora-pig
> ---
>
> Key: GORA-681
> URL: https://issues.apache.org/jira/browse/GORA-681
> Project: Apache Gora
>  Issue Type: Sub-task
>  Components: gora-pig
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> {code:bash}
>  Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/util/PersistentUtils.java:[104,27]
>  [deprecation] Integer(int) in Integer has been deprecated
> Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[301,48]
>  [deprecation] newInstance() in Class has been deprecated
>   where T is a type-variable:
> T extends Object declared in class Class
> Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[687,114]
>  [deprecation] newInstance() in Class has been deprecated
> {code}



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

[jira] [Created] (GORA-685) gora-rethinkdb non-varargs call of varargs method with inexact argument type for last parameter;

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-685:
-

 Summary: gora-rethinkdb non-varargs call of varargs method with 
inexact argument type for last parameter;
 Key: GORA-685
 URL: https://issues.apache.org/jira/browse/GORA-685
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-rethinkdb
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0



{code:bash}
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
gora-rethinkdb ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 9 source files to 
/home/runner/work/gora/gora/gora-rethinkdb/target/classes
Warning:  
/home/runner/work/gora/gora/gora-rethinkdb/src/main/java/org/apache/gora/rethinkdb/store/RethinkDBStore.java:[290,79]
 non-varargs call of varargs method with inexact argument type for last 
parameter;
  cast to Object for a varargs call
  cast to Object[] for a non-varargs call and to suppress this warning
Warning:  
/home/runner/work/gora/gora/gora-rethinkdb/src/main/java/org/apache/gora/rethinkdb/query/RethinkDBQuery.java:[89,30]
 non-varargs call of varargs method with inexact argument type for last 
parameter;
  cast to Object for a varargs call
  cast to Object[] for a non-varargs call and to suppress this warning
{code}




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

[jira] [Created] (GORA-684) IgniteSQLBuilder.java:[124,48] non-varargs call of varargs method with inexact argument type for last parameter

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-684:
-

 Summary: IgniteSQLBuilder.java:[124,48] non-varargs call of 
varargs method with inexact argument type for last parameter
 Key: GORA-684
 URL: https://issues.apache.org/jira/browse/GORA-684
 Project: Apache Gora
  Issue Type: Improvement
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0



{code:java}
 [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ gora-ignite 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 15 source files to 
/home/runner/work/gora/gora/gora-ignite/target/classes
Warning:  
/home/runner/work/gora/gora/gora-ignite/src/main/java/org/apache/gora/ignite/utils/IgniteSQLBuilder.java:[124,48]
 non-varargs call of varargs method with inexact argument type for last 
parameter;
{code}




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

[jira] [Created] (GORA-683) maven-plugin Unsupported packaging type bundle, execution skipped

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-683:
-

 Summary: maven-plugin Unsupported packaging type bundle, execution 
skipped
 Key: GORA-683
 URL: https://issues.apache.org/jira/browse/GORA-683
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-maven-plugin, maven
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0



{code:bash}
[INFO] -< org.apache.gora:gora-maven-plugin >--
[INFO] Building Apache Gora :: Maven Plugin 1.0-SNAPSHOT[15/28]
[INFO] ---[ bundle ]---
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ gora-maven-plugin 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-versions) @ 
gora-maven-plugin ---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @ 
gora-maven-plugin ---
[INFO] 
[INFO] --- maven-plugin-plugin:3.5.2:helpmojo (help-goal) @ gora-maven-plugin 
---
Warning:  Unsupported packaging type bundle, execution skipped
{code}




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

[jira] [Commented] (GORA-682) gora-hbase The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, no dependency information available

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-682:
---

Also, 

{code:bash}
Warning:  
/home/runner/work/gora/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStoreMetadataAnalyzer.java:[89,19]
 [deprecation] finalize() in Object has been deprecated
Warning:  
/home/runner/work/gora/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStoreMetadataAnalyzer.java:[91,13]
 [deprecation] finalize() in Object has been deprecated
{code}


> gora-hbase The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> 
>
> Key: GORA-682
> URL: https://issues.apache.org/jira/browse/GORA-682
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> {code:bash}
>  Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is 
> missing, no dependency information available
> Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b11-SNAPSHOT is 
> missing, no dependency information available
> {code}



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

[jira] [Created] (GORA-682) gora-hbase The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, no dependency information available

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-682:
-

 Summary: gora-hbase The POM for 
org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing, no dependency 
information available
 Key: GORA-682
 URL: https://issues.apache.org/jira/browse/GORA-682
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-hbase
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0



{code:bash}
 Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is 
missing, no dependency information available
Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is missing, 
no dependency information available
Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is missing, 
no dependency information available
Warning:  The POM for org.glassfish:javax.el:jar:3.0.1-b11-SNAPSHOT is missing, 
no dependency information available
{code}




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

[jira] [Commented] (GORA-681) Address use of deprectated APIs in gora-pig

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-681:
---


{code:java}
Error:  Forbidden method invocation: java.lang.Integer#(int) [Deprecated 
in Java 11]
Error:in org.apache.gora.pig.util.PersistentUtils (PersistentUtils.java:104)
Error:  Forbidden method invocation: java.lang.Class#newInstance() [Deprecated 
in Java 11]
Error:in org.apache.gora.pig.GoraStorage (GoraStorage.java:301)
Error:  Forbidden method invocation: java.lang.Class#newInstance() [Deprecated 
in Java 11]
Error:in org.apache.gora.pig.GoraStorage (GoraStorage.java:687)
Error:  Scanned 13 class file(s) for forbidden API invocations (in 0.16s), 3 
error(s).
{code}


> Address use of deprectated APIs in gora-pig
> ---
>
> Key: GORA-681
> URL: https://issues.apache.org/jira/browse/GORA-681
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-pig
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> {code:bash}
>  Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/util/PersistentUtils.java:[104,27]
>  [deprecation] Integer(int) in Integer has been deprecated
> Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[301,48]
>  [deprecation] newInstance() in Class has been deprecated
>   where T is a type-variable:
> T extends Object declared in class Class
> Warning:  
> /home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[687,114]
>  [deprecation] newInstance() in Class has been deprecated
> {code}



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

[jira] [Created] (GORA-681) Address use of deprectated APIs in gora-pig

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-681:
-

 Summary: Address use of deprectated APIs in gora-pig
 Key: GORA-681
 URL: https://issues.apache.org/jira/browse/GORA-681
 Project: Apache Gora
  Issue Type: Improvement
  Components: gora-pig
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0



{code:bash}
 Warning:  
/home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/util/PersistentUtils.java:[104,27]
 [deprecation] Integer(int) in Integer has been deprecated
Warning:  
/home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[301,48]
 [deprecation] newInstance() in Class has been deprecated
  where T is a type-variable:
T extends Object declared in class Class
Warning:  
/home/runner/work/gora/gora/gora-pig/src/main/java/org/apache/gora/pig/GoraStorage.java:[687,114]
 [deprecation] newInstance() in Class has been deprecated
{code}




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

[jira] [Created] (GORA-680) Upgrade Avro from 1.8.2 --> 1.10.2

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-680:
-

 Summary: Upgrade Avro from 1.8.2 --> 1.10.2
 Key: GORA-680
 URL: https://issues.apache.org/jira/browse/GORA-680
 Project: Apache Gora
  Issue Type: Improvement
  Components: build process, gora-core
Reporter: Lewis John McGibbney
 Fix For: 1.0


Avro is a critical dependency in Gora. We should keep this dependency 
uo-to-date with the Avro project releases so we do not diverge too much.



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

[jira] [Assigned] (GORA-678) Upgrade to JDK11

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney reassigned GORA-678:
-

Assignee: Lewis John McGibbney

> Upgrade to JDK11
> 
>
> Key: GORA-678
> URL: https://issues.apache.org/jira/browse/GORA-678
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> Context is at the following mailing list thread
> https://lists.apache.org/list.html?dev@gora.apache.org
> I cannot build Gora under the following environment
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
> 2018-10-24T11:41:47-07:00)
> Maven home: /usr/local/Cellar/maven/3.6.0/libexec
> Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"



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

[jira] [Commented] (GORA-679) Restlet JARs and third party dependencies aren’t available in the main public Maven repository

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-679:
---

Hi [~djkevincr] I can't replicate this yet because I can't get Gora to build on 
JDK11 (I am working on that cf. GORA-678)
I'll report back here once I get the PR ready for that ticket.
In the meantime, do you know why the Github CI actions are failing?

> Restlet JARs and third party dependencies aren’t available in the main public 
> Maven repository
> --
>
> Key: GORA-679
> URL: https://issues.apache.org/jira/browse/GORA-679
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
>Affects Versions: 0.9
>    Reporter: Lewis John McGibbney
>Priority: Blocker
> Fix For: 1.0
>
>
> The CI process complains about the following issue which ultimately fails the 
> builds
> {code:bash}
> Error:  Failed to execute goal on project gora-solr: Could not resolve 
> dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: 
> Failed to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
> org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
> org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
> org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-default-http-blocker 
> (http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet 
> (http://maven.restlet.org, default, releases+snapshots), apache.snapshots 
> (http://repository.apache.org/snapshots, default, disabled)] -> [Help 1]
> {code}
> I took at look at the [Restlet 
> website|https://restlet.talend.com/downloads/current/] and discovered the 
> following
> {quote}The Maven repository for Restlet is accessible from 
> https://maven.restlet.talend.com and contains all Restlet JARs and third 
> party dependencies that aren’t available in the main public Maven repository. 
> It is automatically refreshed once a day if the build succeeds.{quote}
> So it looks like we need to update the Maven configuration to accommodate the 
> change...



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

[jira] [Created] (GORA-679) Restlet JARs and third party dependencies aren’t available in the main public Maven repository

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-679:
-

 Summary: Restlet JARs and third party dependencies aren’t 
available in the main public Maven repository
 Key: GORA-679
 URL: https://issues.apache.org/jira/browse/GORA-679
 Project: Apache Gora
  Issue Type: Improvement
  Components: build process
Affects Versions: 0.9
Reporter: Lewis John McGibbney
 Fix For: 1.0


The CI process complains about the following issue which ultimately fails the 
builds


{code:bash}
Error:  Failed to execute goal on project gora-solr: Could not resolve 
dependencies for project org.apache.gora:gora-solr:bundle:1.0-SNAPSHOT: Failed 
to collect dependencies at org.apache.solr:solr-core:jar:8.0.0 -> 
org.restlet.jee:org.restlet:jar:2.3.1: Failed to read artifact descriptor for 
org.restlet.jee:org.restlet:jar:2.3.1: Could not transfer artifact 
org.restlet.jee:org.restlet:pom:2.3.1 from/to maven-default-http-blocker 
(http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet 
(http://maven.restlet.org, default, releases+snapshots), apache.snapshots 
(http://repository.apache.org/snapshots, default, disabled)] -> [Help 1]
{code}


I took at look at the [Restlet 
website|https://restlet.talend.com/downloads/current/] and discovered the 
following

{quote}The Maven repository for Restlet is accessible from 
https://maven.restlet.talend.com and contains all Restlet JARs and third party 
dependencies that aren’t available in the main public Maven repository. It is 
automatically refreshed once a day if the build succeeds.{quote}

So it looks like we need to update the Maven configuration to accommodate the 
change...



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

[jira] [Created] (GORA-678) Upgrade to JDK11

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-678:
-

 Summary: Upgrade to JDK11
 Key: GORA-678
 URL: https://issues.apache.org/jira/browse/GORA-678
 Project: Apache Gora
  Issue Type: Improvement
  Components: build process
Reporter: Lewis John McGibbney
 Fix For: 1.0


Context is at the following mailing list thread

https://lists.apache.org/list.html?dev@gora.apache.org

I cannot build Gora under the following environment

Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T11:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"



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

Upgrading Gora --> JDK11

[Lewis John McGibbney]

Hi dev@,

I recently tried to build Gora with following environment

Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T11:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.10, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-11.0.10.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"

.. unfortunately things didn't go very well and the installation failed with 
the maven-javadoc-plugin complaining about various issues.

Is there any desire or motivation to upgrade to JDK11?

lewismc

Re: [PROPOSAL] Pull request hackathon

[Lewis John McGibbney]

Hi Kevin,

On 2021/05/07 18:07:01, Kevin Ratnasekera  wrote: 
> +1 I am in Lewis. I will help out, 

Excellent.

> I Apologize from my end not having much
> time to review these with recent times.

Absolutely no apology needed whatsoever. I hope you are keeping well :)

Let's see what other feedback we get and we can create the Doodle poll.
Thanks

[PROPOSAL] Pull request hackathon

[Lewis John McGibbney]

Hi dev@,
I was taking a look at the Gora pull requests.
Firsly, let me say how encouraged I am by all of the new modules... this is 
really neat! A lot of hard work has gone into producing these results.
There are quite a few open pull requests. With that in mind, I wondered if 
anyone would be interested having a virtual hackathon of sorts where we could 
openly review the open pull requests one at a time and determine what needs to 
be done to get them into master branch.
Is anyone interested in this? I so, can do a Doodle poll for availability.
Thanks
lewismc

Re: GSoc 2021 rewrite gora-sql from JOOQ Library

[lewis john mcgibbney]

Yeah I’ll take a look but unfortunately I’m not in a position to mentor
this time.
I’ll have a look and make any suggestions.
Thank you

On Mon, May 3, 2021 at 10:12 Mohamed Infaz  wrote:

> Hi Lewis,
>
> Thanks for getting back to me, yes this project is going ahead but I think
> it's in the proposal evaluation stage.
> Can you kindly provide me feedback on this project?
>
> Regards,
> Infaz.
>
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: GSoc 2021 rewrite gora-sql from JOOQ Library

[Lewis John McGibbney]

Hi Infaz,
Is this project going ahead?
Did you get an y feedback on your proposal?
Thanks
lewismc

On 2021/04/13 08:30:20, Mohamed Infaz  wrote: 
> Hi All,
> 
> I am Mohamed Infaz a computer science student who is interested in the
> above ticket to complete it as my Gsoc 2021 project.
> Ticket - https://issues.apache.org/jira/projects/GORA/issues/GORA-86
> 
> Proposal
> https://docs.google.com/document/d/1UAS1OqyJU2RjWjLYppqMx2hM8Lt6oxo0T7Q2t1cx3aw/edit?usp=sharing
> 
> 
> Please kindly let me know your feedback on the proposal and if there is
> room for improvement.
> 
> Regards,
> Infaz.
> 

Gora static source code analysis on sonarcloud.io

[Lewis John McGibbney]

Hi dev@,
Did anyone know that we 'used to' have static source code analysis activated 
https://sonarcloud.io/dashboard?id=apache_gora
I can't remember why this dropped off but it may be a good idea to try to 
integrate this with the Jenkins pipeline just a thought.
Lewis

[jira] [Commented] (GORA-675) Perform Sonar static code analysis on Jenkins

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-675:
---

+1

> Perform Sonar static code analysis on Jenkins
> -
>
> Key: GORA-675
> URL: https://issues.apache.org/jira/browse/GORA-675
> Project: Apache Gora
>  Issue Type: Task
>  Components: build process
>Reporter: Damien Raude-Morvan
>Assignee: Damien Raude-Morvan
>Priority: Minor
>
> I would like to use [https://sonarcloud.io/] in order to perform static code 
> analysis on Apache Gora project.
> This analysis should be automatically triggered on our Jenkins job as 
> described on 
> https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis



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

Re: [Gora] builds.apache.org

[lewis john mcgibbney]

Hi Damien,

On Sat, Mar 27, 2021 at 16:40  wrote:

>
> Hi all !
>
> I'm trying to catch up on the emails on this list regarding a subject that
> interests me : Gora Continuous Integration :)
>
> I'm a little confused about what we're trying to achieve here:
>
> Last year, I've spend some time to setup a multi-branch Jenkins pipeline
>  which is
> properly setup by Jenkinsfile located inside our git repository.
> Lewis just added a manual Jenkins job on master branch
>  which seems
> (AFAIK) to duplicate the purpose of the previous pipeline.
>
> For my point of view, it seems easier and more maintainable to modify
> existing Jenkinsfile in order to add support for artifacts upload, isn't it
> ?


I totally agree with this. I was not aware that this was driven by the
Jenkinsfile that you created. Let’s just update that and remove the job I
created.



> There is a Deploying Artifacts
> <
> https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes#MultibranchPipelinerecipes-DeployingArtifacts
> >
> section on Multibranch Pipeline recipes documentation from INFRA. Maybe
> someone can give it a try ?
>

I’ll certainly give it a go yes. I’ll
Report back here.
lewismc

>
> --
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [Gora] builds.apache.org

[lewis john mcgibbney]

Hi Folks,
I went ahead and created a build for master.
https://ci-builds.apache.org/job/Gora/job/gora-master/1/
Alfonso, Kevin or anyone else you should have access to the builds. If you
do not please ask infra on Slack or via email/JIRA. No access is privilege.
We should all have the same access.
Thanks guys, good work.
lewismc

On Sat, Mar 27, 2021 at 5:20 AM Alfonso Nishikawa <
alfonso.nishik...@gmail.com> wrote:

> Hi, Kevin.
>
> You are right :( probably only Lewis has access.
> Our current pipeline does not publish the snapshots to nexus. Last
> snapshot jar is from around june of last year. I can't configure it because
> I don't know how to make Jenkins deploy the snapshots jars from master
> buils :( (I don't event know how to deploy the official jars)
>
> Regards,
>
> Alfonso
>
>
> El sáb, 27 mar 2021 a las 9:57, Kevin Ratnasekera (<
> djkevincr1...@gmail.com>) escribió:
>
>> Hi Alfonso,
>>
>> I just checked the Any23 job configuration link, I get the same error
>> related to missing permissions. I think only committers of the
>> particular project are allowed to read / write access to build
>> configurations.
>>
>> Let's see whether we can find issues with our current gora-pipeline
>> configuration.
>>
>> Regards
>> Kevin
>>
>>

Re: [Gora] builds.apache.org

[Lewis John McGibbney]

Hi Alfonso,
The Gora builds now reside on the Cloudbees Jenkins server (which I think you 
already figured out)
https://ci-builds.apache.org/job/Gora/job/gora-pipeline/job/master/
I don't have time to look into configuring the job right now but if you look at 
the Any23 build we did a while back, then you can basically copy it for the 
Gora master build
https://ci-builds.apache.org/job/Any23/job/any23-master-jdk8/configure
I hope this makes sense. 
lewismc

On 2021/03/13 16:48:49, Alfonso Nishikawa  wrote: 
> Hi!
> 
> I am reopening this topic because I found that the jars master x.x-SNAPSHOT
> are not being published to the repository of snapshots at the apache
> repository
> https://repository.apache.org/#view-repositories;snapshots-group~browsestorage~org/apache/gora/gora-hbase/1.0-SNAPSHOT/
> since Jun 2020.
> 
> I guess we would need to add a "deploy" step to the Jenkins file (see
> https://github.com/apache/gora/pull/229 ,
> https://www.jenkins.io/doc/book/pipeline/jenkinsfile/) but does anyone
> exactly what command is it? Or how to configure it? Maybe I have to ask
> INFRA?
> 
> Let me know :)
> 
> Thank you!
> 
> Regards,
> Alfonso Nishikawa
> 
> 
> 
> 
> El sáb, 31 oct 2020 a las 17:28, Alfonso Nishikawa (<
> alfonso.nishik...@gmail.com>) escribió:
> 
> > All merits go for Damien :D Thanks too!
> >
> > Best regards,
> >
> > Alfonso Nishikawa
> >
> > El sáb., 31 oct. 2020 a las 16:59, Kevin Ratnasekera (<
> > djkevincr1...@gmail.com>) escribió:
> >
> >> Hi Damien/Alfonso,
> >>
> >> I just noticed the jenkins build system works just fine. Thank you for
> >> setting up builds again. :)
> >>
> >> Regards
> >> Kevin
> >>
> >> On Tue, Oct 27, 2020 at 5:27 AM Alfonso Nishikawa <
> >> alfonso.nishik...@gmail.com> wrote:
> >>
> >>> Hi, Damien.
> >>>
> >>> I really don't know anything about how to configure Jenkins, so
> >>> everything
> >>> seems ok to me n_nU
> >>>
> >>> Thank you!
> >>>
> >>> Best regards,
> >>>
> >>> Alfonso Nishikawa
> >>>
> >>> El sáb., 24 oct. 2020 a las 21:15, Damien Raude-Morvan (<
> >>> draz...@drazzib.com>)
> >>> escribió:
> >>>
> >>> > Hi Kevin & Alfonso !
> >>> >
> >>> > I've pretty good experience regarding creating Jenkinsfile for Java
> >>> > projects. I think this is the way to go for Gora.
> >>> >
> >>> > This approach is described on ASF wiki : Multibranch Pipeline recipes
> >>> > <
> >>> >
> >>> https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes
> >>> > >
> >>> >
> >>> > I've created a new issue (GORA-668
> >>> > ) on this subject
> >>> >
> >>> > Regards,
> >>> >
> >>> > Le sam. 24 oct. 2020 à 14:46, Kevin Ratnasekera <
> >>> djkevincr1...@gmail.com>
> >>> > a
> >>> > écrit :
> >>> >
> >>> > > Hi Alfonso,
> >>> > >
> >>> > > Apologize for taking time to respond to your email. Thank you for
> >>> taking
> >>> > > over this and creating the ticket. Let's see what we can do, once
> >>> INFRA
> >>> > > responds back to the ticket.
> >>> > >
> >>> > > Regards
> >>> > > Kevin
> >>> > >
> >>> > > On Sat, Oct 24, 2020 at 5:45 PM Alfonso Nishikawa <
> >>> > > alfonso.nishik...@gmail.com> wrote:
> >>> > >
> >>> > > > Created: https://issues.apache.org/jira/browse/INFRA-21024
> >>> > > >
> >>> > > > Now we just have to wait, and I believe we would have to create
> >>> some
> >>> > jobs
> >>> > > > after? If I am not wrong, Infra does not create the jobs, but I
> >>> hope I
> >>> > am
> >>> > > > mistaken :)
> >>> > > >
> >>> > > > Best regards,
> >>> > > >
> >>> > > > Alfonso Nishikawa
> >>> > > >
> >>> > > > El sáb., 24 oct. 2020 a las 12:06, Alfonso Nishikawa (<
> >>> > > > alfonso.nishik...@gmail.com>) escribió:
> >>> > > >
> >>> > > > > Hi, Damien.
> >>> > > > >
> >>> > > > > Yes, I will create the ticket :) Let's see if I manage to get it
> >>> > done,
> >>> > > > > since I never wrote to Infra :)
> >>> > > > >
> >>> > > > > Thank you!
> >>> > > > >
> >>> > > > > Best regards,
> >>> > > > >
> >>> > > > > Alfonso Nishikawa
> >>> > > > >
> >>> > > > > El vie., 23 oct. 2020 a las 19:38, Damien Raude-Morvan (<
> >>> > > > > draz...@drazzib.com>) escribió:
> >>> > > > >
> >>> > > > >> Hi Alfonso!
> >>> > > > >>
> >>> > > > >> Gora builds used to be at
> >>> https://builds.apache.org/job/gora-trunk/
> >>> > > > >> but it seems that the old Jenkins instance has been dropped...
> >>> > > > >>
> >>> > > > >> I've find a reference on this subject on build@
> >>> > > > >> => [IMPORTANT] - Migration to ci-builds.a.o
> >>> > > > >> <
> >>> > > > >>
> >>> > > >
> >>> > >
> >>> >
> >>> https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> >>> > > > >> >
> >>> > > > >>
> >>> > > > >> Alfonso, if you have time, can you please a ticket in order to
> >>> > > re-create
> >>> > > > >> our job ?
> >>> > > > >>
> >>> > > > >> Best regards,
> >>> > > > >>
> >>> > > > >> Le jeu. 22 oct. 2020 à 18:35, Alfonso Nishikawa <
> >>> > > > >> 

Re: [Discuss] Apache Gora Next Release

[lewis john mcgibbney]

Excellent work folks.
I would suggest activating dependabot on the Gora repository. It may make
our lives a bit easier to keep on top of dependency management.
lewismc

On Sun, Mar 21, 2021 at 6:02 AM  wrote:

>
> dev Digest 21 Mar 2021 13:02:16 - Issue 1401
>
> Topics (messages 13057 through 13057)
>
> Re: [Discuss] Apache Gora Next Release
> 13057 by: Madhawa Gunasekara
>
> Administrivia:
>
> -
> To post to the list, e-mail: dev@gora.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscr...@gora.apache.org
> For additional commands, e-mail: dev-digest-h...@gora.apache.org
>
> --
>
>
>
>
> -- Forwarded message --
> From: Madhawa Gunasekara 
> To: "" 
> Cc:
> Bcc:
> Date: Fri, 19 Mar 2021 12:59:48 +0100
> Subject: Re: [Discuss] Apache Gora Next Release
> Hi,
>
> I believe we have enough features to do a release. In the meantime, we need
> to upgrade all the dependency versions as well.  We have to merge the last
> GSOC Project PRs and Outreachy PRs as well, after that we can produce a
> release candidate. WDYT?
>
> Thanks,
> Madhawa
>
>
> On Fri, Mar 19, 2021 at 10:31 AM Alfonso Nishikawa <
> alfonso.nishik...@gmail.com> wrote:
>
> > Hi!
> >
> > I have nothing to add, but will read this thread with expectancy =)
> >
> > Thank you!
> >
> > Regards,
> > Alfonso Nishikawa
> >
> > El mar., 2 mar. 2021 8:28, Kevin Ratnasekera 
> > escribió:
> >
> > > Hi all,
> > >
> > > This is to initiate a discussion on $subject. I think there's
> > considerable
> > > work already merged to master branch. Is there anything else we want to
> > > include in the Gora 1.0 development drive or can we go ahead and
> produce
> > a
> > > release candidate?
> > >
> > > Regards
> > > Kevin
> > >
> >
>


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

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

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-338:
---

Hi [~suwindev19] thanks for your interest. Of course you can assist here. 

The Gora website resides in Subversion and can be accessed at 
http://svn.apache.org/repos/asf/gora/site/trunk/content/current/gora-dynamodb.md
Do you know how to use Subversion?

> 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
>
>
> 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

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-455:
---

Are you still interested in addressing this issue ![~arqgabyortiz]? Thanks for 
your interest. 

> 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] [Resolved] (GORA-213) Document every method in GoraCompiler

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-213.
---
Resolution: Fixed

Thank you [~mariia.podorvanova]

Addressed https://github.com/apache/gora/pull/224

> Document every method in GoraCompiler
> -
>
> Key: GORA-213
> URL: https://issues.apache.org/jira/browse/GORA-213
> Project: Apache Gora
>  Issue Type: Bug
>  Components: documentation, gora-core
>Affects Versions: 0.2.1
>    Reporter: Lewis John McGibbney
>Assignee: Mariia Podorvanova
>Priority: Trivial
> Fix For: 1.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This is a rather trivial affair, but concerns an attempt to clean up 
> GoraCompiler.
> I know I for one have struggled in the past to get to grips to GoraCompiler, 
> and honestly, additional class specific strung utility like methods really do 
> not help in the slightest. 



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

[jira] [Assigned] (GORA-213) Document every method in GoraCompiler

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney reassigned GORA-213:
-

Assignee: Mariia Podorvanova

> Document every method in GoraCompiler
> -
>
> Key: GORA-213
> URL: https://issues.apache.org/jira/browse/GORA-213
> Project: Apache Gora
>  Issue Type: Bug
>  Components: documentation, gora-core
>Affects Versions: 0.2.1
>    Reporter: Lewis John McGibbney
>Assignee: Mariia Podorvanova
>Priority: Trivial
> Fix For: 1.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This is a rather trivial affair, but concerns an attempt to clean up 
> GoraCompiler.
> I know I for one have struggled in the past to get to grips to GoraCompiler, 
> and honestly, additional class specific strung utility like methods really do 
> not help in the slightest. 



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

[jira] [Resolved] (GORA-539) Gora Website is not fully secure

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-539.
---
Resolution: Not A Problem

This issue is no longer a problem. 

> Gora Website is not fully secure
> 
>
> Key: GORA-539
> URL: https://issues.apache.org/jira/browse/GORA-539
> Project: Apache Gora
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Cihad Guzel
>Priority: Major
> Fix For: 1.0
>
>
> Chrome console show some error as follow:
>  
> "Mixed Content: The page at '[https://gora.apache.org/]' was loaded over 
> HTTPS, but requested an insecure script 
> '[http://w.sharethis.com/button/buttons.js]'. This request has been blocked; 
> the content must be served over HTTPS."
>  
> etc..



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

[jira] [Commented] (GORA-539) Gora Website is not fully secure

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-539:
---

Gora Website resides at http://svn.apache.org/repos/asf/gora/site/
Best way to address this issue is to remove the sharethis widget from the 
Website

> Gora Website is not fully secure
> 
>
> Key: GORA-539
> URL: https://issues.apache.org/jira/browse/GORA-539
> Project: Apache Gora
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Cihad Guzel
>Priority: Major
> Fix For: 1.0
>
>
> Chrome console show some error as follow:
>  
> "Mixed Content: The page at '[https://gora.apache.org/]' was loaded over 
> HTTPS, but requested an insecure script 
> '[http://w.sharethis.com/button/buttons.js]'. This request has been blocked; 
> the content must be served over HTTPS."
>  
> etc..



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

Re: Your project's website

[lewis john mcgibbney]

Hi Andrew,
Yes this issue does affect the Gora website so we need to transition to a
new framework.

dev@,
Does anyone have a preference of which website framework we should use?

Thanks

On Wed, Aug 5, 2020 at 5:16 AM  wrote:

>
> From: Andrew Wetmore 
> To: dev@gora.apache.org
> Cc:
> Bcc:
> Date: Wed, 5 Aug 2020 09:16:17 -0300
> Subject: Your project's website
> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if so,
> who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Github actions for Gora Github

[lewis john mcgibbney]

Hi dev@,
I really like the use of Github Actions to test incoming PR's.
Who turned this on? Is this documented anywhere?I also think we could
execute a source code formatting check and maybe even findbugs or similar.
Any thoughts?
Thanks

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Resolved] (GORA-662) 파워볼 총판 모집

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-662.
---
Resolution: Invalid

> 파워볼 총판 모집
> -
>
> Key: GORA-662
> URL: https://issues.apache.org/jira/browse/GORA-662
> Project: Apache Gora
>  Issue Type: Bug
>Reporter: leehyunsoo
>Priority: Major
>
> [파워볼 총판|https://toto-town.com/] 모집!! 총판 모집!! 총판 구인구직에 최적화 된 토토총판 커뮤니티입니다! 
> 사설토토 총판 회원님에게 총판 정산금 먹튀 업체, 먹튀사이트 정보 제공과 총판 활동에 도움되는 안전한 보증 업체까지 소개해 드리는 총판 
> 커뮤니티 토토 타운입니다! 



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

[WELCOME] Sheriffo Ceesay to Gora PMC and Committership

[lewis john mcgibbney]

Hi dev@,
I'm very happy to welcome Sheriffo Ceesay to our ranks. Sheriffo was one of
our GSoC students this year with his work resulting in a benchmarking
module based on Yahoo!'s Cloud Serving Benchmark [0].
Sheriffo is finishing off his Ph.D. at the University of St. Andrews, in my
mother country of Scotland and has mentioned that he will be pretty quiet
until that is done. I personally with you the very best with that.
Sheriffo, once your account is created it is customary to commit your
details to the Gora parent pom.xml [1]. If you need some assistance with
that then please let me know.
Lewis

[0] https://github.com/apache/gora/tree/master/gora-benchmark
[1] https://github.com/apache/gora/blob/master/pom.xml#L53

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Updated] (GORA-637) Upgrade all dependencies and Maven plugins

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-637:
--
Environment: 
lmcgibbn@MT-207576 ~/Downloads/gora(master) $ mvn --version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
2018-10-24T11:41:47-07:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 13, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-13.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"

> Upgrade all dependencies and Maven plugins
> --
>
> Key: GORA-637
> URL: https://issues.apache.org/jira/browse/GORA-637
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: build process
> Environment: lmcgibbn@MT-207576 ~/Downloads/gora(master) $ mvn 
> --version
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
> 2018-10-24T11:41:47-07:00)
> Maven home: /usr/local/Cellar/maven/3.6.0/libexec
> Java version: 13, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk-13.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"
>Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> This is a major issue and will require peer review from as many people as 
> possible. It essentially uses the the following commands to mass upgrade all 
> dependencies and plugins as follows
> {code}
> mvn versions:update-properties
> mvn versions:update-child-modules
> {code}



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

[jira] [Created] (GORA-637) Upgrade all dependencies and Maven plugins

[Lewis John McGibbney (Jira)]

Lewis John McGibbney created GORA-637:
-

 Summary: Upgrade all dependencies and Maven plugins
 Key: GORA-637
 URL: https://issues.apache.org/jira/browse/GORA-637
 Project: Apache Gora
  Issue Type: Improvement
  Components: build process
Reporter: Lewis John McGibbney
 Fix For: 1.0


This is a major issue and will require peer review from as many people as 
possible. It essentially uses the the following commands to mass upgrade all 
dependencies and plugins as follows
{code}
mvn versions:update-properties
mvn versions:update-child-modules
{code}



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

[jira] [Resolved] (GORA-532) Benchmarking Module

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-532.
---
Resolution: Fixed

Thank you [~Sheriffo]... good job.

> Benchmarking Module
> ---
>
> Key: GORA-532
> URL: https://issues.apache.org/jira/browse/GORA-532
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Furkan KAMACI
>Assignee: Sheriffo Ceesay
>Priority: Major
>  Labels: gsoc2018, gsoc2019
> Fix For: 1.0
>
>  Time Spent: 26.5h
>  Remaining Estimate: 0h
>
> We should make a benchmark and publish it, and improved version of the 
> Yahoo!’s Cloud Serving Benchmark (YCSB++) [1] is the most suitable tool for 
> such a purpose. Here is a recent research about Object-NoSQL Database Mapper 
> (ONDM) benchmark [2] which includes Apache Gora and they have produced the 
> benchmark source code as ASF 2.0 licensed [3].
>  
> Also, here is an example from Apache Accumulo which is based on YCSB [4].
>  
> [1] [http://www.cs.cmu.edu/~wtantisi/files/tablebenchmark-pdl11-talk.pdf]
> [2] [https://doi.org/10.1186/s13174-016-0052-x]
> [3] [https://github.com/vreniers/ONDM-Benchmarker]
> [4] [https://accumulo.apache.org/papers/accumulo-benchmarking-2.1.pdf]



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

[jira] [Assigned] (GORA-532) Benchmarking Module

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney reassigned GORA-532:
-

Assignee: Sheriffo Ceesay  (was: Furkan KAMACI)

> Benchmarking Module
> ---
>
> Key: GORA-532
> URL: https://issues.apache.org/jira/browse/GORA-532
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Furkan KAMACI
>Assignee: Sheriffo Ceesay
>Priority: Major
>  Labels: gsoc2018, gsoc2019
> Fix For: 1.0
>
>  Time Spent: 26.5h
>  Remaining Estimate: 0h
>
> We should make a benchmark and publish it, and improved version of the 
> Yahoo!’s Cloud Serving Benchmark (YCSB++) [1] is the most suitable tool for 
> such a purpose. Here is a recent research about Object-NoSQL Database Mapper 
> (ONDM) benchmark [2] which includes Apache Gora and they have produced the 
> benchmark source code as ASF 2.0 licensed [3].
>  
> Also, here is an example from Apache Accumulo which is based on YCSB [4].
>  
> [1] [http://www.cs.cmu.edu/~wtantisi/files/tablebenchmark-pdl11-talk.pdf]
> [2] [https://doi.org/10.1186/s13174-016-0052-x]
> [3] [https://github.com/vreniers/ONDM-Benchmarker]
> [4] [https://accumulo.apache.org/papers/accumulo-benchmarking-2.1.pdf]



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

[jira] [Resolved] (GORA-623) Javadoc build fails with Gora master branch

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-623.
---
Resolution: Fixed

Thank you [~chanakadkb]

> Javadoc build fails with Gora master branch
> ---
>
> Key: GORA-623
> URL: https://issues.apache.org/jira/browse/GORA-623
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 0.9
> Environment: commit ID: 9b1d297fc11f90850d0360c93b3bd65486a20834
>    Reporter: Lewis John McGibbney
>Assignee: Chanaka
>Priority: Critical
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We should really add a _*mvn javadoc:aggregate*_ command to our master branch 
> build.
> {code}
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate (default-cli) 
> on project gora: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/store/DataStore.java:144:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   boolean exists(K key) throws GoraException;
> [ERROR]   ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/Query.java:50:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   Result execute() throws GoraException;
> [ERROR]^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:62:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   public BeanFactoryImpl(Class keyClass, Class persistentClass) 
> throws GoraException {
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:82:
>  warning: no description for @param
> [ERROR]* @param keyClass
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:85:
>  warning: no description for @throws
> [ERROR]* @throws GoraException
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/Persistent.java:131:
>  warning: no description for @throws
> [ERROR]* @throws CloneNotSupportedException
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:74:
>  warning: no @param for index
> [ERROR]   public String getField(int index) {
> [ERROR] ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:82:
>  warning: no @param for field
> [ERROR]   public int getFieldIndex(String field) {
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:84:
>  warning: no description for @return
> [ERROR]* @return
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:262:
>  warning: no description for @return
> [ERROR]* @return
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:270:
>  warning: no description for @param
> [ERROR]* @param auth
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for baseQuery
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for startKey
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for endKey
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQ

[jira] [Assigned] (GORA-623) Javadoc build fails with Gora master branch

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney reassigned GORA-623:
-

Assignee: Chanaka

> Javadoc build fails with Gora master branch
> ---
>
> Key: GORA-623
> URL: https://issues.apache.org/jira/browse/GORA-623
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 0.9
> Environment: commit ID: 9b1d297fc11f90850d0360c93b3bd65486a20834
>    Reporter: Lewis John McGibbney
>Assignee: Chanaka
>Priority: Critical
> Fix For: 1.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We should really add a _*mvn javadoc:aggregate*_ command to our master branch 
> build.
> {code}
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate (default-cli) 
> on project gora: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/store/DataStore.java:144:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   boolean exists(K key) throws GoraException;
> [ERROR]   ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/Query.java:50:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   Result execute() throws GoraException;
> [ERROR]^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:62:
>  warning: no @throws for org.apache.gora.util.GoraException
> [ERROR]   public BeanFactoryImpl(Class keyClass, Class persistentClass) 
> throws GoraException {
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:82:
>  warning: no description for @param
> [ERROR]* @param keyClass
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:85:
>  warning: no description for @throws
> [ERROR]* @throws GoraException
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/Persistent.java:131:
>  warning: no description for @throws
> [ERROR]* @throws CloneNotSupportedException
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:74:
>  warning: no @param for index
> [ERROR]   public String getField(int index) {
> [ERROR] ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:82:
>  warning: no @param for field
> [ERROR]   public int getFieldIndex(String field) {
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:84:
>  warning: no description for @return
> [ERROR]* @return
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:262:
>  warning: no description for @return
> [ERROR]* @return
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:270:
>  warning: no description for @param
> [ERROR]* @param auth
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for baseQuery
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for startKey
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
>  warning: no @param for endKey
> [ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
> endKey,
> [ERROR]  ^
> [ERROR] 
> /Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
> 

Fwd: [NOTICE] Introducing .asf.yaml for enhanced automation of git repository services

[lewis john mcgibbney]

-- Forwarded message -
From: Daniel Gruno 
Date: Wed, Sep 4, 2019 at 17:33
Subject: [NOTICE] Introducing .asf.yaml for enhanced automation of git
repository services
To: 


Hello, fellow Apache committers and enthusiasts!

Today, the Apache Infrastructure Team is launching new self-serve
features to help augment the productivity of Apache projects through a
series of simple configurations for enabling automation of various
service offerings.

We call this new initiative '.asf.yaml', and as the name implies, it
consists of a new file that projects can add to their git repositories
to control various aspects that were previously done through JIRA
tickets and manual operations by the Infrastructure staff.

For detailed information about these features and how to enable them,
please visit our documentation page at: https://s.apache.org/asfyaml

At launch time, .asf.yaml has three features enabled that projects can
make use of: web site staging, web site publishing, and github meta-data
settings:

web site staging:
   Much like with the Apache CMS system, projects using git can now get
   their web sites staged for previews at a specific (HTTPS-enabled)
   staging domain. Staging supports multi-tenancy, which allows for
   multiple staging web sites from different site repository branches.
   For more information on multi-tenancy, see the canonical documentation
   linked above.

web site publishing:
   Projects can now automatically set up publishing for their own main
   web site ($project.apache.org) and change at will, without the need to
   wait for assistance from the Infrastructure team. New podlings and
   projects can also get web sites bootstrapped and ready immediately.

github meta-data settings:
   Projects can now, via .asf.yaml, specify their repositories' meta-data
   on github, such as the description, homepage URL, and which topics to
   add to a repository's front page.

In the coming months, we will extend this feature with many new,
exciting features such as automated buildbot integration for web site
generation (think CMS but via git) and enhanced JIRA integration
automation.

We hope projects will appreciate and make use of these new features. If
you or your project have any questions, please feel free to reach out to
us at: us...@infra.apache.org - but please read through the
documentation first :)

With regards, and on behalf of the Apache Infrastructure Team,
Daniel.
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: YCSB dependency issue -- Plan B?

[lewis john mcgibbney]

Go for it +1
We can then merge and essentially disable the module in the build and test
until the dependency is available.
Lewis

On Thu, Aug 29, 2019 at 7:30 AM Sheriffo Ceesay 
wrote:

> All,
>
> I think getting YCSB to publish their artefacts to maven central is taking
> an unexpected amount of time. It seems they are having an infinite internal
> discussion [1], so I thought of a possible Plan B.
>
> The plan would be to auto-provision the required YCSB jar by scripting the
> current manual process that I used. This will entail, downloading the
> latest YCSB or stable source, perform a local maven install, compile and
> run some tests.
>
> If the above suggestions make sense, then I can find some time and work on
> the implementation. Alternatively, if you have a better idea, please let me
> know.
>
> Please let me know what your thoughts are.
>
> [1] https://github.com/brianfrankcooper/YCSB/issues/1340
>
> Thank you.
>
> **Sheriffo Ceesay**
>


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Commented] (GORA-538) No content stored for an object field with name "value"

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney commented on GORA-538:
---

I get successful build and test locally
{code}
[INFO] Reactor Summary for Apache Gora 1.0-SNAPSHOT:
[INFO]
[INFO] Apache Gora  SUCCESS [  1.723 s]
[INFO] Apache Gora :: Compiler  SUCCESS [  1.911 s]
[INFO] Apache Gora :: Compiler-CLI  SUCCESS [  0.846 s]
[INFO] Apache Gora :: Core  SUCCESS [01:08 min]
[INFO] Apache Gora :: Pig . SUCCESS [  3.781 s]
[INFO] Apache Gora :: Accumulo  SUCCESS [06:53 min]
[INFO] Apache Gora :: HBase ... SUCCESS [03:37 min]
[INFO] Apache Gora :: Cassandra - CQL . SUCCESS [01:29 min]
[INFO] Apache Gora :: GoraCI .. SUCCESS [  4.353 s]
[INFO] Apache Gora :: Infinispan .. SUCCESS [01:15 min]
[INFO] Apache Gora :: JCache .. SUCCESS [01:16 min]
[INFO] Apache Gora :: OrientDB  SUCCESS [01:53 min]
[INFO] Apache Gora :: Lucene .. SUCCESS [  9.434 s]
[INFO] Apache Gora :: Dynamodb  SUCCESS [  4.144 s]
[INFO] Apache Gora :: CouchDB . SUCCESS [  5.470 s]
[INFO] Apache Gora :: Maven Plugin  SUCCESS [  2.518 s]
[INFO] Apache Gora :: MongoDB . SUCCESS [02:10 min]
[INFO] Apache Gora :: Solr  SUCCESS [04:33 min]
[INFO] Apache Gora :: Aerospike ... SUCCESS [  3.020 s]
[INFO] Apache Gora :: Ignite .. SUCCESS [01:00 min]
[INFO] Apache Gora :: Tutorial  SUCCESS [  5.248 s]
[INFO] Apache Gora :: Sources-Dist  SUCCESS [  0.371 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  26:02 min
[INFO] Finished at: 2019-08-20T07:35:34-07:00
[INFO] 
{code}

> No content stored for an object field with name "value"
> ---
>
> Key: GORA-538
> URL: https://issues.apache.org/jira/browse/GORA-538
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-mongodb
>Reporter: Clément Garbay
>Assignee: John Mora
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> When I have a field called "value" in a Java object, no content is stored for 
> this field in MongoDB.
> I came accross this problem when I stored a raw object in a field declared 
> with type `list` in class using the Gora ORM.
> It seems that the problem appears with reserved Java keywords.



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

[jira] [Resolved] (GORA-538) No content stored for an object field with name "value"

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney resolved GORA-538.
---
  Assignee: John Mora
Resolution: Fixed

Thanks [~jhnmora000]

> No content stored for an object field with name "value"
> ---
>
> Key: GORA-538
> URL: https://issues.apache.org/jira/browse/GORA-538
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-mongodb
>Reporter: Clément Garbay
>Assignee: John Mora
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> When I have a field called "value" in a Java object, no content is stored for 
> this field in MongoDB.
> I came accross this problem when I stored a raw object in a field declared 
> with type `list` in class using the Gora ORM.
> It seems that the problem appears with reserved Java keywords.



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

[jira] [Updated] (GORA-538) No content stored for an object field with name "value"

[Lewis John McGibbney (Jira)]

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

Lewis John McGibbney updated GORA-538:
--
Fix Version/s: 1.0

> No content stored for an object field with name "value"
> ---
>
> Key: GORA-538
> URL: https://issues.apache.org/jira/browse/GORA-538
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-mongodb
>Reporter: Clément Garbay
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> When I have a field called "value" in a Java object, no content is stored for 
> this field in MongoDB.
> I came accross this problem when I stored a raw object in a field declared 
> with type `list` in class using the Gora ORM.
> It seems that the problem appears with reserved Java keywords.



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

[jira] [Commented] (GORA-464) Get gora-dynamodb back up and running and available as part of the examples

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-464:
---

Ongoing work can be seen at https://github.com/lewismc/gora/tree/GORA-464
Several compilation issues right now. I'll fix it all and get a PR ready. 

> Get gora-dynamodb back up and running and available as part of the examples
> ---
>
> Key: GORA-464
> URL: https://issues.apache.org/jira/browse/GORA-464
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-dynamodb
>Affects Versions: 0.6.1
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> We have had the DynamoDB module commented out for a wee while now and it 
> would be nice to get it brought bang up to date within the 1.0 development 
> cycle.
> [~renato2099] tagging you for context as I know this is your baby :)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Updated] (GORA-464) Get gora-dynamodb back up and running and available as part of the examples

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-464:
--
Description: 
We have had the DynamoDB module commented out for a wee while now and it would 
be nice to get it brought bang up to date within the 1.0 development cycle.
[~renato2099] tagging you for context as I know this is your baby :)

  was:
We have had the DynamoDB module commented out for a wee while now and it would 
be nice to get it brought bang up to date within the 0.8 development cycle.
[~renato2099] tagging you for context as I know this is your baby :)


> Get gora-dynamodb back up and running and available as part of the examples
> ---
>
> Key: GORA-464
> URL: https://issues.apache.org/jira/browse/GORA-464
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-dynamodb
>Affects Versions: 0.6.1
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> We have had the DynamoDB module commented out for a wee while now and it 
> would be nice to get it brought bang up to date within the 1.0 development 
> cycle.
> [~renato2099] tagging you for context as I know this is your baby :)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (GORA-464) Get gora-dynamodb back up and running and available as part of the examples

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-464:
---

Going to address this right now. I am working on upgrading dynamodb and getting 
rid of deprecation. 

> Get gora-dynamodb back up and running and available as part of the examples
> ---
>
> Key: GORA-464
> URL: https://issues.apache.org/jira/browse/GORA-464
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-dynamodb
>Affects Versions: 0.6.1
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> We have had the DynamoDB module commented out for a wee while now and it 
> would be nice to get it brought bang up to date within the 0.8 development 
> cycle.
> [~renato2099] tagging you for context as I know this is your baby :)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Assigned] (GORA-464) Get gora-dynamodb back up and running and available as part of the examples

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney reassigned GORA-464:
-

Assignee: Lewis John McGibbney

> Get gora-dynamodb back up and running and available as part of the examples
> ---
>
> Key: GORA-464
> URL: https://issues.apache.org/jira/browse/GORA-464
> Project: Apache Gora
>  Issue Type: Task
>  Components: gora-dynamodb
>Affects Versions: 0.6.1
>    Reporter: Lewis John McGibbney
>    Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.0
>
>
> We have had the DynamoDB module commented out for a wee while now and it 
> would be nice to get it brought bang up to date within the 0.8 development 
> cycle.
> [~renato2099] tagging you for context as I know this is your baby :)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (GORA-623) Javadoc build fails with Gora master branch

[Lewis John McGibbney (JIRA)]

Lewis John McGibbney created GORA-623:
-

 Summary: Javadoc build fails with Gora master branch
 Key: GORA-623
 URL: https://issues.apache.org/jira/browse/GORA-623
 Project: Apache Gora
  Issue Type: Improvement
  Components: documentation
Affects Versions: 0.9
 Environment: commit ID: 9b1d297fc11f90850d0360c93b3bd65486a20834
Reporter: Lewis John McGibbney
 Fix For: 1.0


We should really add a _*mvn javadoc:aggregate*_ command to our master branch 
build.

{code}
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:aggregate (default-cli) on 
project gora: An error has occurred in JavaDocs report generation:
[ERROR] Exit code: 1 - 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/store/DataStore.java:144:
 warning: no @throws for org.apache.gora.util.GoraException
[ERROR]   boolean exists(K key) throws GoraException;
[ERROR]   ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/Query.java:50:
 warning: no @throws for org.apache.gora.util.GoraException
[ERROR]   Result execute() throws GoraException;
[ERROR]^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:62:
 warning: no @throws for org.apache.gora.util.GoraException
[ERROR]   public BeanFactoryImpl(Class keyClass, Class persistentClass) 
throws GoraException {
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:82:
 warning: no description for @param
[ERROR]* @param keyClass
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/impl/BeanFactoryImpl.java:85:
 warning: no description for @throws
[ERROR]* @throws GoraException
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/Persistent.java:131:
 warning: no description for @throws
[ERROR]* @throws CloneNotSupportedException
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:74:
 warning: no @param for index
[ERROR]   public String getField(int index) {
[ERROR] ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/persistency/ws/impl/PersistentWSBase.java:82:
 warning: no @param for field
[ERROR]   public int getFieldIndex(String field) {
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:84:
 warning: no description for @return
[ERROR]* @return
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:262:
 warning: no description for @return
[ERROR]* @return
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:270:
 warning: no description for @param
[ERROR]* @param auth
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
 warning: no @param for baseQuery
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
endKey,
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
 warning: no @param for startKey
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
endKey,
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
 warning: no @param for endKey
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
endKey,
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:64:
 warning: no @param for locations
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, K startKey, K 
endKey,
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:57:
 warning: no @param for baseQuery
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, String... 
locations) {
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/PartitionWSQueryImpl.java:57:
 warning: no @param for locations
[ERROR]   public PartitionWSQueryImpl(Query baseQuery, String... 
locations) {
[ERROR]  ^
[ERROR] 
/Users/lmcgibbn/Downloads/gora/gora-core/src/main/java/org/apache/gora/query/ws/impl/QueryWSBase.java:80:
 warning: no description

Re: [VOTE] RC03 for Apache Gora 0.9 Release

[lewis john mcgibbney]

Hi Kevin

On Tue, Aug 13, 2019 at 10:01 AM Kevin Ratnasekera 
wrote:

>
> [ ] +1 Release this package as Apache Gora 0.9 …
>

[X] +1 Release this package as Apache Gora 0.9 …

PMB-binding VOTE

>
> 48 tickets were resolved and release report is available here :
>
> https://s.apache.org/0.9GoraReleaseNotes
>

Nice good job folks.


>
> Source release artifacts are available here :
>
> https://dist.apache.org/repos/dist/dev/gora/apache-gora-0.9-RC03/
>

gpg --verify apache-gora-0.9-src.tar.gz.asc
gpg: WARNING: unsafe permissions on homedir '/Users/lmcgibbn/.gnupg'
gpg: assuming signed data in 'apache-gora-0.9-src.tar.gz'
gpg: Signature made Tue Aug 13 08:16:40 2019 PDT
gpg:using RSA key 396DA771A3E66AC7
gpg: Good signature from "Kevin Ratnasekera (CODE SIGNING KEY) <
djkevi...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: A8E6 7C9C 51A3 1440 F90F  CA55 396D A771 A3E6 6AC7

cat apache-gora-0.9-src.tar.gz.sha512
2cf79bc9556015486014fed27b71192d09d92170cf44637c7ecce4f993aabaa1fc03a9279c80be81643c668ed84c14d5fae48c720a5a297e6854a9ecf209e42c
openssl sha512 -r apache-gora-0.9-src.tar.gz
2cf79bc9556015486014fed27b71192d09d92170cf44637c7ecce4f993aabaa1fc03a9279c80be81643c668ed84c14d5fae48c720a5a297e6854a9ecf209e42c
*apache-gora-0.9-src.tar.gz

All good!

Does it test?

[INFO] Reactor Summary for Apache Gora 0.9:
[INFO]
[INFO] Apache Gora  SUCCESS [
 1.831 s]
[INFO] Apache Gora :: Compiler  SUCCESS [
 1.927 s]
[INFO] Apache Gora :: Compiler-CLI  SUCCESS [
 0.828 s]
[INFO] Apache Gora :: Core  SUCCESS [01:11
min]
[INFO] Apache Gora :: Pig . SUCCESS [
 3.750 s]
[INFO] Apache Gora :: Accumulo  SUCCESS [06:54
min]
[INFO] Apache Gora :: HBase ... SUCCESS [03:35
min]
[INFO] Apache Gora :: Cassandra - CQL . SUCCESS [01:18
min]
[INFO] Apache Gora :: GoraCI .. SUCCESS [
 5.082 s]
[INFO] Apache Gora :: Infinispan .. SUCCESS [01:14
min]
[INFO] Apache Gora :: JCache .. SUCCESS [
58.616 s]
[INFO] Apache Gora :: OrientDB  SUCCESS [01:32
min]
[INFO] Apache Gora :: Lucene .. SUCCESS [
 8.747 s]
[INFO] Apache Gora :: Dynamodb  SUCCESS [
 4.185 s]
[INFO] Apache Gora :: CouchDB . SUCCESS [
 5.469 s]
[INFO] Apache Gora :: Maven Plugin  SUCCESS [
 2.621 s]
[INFO] Apache Gora :: MongoDB . SUCCESS [02:07
min]
[INFO] Apache Gora :: Solr  SUCCESS [09:38
min]
[INFO] Apache Gora :: Aerospike ... SUCCESS [
 4.101 s]
[INFO] Apache Gora :: Ignite .. SUCCESS [01:13
min]
[INFO] Apache Gora :: Tutorial  SUCCESS [
 6.905 s]
[INFO] Apache Gora :: Sources-Dist  SUCCESS [
 0.370 s]
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time:  30:33 min
[INFO] Finished at: 2019-08-14T18:49:38-07:00
[INFO]


Some of the modules take quite a while... I think it is because it is the
first time I've run them on my new laptop.


>
> Release candidate is signed through the key A3E66AC7 which is available
> here :
>
> https://dist.apache.org/repos/dist/dev/gora/KEYS
>

Yep good.

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Created] (GORA-622) maven-assemly-plugin complains that group id is too big and fails build on macOS Mojave 10.14.6 (18G87)

[Lewis John McGibbney (JIRA)]

Lewis John McGibbney created GORA-622:
-

 Summary: maven-assemly-plugin complains that group id is too big 
and fails build on macOS Mojave 10.14.6 (18G87)
 Key: GORA-622
 URL: https://issues.apache.org/jira/browse/GORA-622
 Project: Apache Gora
  Issue Type: Bug
  Components: build process
Affects Versions: 0.9
 Environment: macOS Mojave 10.14.6 (18G87)
Gora master branch d9b4b8eb73c84806971a7375fe35c038a0a10197
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
 Fix For: 0.9


Building Gora branch under system detailed in the environment, I experience 
very similar results to what is described at OPENNLP-998
Pull request coming up to upgrade the maven-assemly-plugin and then specify 
posix



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Week 11 Report

[lewis john mcgibbney]

An excellent week of work Sheriffo good job.
I’ll pull your code and run it locally. I’ll then update JIra with the
results.
Thanks

On Sun, Aug 11, 2019 at 15:01 Sheriffo Ceesay  wrote:

> All,
>
> Week 11 report of [1] is available at
> https://cwiki.apache.org/confluence/display/GORA/%5BGORA-532%5D+Apache+Gora+Benchmark+Module+Weekly+Report
>
> Basically, I have worked on the comments on the pull request [2]. It will
> be great if someone can run my code locally to see if there are any issues.
> You can use the README file in the project root directory.
>
> We have reported an issue and the maintainers of YCSB are working on it to
> get it resolved [3].
>
> [1] https://github.com/sneceesay77/gora/tree/GORA-532
> [2] https://github.com/apache/gora/pull/179
> [3] https://github.com/brianfrankcooper/YCSB/issues/1340
>
> Thank you.
>
> **Sheriffo Ceesay**
>
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: Week 1 Report and Some Questions

[lewis john mcgibbney]

Excellent.
Apologies for being absent. I am undergoing a job transition and it has
been very busy.
I suggest that we start a weekly tagup as well.
Lewis

On Sun, Jun 2, 2019 at 1:14 PM Sheriffo Ceesay 
wrote:

> The code so far is available at the GitHub link below.
>
> https://github.com/sneceesay77/gora/tree/GORA-532/gora-benchmark
>
>
>
> **Sheriffo Ceesay**
>
>
> On Sun, Jun 2, 2019 at 8:34 PM Sheriffo Ceesay 
> wrote:
>
>> Hi Renato,
>>
>> Thanks for the detailed reply. I agree with your recommendations on the
>> way forward. I will go ahead and implement the rest of the functionality
>> using reflection and we can follow your recommendations on the next
>> iterations.
>>
>> As for the backend, I am using both HBase and MongoDB and all seems well
>> at the moment.
>>
>> I will let you all know why I push my code to GitHub.
>>
>> Thank you.
>>
>>
>> **Sheriffo Ceesay**
>>
>>
>> On Sun, Jun 2, 2019 at 7:01 PM Renato Marroquín Mogrovejo <
>> renatoj.marroq...@gmail.com> wrote:
>>
>>> Hi Sheriffo,
>>>
>>> Some opinions about your questions, but others are more than welcome
>>> to suggest other things as well.
>>>
>>> Q1: Are we going to consider arbitrary field length, e.g. if we set
>>> the fieldcount to 100 then we have to create the respective Avro and
>>> mapping files? Currently,
>>> I don't think this process is automated and may be tedious for large
>>> field counts.
>>> I think for the first code iteration, we should use whatever
>>> fieldcount you have generated for. Ideally, we should be able to
>>> invoke the Gora bean generator and generate as many fields as required
>>> by the benchmark configuration.
>>>
>>> Q2: Second: The second problem has to do with the first one, if we
>>> allow arbitrary field counts, then there has to be a mechanism to call
>>> each of the set or get methods during CRUD operations. So to avoid
>>> this I used Java Reflection. See the sample code below.
>>> We have some options to deal with having arbitrarily number of fields.
>>> 1) Use reflection as you have which might be ok for the first code
>>> iteration, but if we want to have some decent performance against
>>> using datastores natively (no Gora), we should go away from it.
>>> 2) Do Gora class generation (and also generate the method used to
>>> insert data through Gora) in a step before the benchmark starts.
>>> Something like this:
>>> # passing config parameters to generate Gora Beans with number of
>>> required fields
>>> # this should output the generate class and the method that does the
>>> insertion
>>> $ gora_compiler.sh --benchmark --fields_required 4
>>> The output path containing the result of this should be then include
>>> (or passed) as runtime dependency to the benchmark class.
>>> 3) Because Gora uses Avro, we can use complex data types, e.g.,
>>> arrays, maps. So we could represent number of fields as number of
>>> elements inside an array. I would think that this option gives us the
>>> best performance.
>>> I think  we should continue with option (1) until we have the entire
>>> pipeline working, and we understand how every piece fits together with
>>> each other (YSCB, Gora, Gora compiler, benchmark setup steps). Then we
>>> should do (2) which is the most general and the one that reflects how
>>> people usually use Gora, and then we test with (3). I think all of
>>> these steps are totally doable in our time frame as we build upon
>>> previous steps.
>>> The other thing that we should decide is which backend to use as there
>>> are backends that are more mature than others. I'd say to use the
>>> HBase backend as it is the most stable one and the one with more
>>> features, and if we feel brave we can try other backends (and fix them
>>> if necessary!)
>>>
>>>
>>> Best,
>>>
>>> Renato M>
>>>
>>> El dom., 2 jun. 2019 a las 19:10, Sheriffo Ceesay
>>> () escribió:
>>> >
>>> > Dear Mentors,
>>> >
>>> > My week one report is available at
>>> >
>>> https://cwiki.apache.org/confluence/display/GORA/%5BGORA-532%5D+Apache+Gora+Benchmark+Module+Weekly+Report
>>> >
>>> > I have also included a detailed question of and I will need your
>>> guidance
>>> > on that.
>>> >
>>> > Please let me know what your thoughts are.
>>> >
>>> > Thank you.
>>> >
>>> > **Sheriffo Ceesay**
>>>
>>

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Commented] (GORA-405) Create Gora REST API

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-405:
---

[~vyomkesh] I'm not sure who tagged this as GSoC2019 it was not me. I would 
encourage you to ask over on the Gora dev@ mailing list. First you need to 
attract a mentor. I am not able to mentor this. 

> Create Gora REST API
> 
>
> Key: GORA-405
> URL: https://issues.apache.org/jira/browse/GORA-405
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-compiler, gora-core
>Reporter: Udesh Liyanaarachchi
>Assignee: Udesh Liyanaarachchi
>Priority: Minor
>  Labels: gsoc2019
> Fix For: 0.9
>
>
> As to the discussion [~lewismc]  initiated in the 
> [mail list 
> thread|https://www.mail-archive.com/dev@gora.apache.org/msg05444.html] we 
> need to implement a REST API for GORA.
> This is the initial proposal documentation for the [GORA REST 
> API|http://docs.apachegoraapi.apiary.io/].
> The plan will be to implement the API with  [Apache CXF 
> |http://cxf.apache.org] using [CXF's JAXRS 
> |http://cxf.apache.org/docs/jax-rs.html] implementation.



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

[jira] [Created] (GORA-610) Upgrade Apache Avro from 1.8.1-->1.8.2

[Lewis John McGibbney (JIRA)]

Lewis John McGibbney created GORA-610:
-

 Summary: Upgrade Apache Avro from 1.8.1-->1.8.2
 Key: GORA-610
 URL: https://issues.apache.org/jira/browse/GORA-610
 Project: Apache Gora
  Issue Type: Task
  Components: avro
Affects Versions: 0.8
Reporter: Lewis John McGibbney
 Fix For: 0.9


A newer version of Avro was released some time ago, Gora should upgrade
https://search.maven.org/artifact/org.apache.avro/avro/1.8.2/bundle



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

GSoC 2019 mentor requests for Lewis John McGibbney (lewismc) and Renato Javier Marroquín Mogrovejo (rmarroquin)

[lewis john mcgibbney]

Gora PMC,

Please acknowledged Renato and my own joint request to become a mentor for
GSoC project - Benchmark Module
https://issues.apache.org/jira/browse/GORA-532

We are going to jointly mentor this project having already reviewed the
students proposal which is in excellent shape.

Mentor invitations should go to rmarroquin and lewismc @apache.org
respectively.

Thank you
Lewis

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Commented] (GORA-532) Benchmarking Module

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-532:
---

Hi [~Sheriffo] both Renato and I have looked over the proposal and I am very 
happy to support it.
I would like you ton consider however how we go about obtaining compute 
resources to test this. As you know, the fundamental principle of Gora is that 
lots of operations can run at scale. How are we going to simulate this?
I would also like you to consider subscribing to notifications for ApacheCon EU 
2019 - https://www.apachecon.com/aceu19/index.html. It is always preferable to 
demo the GSoC work at an event nearer to you.
BTW, a fun fact here is that I obtained my Ph.D. from Glasgow Caledonian 
University and i am Scottish. Been to St. Andrews many many times over the 
years... reading that in your proposal made me a tad homesick :(
Anyways, this looks promising. Let's see if it is accepted or not.

> Benchmarking Module
> ---
>
> Key: GORA-532
> URL: https://issues.apache.org/jira/browse/GORA-532
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Major
>  Labels: gsoc2018, gsoc2019
> Fix For: 0.9
>
>
> We should make a benchmark and publish it, and improved version of the 
> Yahoo!’s Cloud Serving Benchmark (YCSB++) [1] is the most suitable tool for 
> such a purpose. Here is a recent research about Object-NoSQL Database Mapper 
> (ONDM) benchmark [2] which includes Apache Gora and they have produced the 
> benchmark source code as ASF 2.0 licensed [3].
>  
> Also, here is an example from Apache Accumulo which is based on YCSB [4].
>  
> [1] [http://www.cs.cmu.edu/~wtantisi/files/tablebenchmark-pdl11-talk.pdf]
> [2] [https://doi.org/10.1186/s13174-016-0052-x]
> [3] [https://github.com/vreniers/ONDM-Benchmarker]
> [4] [https://accumulo.apache.org/papers/accumulo-benchmarking-2.1.pdf]



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

[jira] [Commented] (GORA-532) Benchmarking Module

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-532:
---

Hi [~Sheriffo] both [~renato2099] and I would like to mentor this project. I've 
requested access to the document so please grant it to me (lewis dot mcgibbney 
at gmail dot com). Thank you

> Benchmarking Module
> ---
>
> Key: GORA-532
> URL: https://issues.apache.org/jira/browse/GORA-532
> Project: Apache Gora
>  Issue Type: New Feature
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Major
>  Labels: gsoc2018, gsoc2019
> Fix For: 0.9
>
>
> We should make a benchmark and publish it, and improved version of the 
> Yahoo!’s Cloud Serving Benchmark (YCSB++) [1] is the most suitable tool for 
> such a purpose. Here is a recent research about Object-NoSQL Database Mapper 
> (ONDM) benchmark [2] which includes Apache Gora and they have produced the 
> benchmark source code as ASF 2.0 licensed [3].
>  
> Also, here is an example from Apache Accumulo which is based on YCSB [4].
>  
> [1] [http://www.cs.cmu.edu/~wtantisi/files/tablebenchmark-pdl11-talk.pdf]
> [2] [https://doi.org/10.1186/s13174-016-0052-x]
> [3] [https://github.com/vreniers/ONDM-Benchmarker]
> [4] [https://accumulo.apache.org/papers/accumulo-benchmarking-2.1.pdf]



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

[jira] [Resolved] (GORA-208) Implement consistent use of DataStoreFactory across Gora modules

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney resolved GORA-208.
---
Resolution: Not A Problem

> Implement consistent use of DataStoreFactory across Gora modules
> 
>
> Key: GORA-208
> URL: https://issues.apache.org/jira/browse/GORA-208
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-accumulo, gora-cassandra, gora-core, gora-dynamodb, 
> gora-hbase
>Affects Versions: 0.2.1
>    Reporter: Lewis John McGibbney
>Priority: Major
> Fix For: 0.9
>
>
> Currently usage of DataStoreFactory (for initializing datastores, mappings 
> and datastore configuration properties) is in consistent across datastore 
> modules. If we are to lower the barrier to datastore contributions and 
> implementations then we need to make the approach consistent.
> This should also be documented thoroughly as it is a key part of the Gora 
> architecture.



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

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

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-411:
---

[~jhnmora000] LGTM
When you get to the actual implementations, I would advise that you have some 
sort of temporal benchmark to gauge efficiency of the method.
+1

> 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] [Resolved] (GORA-225) Various Issues with MemStore

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney resolved GORA-225.
---
Resolution: Fixed

Thanks [~djkevincr]

> Various Issues with MemStore 
> -
>
> Key: GORA-225
> URL: https://issues.apache.org/jira/browse/GORA-225
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-core, testing
>Affects Versions: 0.3
> Environment: Nutch 2.x HEAD, gora-core 0.3
>    Reporter: Lewis John McGibbney
>Priority: Major
>  Labels: gsoc2015
> Fix For: 0.9
>
>
> In Nutch we have numerous testing scenarios which simulate persistence of 
> data to Gora in some form or other. It has worked good as until now.
> Now that gora-sql-0.1.1-incubating artifact is non-compatible with gora-core 
> 0.3, there is a requirement to address this situation in order to keep some 
> degree of integrity within the Nutch codebase.
> Specifcally a number of tests [0][1][2][3] all extend a Util testing class 
> which utilizes functionality from the gora-sql artifact.
> My initial solution was to switch to using MemStore... which brought me to 
> logging this issue!
> I've logged sub issues here to make clear distinction about my observations.



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

Re: GSOC 2019 discussion

[lewis john mcgibbney]

Hi Bharath,
Thanks for your interest in the project. Please kick off discussion on the
dev@gora mailing list.
Thanks

On Mon, Mar 11, 2019 at 12:06 Bharath Joginapally 
wrote:

> Hi guys
>  I have gone through the gsoc project ideas and am interested in GORA
> 527 (Implement
> a data store for redis) .  Can i know the IRC channel where i can start the
> discussion on this.
>
> Thank You
> Bharath J
>
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: Suggestion for new Direction for Gora

[lewis john mcgibbney]

Hi Kevin,
Responses inline

On Tue, Dec 4, 2018 at 5:56 PM  wrote:

> From: Kevin Ratnasekera 
> To: Gora Dev 
> Cc:
> Bcc:
> Date: Wed, 5 Dec 2018 02:35:14 +0530
> Subject: Re: Suggestion for new Direction for Gora
> Hi Lewis,
>
> Thank you for all the suggestions given. I went through the pointers you
> given and found out that,
>
> 1. Camel is at gora 0.8 ( Already upgraded to latest )
>

cool


> 2. Giraph is at gora 0.5 ( Upgrade needed )
>

Yes and this upgrade will be pretty trivial.


> 3. Chukwa is at gora 0.6 ( Upgrade needed )
>

Yes and this upgrade will be pretty trivial.


>
> I logged two jira tickets [1] which I will be taking over. ( If anyone like
> to join please talk to me  )


Nice.


> I am not sure about nutch gora integration,
> current status and whether we can do anything from our end. I have seen
> several times dev@gora people raised their concerns over improvements to
> nutch-gora Eg:- Last time when we had discussion on GSoC ideas, there was a
> proposal from Renato on fixing gora-nutch integration in Nutch 2.x possible
> cases where we have neglected as community. [3]


We are proposing to retire Nutch 2.x due to long periods of inactivity...
which is a shame but it is also fragmenting the Nutch community so I think
it is probably best fr the project at this stage. If you are interested in
maintaining then please let us know on dev@nutch. Our plans are to release
once more then retire it.


> Also recently I noticed
> some people requesting mavenized build for 2.x branch as well. [4] Do we
> have ideas to take things forward?
>

I don't think at this stage that it is worth it. We are going to finish off
the Maven build for 1.x instead and focus on that branch for development
moving forward.

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

[lewis john mcgibbney]

dev@,
As per Daniel Gruno's NOTICE [0], all https://git-wip-us.apache.org
repositories will be moved to the new gitbox service which includes direct
write access on github as well as the standard ASF commit access via
gitbox.apache.org.
We can do this voluntarily or we can be forced to do it (which basically
means we are being forced to do it but the former option at least enables
us to have some input into how it is done.)
This thread is a VOTE for us to move the canonical Gora source code over to
gitbox.apache.org. There will be no severe impact to our users or dev@
community. I anticipate the only impact to be the requirement to change the
remote canonical origin mapping in your Git client. Everything else should
be fine.
Some benefits include the ability for us to use the normal Github workflow
for merging, etc. so infact it will probably streamline some aspects of our
development workflow.
Please VOTE as follows

[ ] +1 Move the canonical Gora source code from
https://git-wip-us.apache.org to gitbox.apache.org.
[ ] +1 DO NOT move the canonical Gora source code from
https://git-wip-us.apache.org to gitbox.apache.org (please provide
justification)

This VOTE will be open a minimum of 72 hours.
Here is my +1
Lewis


[0] https://s.apache.org/aGMR
-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Fwd: dev Digest 7 Dec 2018 16:52:41 -0000 Issue 543

[lewis john mcgibbney]

FYI folks. We should probably log a ticket with JIRA and get this sorted
out.

-- Forwarded message -
From: 
Date: Fri, Dec 7, 2018 at 8:54 AM
Subject: dev Digest 7 Dec 2018 16:52:41 - Issue 543
To: 



dev Digest 7 Dec 2018 16:52:41 - Issue 543

Topics (messages 4637 through 4637)

[NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
4637 by: Daniel Gruno

Administrivia:

-
To post to the list, e-mail: d...@streams.apache.org
To unsubscribe, e-mail: dev-digest-unsubscr...@streams.apache.org
For additional commands, e-mail: dev-digest-h...@streams.apache.org

--




-- Forwarded message --
From: Daniel Gruno 
To: "us...@infra.apache.org" 
Cc:
Bcc:
Date: Fri, 7 Dec 2018 17:52:36 +0100
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

Hello Apache projects,

I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
months. All repositories will be moved to the new gitbox service which
includes direct write access on github as well as the standard ASF
commit access via gitbox.apache.org.

## Why this move? ##
The move comes as a result of retiring the git-wip service, as the
hardware it runs on is longing for retirement. In lieu of this, we
have decided to consolidate the two services (git-wip and gitbox), to
ease the management of our repository systems and future-proof the
underlying hardware. The move is fully automated, and ideally, nothing
will change in your workflow other than added features and access to
GitHub.

## Timeframe for relocation ##
Initially, we are asking that projects voluntarily request to move
their repositories to gitbox, hence this email. The voluntary
timeframe is between now and January 9th 2019, during which projects
are free to either move over to gitbox or stay put on git-wip. After
this phase, we will be requiring the remaining projects to move within
one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos
   over to gitbox (as stated, this is highly automated and will take
   between a minute and an hour, depending on the size and number of
   your repositories)

To sum up the preliminary timeline;

- December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
   relocation
- January 9th -> February 6th: Mandated (coordinated) relocation
- February 7th: All remaining repositories are mass migrated.

This timeline may change to accommodate various scenarios.

## Using GitHub with ASF repositories ##
When your project has moved, you are free to use either the ASF
repository system (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


We appreciate your understanding of this issue, and hope that your
project can coordinate voluntarily moving your repositories in a
timely manner.

All settings, such as commit mail targets, issue linking, PR
notification schemes etc will automatically be migrated to gitbox as
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to us...@infra.apache.org, not your
project's dev list :-).





-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Suggestion for new Direction for Gora

[lewis john mcgibbney]

Hi Folks,
As our RESOLUTION is now agreed upon within the community and submitted to
the Board for approval. I wanted to drop a few ideas which will hopefully
kickstart some new project activity and usage.
We've been building a rich suite of modules which not only enable flexible
object-to-datastore mapping solutions but also data analysis (Hadoop,
Spark, Flink) and data warehouse query execution (Pig).
I wanted however for us to consider where Gora could be used around the
rich spectrum of projects at the ASF.
So far we've built Gora into Nutch 2.X branch (which will soon be retired),
Camel (which needs updated), Giraph (which needs updated) and Chukwa (which
needs updated).
The above is a pretty nice roster of Apache projects which consume Gora but
I think we should engage those communities again and update everywhere we
can.
It would also be my intention for this thread to act as a bulletin board
for ideas of where Gora could be embedded in other projects.
I'll leave it there for now.
Lewis

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: HackIllinois 2019 + lewismc

[lewis john mcgibbney]

By all means Kenneth, please forward to whoever you think would be a good
mentor.
Thanks

On Thu, Nov 15, 2018 at 9:21 PM  wrote:

>
> From: kenneth mcfarland 
> To: dev@gora.apache.org
> Cc:
> Bcc:
> Date: Thu, 15 Nov 2018 15:43:55 -0800
> Subject: Re: HackIllinois 2019 + lewismc
> Hi Dr. Mccgibney,
>
> Would it help if I post this on another Apache project mail list or is this
> Gora specific?
>
> Thank you!
> Kenny
>
>

Fwd: HackIllinois 2019 + lewismc

[lewis john mcgibbney]

Hi Folks,
See below... is anyone interested in working/mentoring a project-related
project here?
Thanks
Lewis

-- Forwarded message -
From: Misha Patel 
Date: Wed, Nov 14, 2018 at 9:09 AM
Subject: HackIllinois 2019 + lewismc
To: 
Cc: 


Hi Lewis,

My name is Misha Patel and I am a member of the outreach team for
*HackIllinois*, a 36 hour open source hackathon held at the *University of
Illinois at Urbana-Champaign* from *February 22-24th, 2019*. Last year,
hundreds of students contributed to projects like GulpJS, Conda, and Apache
Mesos. This year, we aim to continue our focus on *open source software.*

Our goal is to have students leave our hackathon with knowledge of how to
create, contribute to, and understand open source software. One of the most
important ways of achieving this goal is through mentor-student
relationships that can help them build the skills required to give back to
the open source community. Guidance from talented developers and
contributors like yourself are what makes this possible.

As a contributor to Apache, we believe you have a very active role in this
community. *We would love for you to be a mentor at this year’s hackathon.*
As a mentor, you would work with a group of students throughout the weekend
to help them contribute to an existing project or create a new one. We
encourage you to *bring your own*, whether it's Apache or any other project
you've worked on, so you can simultaneously help students dive into open
source and get some extra hands working on it!

Please visit blog.hackillinois.org and hackillinois.org/mentor to learn
more about the event and the role you would play. I would be glad to set up
a phone call with you sometime this week if you are interested in learning
more or have any questions about how you can get involved. We look forward
to working with you!

Best,
Misha Patel
HackIllinois 2019 Outreach Team
misha.pa...@hackillinois.org | 6316091696


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[REPORT] Apache Gora

[lewis john mcgibbney]

Attachment V: Report from the Apache Gora Project  [Lewis John McGibbney]


## Description:
The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key
value stores, document stores, distributed in-memory key/value stores,
in-memory data grids, in-memory caches, distributed multi-model stores,
and hybrid in-memory architectures.
Gora also enables analysis of data with extensive Apache Hadoop MapReduce
and Apache Spark support.

## Issues:
As of 2018-11-15 the PMC is currrently VOTE'ing on a change of Project
Chair for the
Apache Gora project. The VOTE will be closed and a RESOLUTION will be passed
to the board for consideration by the time the November 2018 board meeting
takes place.

## Activity:
Activity has been reasonably post summer, the Gora project did recently
however welcome
a new Committer and PMC member Carlos Muñoz was added as a committer on Mon
Nov 12 2018.

## Health report:
The Gora project is in good health. Mailing lists are responsive with
VOTE'ing initiatives
seeing good response from the community. The project will most likely look
towards a new
release once the PMC Chair position has been transferred.

## PMC changes:

 - Currently 26 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Cihad Guzel on Tue Mar 13 2018

## Committer base changes:

 - Currently 27 committers.
 - Carlos Muñoz was added as a committer on Mon Nov 12 2018

## Releases:

 - Last release was 0.8 on Mon Sep 18 2017

## Mailing list activity:

Mailing lists number remain allmost flatlined with a very slight decrease
on dev@, our primary
communication medium. Hopefully with the transition of PMC duties we can
inject some renewed
energy into the project and see incresed initiatives.

 - dev@gora.apache.org:
- 72 subscribers (down -1 in the last 3 months):
- 145 emails sent to list (138 in previous quarter)

 - u...@gora.apache.org:
- 75 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (5 in previous quarter)


## JIRA activity:

 - 6 JIRA tickets created in the last 3 months
 - 2 JIRA tickets closed/resolved in the last 3 months

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

[jira] [Updated] (GORA-543) Upgrade Apache parent POM to version 21

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-543:
--
Component/s: build process

> Upgrade Apache parent POM to version 21
> ---
>
> Key: GORA-543
> URL: https://issues.apache.org/jira/browse/GORA-543
> Project: Apache Gora
>  Issue Type: Task
>  Components: build process
>Reporter: Ted Yu
>Priority: Major
> Fix For: 0.9
>
>
> Apache parent POM 21 has just been released. It generates .sha512 checksums 
> during release with Maven Release Plugin.



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

[jira] [Updated] (GORA-543) Upgrade Apache parent POM to version 21

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-543:
--
Fix Version/s: 0.9

> Upgrade Apache parent POM to version 21
> ---
>
> Key: GORA-543
> URL: https://issues.apache.org/jira/browse/GORA-543
> Project: Apache Gora
>  Issue Type: Task
>  Components: build process
>Reporter: Ted Yu
>Priority: Major
> Fix For: 0.9
>
>
> Apache parent POM 21 has just been released. It generates .sha512 checksums 
> during release with Maven Release Plugin.



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

[jira] [Commented] (GORA-543) Upgrade Apache parent POM to version 21

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney commented on GORA-543:
---

Cool thanks Ted.

> Upgrade Apache parent POM to version 21
> ---
>
> Key: GORA-543
> URL: https://issues.apache.org/jira/browse/GORA-543
> Project: Apache Gora
>  Issue Type: Task
>Reporter: Ted Yu
>Priority: Major
>
> Apache parent POM 21 has just been released. It generates .sha512 checksums 
> during release with Maven Release Plugin.



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

Uneven HBase region sizes WAS Re: Nodemanager crashing repeatedly

[lewis john mcgibbney]

Hi Gajanan,
CC dev@gora, this is something we may wish to implement within HBase.
If anything I've provided below is incorrect, then please correct the
record.
BTW, I found the following article written by Elis, to be extremely useful
https://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/

On Wed, Sep 19, 2018 at 3:55 AM  wrote:

> From: Gajanan Watkar 
> To: u...@nutch.apache.org
> Cc:
> Bcc:
> Date: Wed, 19 Sep 2018 16:24:52 +0530
> Subject: Re: Nodemanager crashing repeatedly
> Hi Lewis,
> It appears that my setup was infected. After studying ResourceManager logs
> closely I found that lot of jobs were getting submitted to my cluster as
> user "dr who". Moreover my crontab was listing 2 wget cron jobs I never
> configured (Suspect it to be cryptocurrency miner) and one java app running
> from /var/tmp/java. I Configured firewall, blocked port 8088, purged cron
> (as it was coming back with every re-install) and removed java app from
> /var/tmp/java. It seem to have stabilized my setup. For now it is working
> fine. No more unexpected NodeManager Exits. Also applied patch for
> MalformedURLException.
>

Good to hear that you were able to debug this. From the description you
provided I wondered if it was anything to do with Nutch 2.x namely because
I've never experienced anything like this in the past.


>
> I am getting uneven region sizes, can you suggest me on pre-spliting
> webpage table i.e. split points to be used and splitting policy and optimum
> GC setup for regionserver for efficient Nutch crawling.
>
>
Can you provide the version of HBase you are using? Assuming that you are
using Nutch 2.x branch from Git, you should be using 1.2.6.
Can you also provide the logging from HBase which indicates uneven region
sizes?

>From what I understand (and I am no HBase expert) when Gora first creates
the HBase table, by default, only one region is allocated for the table.
This means that initially, all requests will go to a single region server,
regardless of the number of region servers in your HBase deployment. A
knock on effect of this is that initial phases of loading data into the
empty Webpage table cannot utilize the whole capacity of the Base cluster
however I don't think this is by any means your issue.

The issue at hand is concerned with supplying the split points at the table
creation time which would hopefully resolve the uneven region size. The
comment I made above regarding Gora creating only one region allocation for
the table is correct, take a look at [0], you will see that we do not use
additional parameters for the call to Admin.createTable which would
explicitly specify for example the split points. Examples of additional
parameters which could be used when creating our Table are below, these can
also be seen at [1].

void createTable(HTableDescriptor desc)
Creates a new table.

void createTable(HTableDescriptor desc, byte[][] splitKeys)
Creates a new table with an initial set of empty regions defined by the
specified split keys.

void createTable(HTableDescriptor desc, byte[] startKey, byte[] endKey, int
numRegions)
Creates a new table with the specified number of regions.

void createTableAsync(HTableDescriptor desc, byte[][] splitKeys)
Creates a new table but does not block and wait for it to come online.

One other issue you asked was regarding the split policy... again, we do
not currently specify an explicit split policy, instead we utilize the auto
splitting capability (which I believe is ConstantSizeRegionSplitPolicy)
made available by HBase, however, if we wanted to implement an explicit
split policy, we could do so by implementing the code below at the
following line [2] within Gora's HBaseStore#createSchema method.

HTableDescriptor tableDesc = new HTableDescriptor("example-table");
tableDesc.setValue(HTableDescriptor.SPLIT_POLICY,
AwesomeSplitPolicy.class.getName()); //add columns etc
admin.createTable(tableDesc);

OR, we could make this configurable by providing the
'hbase.regionserver.region.split.policy' available within gora.properties.
There are a few ways we could prototype this.

Finally, regarding GC, I am not entirely sure right now. I don't know too
much about HBase optimization but just like any distributed system you
could tinker with GC values until you land at something which works. The
above however hopefully gets you started in the right direction.

hth
Lewis

[0]
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L182
[1]
https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/client/Admin.html
[2]
https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L180

[REPORT] Apache Gora

[lewis john mcgibbney]

## Description:
The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key
value stores, document stores, distributed in-memory key/value stores,
in-memory data grids, in-memory caches, distributed multi-model stores,
and hybrid in-memory architectures.
Gora also enables analysis of data with extensive Apache Hadoop MapReduce
and Apache Spark support.

## Issues:
There are no issues requiring board attention at this time.

## Activity:
Due to two ongoing GSoC projects, activity has been refreshingly active.
Additionally, recently, a Pig module was sent via a PR. This is under
review.

## Health report:
The Gora project is in a healthy state with review-then-commit
practice being demonstrated time and time again. The PMC is
engaging in community grown initiatives e.g. GSoC and we will
look to open up the PMC books post-successful conclusion of the
current projects.

## PMC changes:

 - Currently 26 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Cihad Guzel on Tue Mar 13 2018

## Committer base changes:

 - Currently 26 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Cihad Guzel at Wed Mar 14 2018

## Releases:

 - Last release was 0.8 on Mon Sep 18 2017

## Mailing list activity:

As always, most of our communication happens on dev@, nothing new here.

 - dev@gora.apache.org:
- 73 subscribers (down -2 in the last 3 months):
- 138 emails sent to list (194 in previous quarter)

 - u...@gora.apache.org:
- 75 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (17 in previous quarter)


## JIRA activity:

 - 1 JIRA tickets created in the last 3 months
 - 2 JIRA tickets closed/resolved in the last 3 months

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: dev Digest 12 Jul 2018 04:37:20 -0000 Issue 1059

[lewis john mcgibbney]

Thanks Talat. Are you logging reports anywhere on the wiki?
Thanks

On Wed, Jul 11, 2018 at 9:37 PM,  wrote:

>
> dev Digest 12 Jul 2018 04:37:20 - Issue 1059
>
> Topics (messages 10652 through 10652)
>
> [GSoC 2018] Redis Store Update
> 10652 by: Talat Uyarer
>
> Administrivia:
>
> -
> To post to the list, e-mail: dev@gora.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscr...@gora.apache.org
> For additional commands, e-mail: dev-digest-h...@gora.apache.org
>
> --
>
>
>
> -- Forwarded message --
> From: Talat Uyarer 
> To: dev 
> Cc:
> Bcc:
> Date: Tue, 10 Jul 2018 12:50:20 -0700
> Subject: [GSoC 2018] Redis Store Update
> Hi All,
>
> As you know I am working on Redis store for GSoC.
>
> So far I implemented basic operations( get and put) for simple type
> objetcs. I am going to implement delete and put and get for Nested Objects.
> Whenever I finish delete implementation. I will create a pr.
>
> I am little behind of my plan I believe I will close that gap for next
> term.
>
> Thanks
> --
> Talat UYARER
> Websitesi: http://talat.uyarer.com
> Twitter: http://twitter.com/talatuyarer
> Linkedin: http://tr.linkedin.com/pub/talat-uyarer/10/142/304
>
>


-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [GSoC 2018] Ignite backend - Status

[Lewis John Mcgibbney]

Hi Carlos, I’ll reciew by end of weekend this is an excellent effort thank
you.
Lewis

On Sat, Jul 7, 2018 at 07:30 carlos muñoz  wrote:

> Hi.
>
> Just a quick update of the project.
>
> I just have sent a PR [1] with the initial Ignite Backend implementation.
> All the tests are passing, but I would like to check the code in other to
> improve it and catch possible errors. So I would highly appreciacte if you
> review it.
> Also, I would like to work on some documentation of the new backend. Where
> does the Gora's website code live? and how can I edit it?.
>
> Best,
> Carlos
>
> [1] https://github.com/apache/gora/pull/134
>
-- 

*Lewis*
Dr. Lewis J. McGibbney Ph.D, B.Sc
*Skype*: lewis.john.mcgibbney