[jira] [Commented] (GORA-443) Upgrade HBase to 1.2.3

[Lewis John McGibbney (JIRA)]

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

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

Right now is a good time to maybe fix 
https://issues.apache.org/jira/browse/GORA-472

> Upgrade HBase to 1.2.3
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Ted Yu
>Assignee: Lewis John McGibbney
> Fix For: 0.7
>
>
> HBase 1.1.2 release is the current stable release.
> Gora should be built based on HBase 1.1.2
> Currently I got the following compilation error:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project gora-hbase: Compilation failure
> [ERROR] 
> /home/hbase/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java:[59,7]
>  error: HBaseTableConnection is not abstract and does not override abstract 
> method checkAndDelete(byte[],byte[],byte[],CompareOp,byte[],Delete) in Table
> {code}



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

[jira] [Updated] (GORA-497) Migrate CassandraThrift to CQL

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-497:
--
Labels: gsoc2017  (was: )

> Migrate CassandraThrift to CQL 
> ---
>
> Key: GORA-497
> URL: https://issues.apache.org/jira/browse/GORA-497
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-cassandra
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
>  Labels: gsoc2017
> Fix For: 0.8
>
>




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

gora-trunk - Build # 1697 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built gora-trunk (build #1697)

Status: Still Failing

Check console output at https://builds.apache.org/job/gora-trunk/1697/ to view 
the results.

[jira] [Commented] (GORA-443) Upgrade HBase to 1.2.3

[Hudson (JIRA)]

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

Hudson commented on GORA-443:
-

FAILURE: Integrated in Jenkins build gora-trunk #1697 (See 
[https://builds.apache.org/job/gora-trunk/1697/])
GORA-443 (marenato: rev 01856b565be8b6e890130dedc3bed89f63c96daa)
* (edit) gora-core/src/test/java/org/apache/gora/store/DataStoreTestUtil.java
* (edit) 
gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java
* (edit) gora-hbase/src/test/conf/hbase-site.xml
* (edit) 
gora-hbase/src/test/java/org/apache/gora/hbase/store/TestHBaseStore.java
* (edit) gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java
GORA-443 (marenato: rev 163d91bc284e5b5a53b9d314e9fd317964cef486)
* (edit) pom.xml
Updates to GORA-443 issue (lewis.mcgibbney: rev 
f5503ef369f2193f6395e72cc1875a94c04b33a3)
* (edit) gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java
* (edit) 
gora-hbase/src/test/java/org/apache/gora/hbase/store/TestHBaseStore.java
* (edit) pom.xml
* (edit) gora-couchdb/pom.xml
* (edit) 
gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java
* (edit) README.md


> Upgrade HBase to 1.2.3
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Ted Yu
>Assignee: Lewis John McGibbney
> Fix For: 0.7
>
>
> HBase 1.1.2 release is the current stable release.
> Gora should be built based on HBase 1.1.2
> Currently I got the following compilation error:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project gora-hbase: Compilation failure
> [ERROR] 
> /home/hbase/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java:[59,7]
>  error: HBaseTableConnection is not abstract and does not override abstract 
> method checkAndDelete(byte[],byte[],byte[],CompareOp,byte[],Delete) in Table
> {code}



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

[jira] [Commented] (GORA-497) Migrate CassandraThrift to CQL

[Madhawa Gunasekara (JIRA)]

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

Madhawa Gunasekara commented on GORA-497:
-

Yes, sure. I'm a student of Institute of Engineers, Sri Lanka. so I can take 
this project on through GSOC.

> Migrate CassandraThrift to CQL 
> ---
>
> Key: GORA-497
> URL: https://issues.apache.org/jira/browse/GORA-497
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-cassandra
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.8
>
>




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

gora-trunk - Build # 1696 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built gora-trunk (build #1696)

Status: Failure

Check console output at https://builds.apache.org/job/gora-trunk/1696/ to view 
the results.

[jira] [Commented] (GORA-498) Adding MongoDB Authentications

[Hudson (JIRA)]

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

Hudson commented on GORA-498:
-

FAILURE: Integrated in Jenkins build gora-trunk #1696 (See 
[https://builds.apache.org/job/gora-trunk/1696/])
GORA-498 Adding mongodb authentications (madhawa30: rev 
5846373ed25d32a37053853ae16265b7e560eeb1)
* (edit) 
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStore.java
* (edit) 
gora-mongodb/src/main/java/org/apache/gora/mongodb/store/MongoStoreParameters.java


> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[jira] [Commented] (GORA-497) Migrate CassandraThrift to CQL

[Lewis John McGibbney (JIRA)]

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

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

[~madhawa] are you in a position to take this project on through GSoC? This is 
just a thought. Are you a student?

> Migrate CassandraThrift to CQL 
> ---
>
> Key: GORA-497
> URL: https://issues.apache.org/jira/browse/GORA-497
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-cassandra
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.8
>
>




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

[jira] [Commented] (GORA-443) Upgrade HBase to 1.2.3

[Lewis John McGibbney (JIRA)]

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

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

Hi [~tedyu] and [~renato2099] I've taken the liberty of merging what I had for 
the GORA-443 branch into master and pushed to remote canonical master. This 
will make the CI build unstable as tests will fail however it will drive on 
with addressing this issue as it will bring a sense or urgency.
I'll take a look into addressing the unstable tests. 
[~tedyu] it would be appreciated if you could also review the failing tests and 
provide me with guidance as to what might be wrong. I think [~renato2099] 
already has a reasonable idea so we will work to resolve the issue.

> Upgrade HBase to 1.2.3
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Ted Yu
>Assignee: Lewis John McGibbney
> Fix For: 0.7
>
>
> HBase 1.1.2 release is the current stable release.
> Gora should be built based on HBase 1.1.2
> Currently I got the following compilation error:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project gora-hbase: Compilation failure
> [ERROR] 
> /home/hbase/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java:[59,7]
>  error: HBaseTableConnection is not abstract and does not override abstract 
> method checkAndDelete(byte[],byte[],byte[],CompareOp,byte[],Delete) in Table
> {code}



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

[jira] [Commented] (GORA-443) Upgrade HBase to 1.2.3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GORA-443:
-

Github user asfgit closed the pull request at:

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


> Upgrade HBase to 1.2.3
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-hbase
>Reporter: Ted Yu
>Assignee: Lewis John McGibbney
> Fix For: 0.7
>
>
> HBase 1.1.2 release is the current stable release.
> Gora should be built based on HBase 1.1.2
> Currently I got the following compilation error:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project gora-hbase: Compilation failure
> [ERROR] 
> /home/hbase/gora/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java:[59,7]
>  error: HBaseTableConnection is not abstract and does not override abstract 
> method checkAndDelete(byte[],byte[],byte[],CompareOp,byte[],Delete) in Table
> {code}



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

[GitHub] gora pull request #86: GORA-443 Upgrade HBase to 1.2.0

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (GORA-498) Adding MongoDB Authentications

[Lewis John McGibbney (JIRA)]

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

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

Thank you Madhawa

> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[jira] [Commented] (GORA-498) Adding MongoDB Authentications

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GORA-498:
-

Github user asfgit closed the pull request at:

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


> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[GitHub] gora pull request #90: GORA-498 Adding mongodb authentications

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Fwd: Google Summer of Code 2017 is coming

[lewis john mcgibbney]

Hi Folks,
Please see above. If anyone is interested in participating in or mentoring
a GSoC project then please respond to this thread. Usually, from there you
can open a Jira ticket in which ever project it is you are interested and
we take it from there.
Have a great weekend.
Lewis


-- Forwarded message --
From: Ulrich Stärk 
Date: Fri, Feb 3, 2017 at 11:50 AM
Subject: Google Summer of Code 2017 is coming
To: ment...@community.apache.org


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and project
ideas, and in return have
the chance to get new code developed and - most importantly - to identify
and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply
separately.

If you want to participate with your project we ask you to do the following
things as soon as
possible but by no later than 2017-02-09:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2017, and they will show up
at [3]. Please be as
specific as possible when describing your idea. Include the programming
language, the tools and
skills required, but try not to scare potential students away. They are
supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...) and record them at [5].

Please use the COMDEV JIRA project for recording your ideas if your project
doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2017 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public d...@community.apache.org
list as much as possible
please). Use a recognized address when subscribing (@apache.org or one of
your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we will not get accepted.

Over the years we were able to complete hundreds of projects successfully.
Some of our prior
students are active contributors now! Let's make this year a success again!

Cheers,

Uli

P.S.: Except for the private parts (label spreadsheet mostly), this email
is free to be shared
publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2017ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels




-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

[jira] [Assigned] (GORA-498) Adding MongoDB Authentications

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney reassigned GORA-498:
-

Assignee: Madhawa Gunasekara

> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
>Assignee: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Cihad Guzel (JIRA)]

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

Cihad Guzel commented on GORA-502:
--

No, I haven't worked on this yet.

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
> Fix For: 0.8
>
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Commented] (GORA-498) Adding MongoDB Authentications

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GORA-498:
-

Github user drazzib commented on the issue:

https://github.com/apache/gora/pull/90
  
Hi @all !
[back to Gora MongoDB after some time offline :]

I've reviewed proposed code and it looks good to me.
IMHO, this could be merged for 0.7 release.

Regards,


> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[GitHub] gora issue #90: GORA-498 Adding mongodb authentications

[drazzib]

Github user drazzib commented on the issue:

https://github.com/apache/gora/pull/90
  
Hi @all !
[back to Gora MongoDB after some time offline :]

I've reviewed proposed code and it looks good to me.
IMHO, this could be merged for 0.7 release.

Regards,


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (GORA-498) Adding MongoDB Authentications

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-498:
--
Summary: Adding MongoDB Authentications  (was: Adding MongoDB 
Authetications)

> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[jira] [Resolved] (GORA-499) Potential NPE issue

[Lewis John McGibbney (JIRA)]

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

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

Thank you

> Potential NPE issue
> ---
>
> Key: GORA-499
> URL: https://issues.apache.org/jira/browse/GORA-499
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-cassandra
>Reporter: JC
>Assignee: JC
>Priority: Minor
> Fix For: 0.7
>
>
> Dear Gora developers
> In recent git repository, I've found the following lines in 
> gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraClient.java.
> {code:java}
> String opConsisLvl = (readOpConsLvl!=null || 
> !readOpConsLvl.isEmpty())?readOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
>   
> ccl.setDefaultReadConsistencyLevel(HConsistencyLevel.valueOf(opConsisLvl));
>   LOG.debug("Hector read consistency configured to '" + opConsisLvl + 
> "'.");
>   opConsisLvl = (writeOpConsLvl!=null || 
> !writeOpConsLvl.isEmpty())?writeOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
> {code}
> It seems, if readOpConsLvl or writeOpConsLvl is null, there could be 
> NullPointerException as the comparison operator is "||" rather using "&&". I 
> have no idea if this is an actual bug but just reporting. Thanks!



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

[jira] [Commented] (GORA-498) Adding MongoDB Authentications

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GORA-498:
-

Github user lewismc commented on the issue:

https://github.com/apache/gora/pull/90
  
@alfonsonishikawa ping


> Adding MongoDB Authentications
> --
>
> Key: GORA-498
> URL: https://issues.apache.org/jira/browse/GORA-498
> Project: Apache Gora
>  Issue Type: Improvement
>  Components: gora-mongodb
>Reporter: Madhawa Gunasekara
> Fix For: 0.7
>
>




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

[jira] [Updated] (GORA-499) Potential NPE issue

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-499:
--
Component/s: gora-cassandra

> Potential NPE issue
> ---
>
> Key: GORA-499
> URL: https://issues.apache.org/jira/browse/GORA-499
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-cassandra
>Reporter: JC
>Priority: Minor
> Fix For: 0.7
>
>
> Dear Gora developers
> In recent git repository, I've found the following lines in 
> gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraClient.java.
> {code:java}
> String opConsisLvl = (readOpConsLvl!=null || 
> !readOpConsLvl.isEmpty())?readOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
>   
> ccl.setDefaultReadConsistencyLevel(HConsistencyLevel.valueOf(opConsisLvl));
>   LOG.debug("Hector read consistency configured to '" + opConsisLvl + 
> "'.");
>   opConsisLvl = (writeOpConsLvl!=null || 
> !writeOpConsLvl.isEmpty())?writeOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
> {code}
> It seems, if readOpConsLvl or writeOpConsLvl is null, there could be 
> NullPointerException as the comparison operator is "||" rather using "&&". I 
> have no idea if this is an actual bug but just reporting. Thanks!



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

[GitHub] gora issue #90: GORA-498 Adding mongodb authentications

[lewismc]

Github user lewismc commented on the issue:

https://github.com/apache/gora/pull/90
  
@alfonsonishikawa ping


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (GORA-499) Potential NPE issue

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-499:
--
Fix Version/s: 0.7

> Potential NPE issue
> ---
>
> Key: GORA-499
> URL: https://issues.apache.org/jira/browse/GORA-499
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-cassandra
>Reporter: JC
>Priority: Minor
> Fix For: 0.7
>
>
> Dear Gora developers
> In recent git repository, I've found the following lines in 
> gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraClient.java.
> {code:java}
> String opConsisLvl = (readOpConsLvl!=null || 
> !readOpConsLvl.isEmpty())?readOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
>   
> ccl.setDefaultReadConsistencyLevel(HConsistencyLevel.valueOf(opConsisLvl));
>   LOG.debug("Hector read consistency configured to '" + opConsisLvl + 
> "'.");
>   opConsisLvl = (writeOpConsLvl!=null || 
> !writeOpConsLvl.isEmpty())?writeOpConsLvl:DEFAULT_HECTOR_CONSIS_LEVEL;
> {code}
> It seems, if readOpConsLvl or writeOpConsLvl is null, there could be 
> NullPointerException as the comparison operator is "||" rather using "&&". I 
> have no idea if this is an actual bug but just reporting. Thanks!



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

[jira] [Resolved] (GORA-501) Fix Javadoc for JDK1.8 compliance

[Lewis John McGibbney (JIRA)]

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

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

:)

> Fix Javadoc for JDK1.8 compliance
> -
>
> Key: GORA-501
> URL: https://issues.apache.org/jira/browse/GORA-501
> Project: Apache Gora
>  Issue Type: Task
>  Components: documentation
>Reporter: Lewis John McGibbney
>Assignee: Kevin Ratnasekera
>Priority: Blocker
> Fix For: 0.7
>
>
> Unfortunately it seems like the Jenkins build was not using JDK 1.8 for our 
> CI, I've just configured it and it results in the following
> {code}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 18:07 min
> [INFO] Finished at: 2017-01-28T09:24:19+00:00
> [INFO] Final Memory: 90M/818M
> [INFO] 
> 
> Waiting for Jenkins to finish collecting data
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.8:aggregate (default-cli) on 
> project gora: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:46:
>  warning: no @param for schema
> [ERROR] public static Map getFieldMap(Schema schema) {
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:46:
>  warning: no @return
> [ERROR] public static Map getFieldMap(Schema schema) {
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @param for clazz
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @return
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @throws for java.lang.NoSuchFieldException
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @throws for java.lang.IllegalAccessException
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:91:
>  warning: no description for @param
> [ERROR] * @param srcOffset
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:92:
>  warning: no description for @param
> [ERROR] * @param srcLength
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:144:
>  warning: no description for @param
> [ERROR] * @param off
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:145:
>  warning: no description for @param
> [ERROR] * @param len
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:166:
>  warning: no description for @param
> [ERROR] * @param s
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:185:
>  warning: no description for @param
> [ERROR] * @param b
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:195:
>  warning: no description for @param
> [ERROR] * @param b
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:207:
>  warning: no description for @param
> [ERROR] * @param val
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:222:
>  warning: no description for @param
> [ERROR] * @param bytes
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:231:
>  warning: no description for @param
> [ERROR] * @param bytes
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:232:
>  

[jira] [Updated] (GORA-500) bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-500:
--
Fix Version/s: 0.8

> bug in org.apache.gora.solr.store.SolrStore#getDatumWriter & #getDatumReader
> 
>
> Key: GORA-500
> URL: https://issues.apache.org/jira/browse/GORA-500
> Project: Apache Gora
>  Issue Type: Bug
>  Components: gora-solr
>Reporter: aakash
> Fix For: 0.8
>
>
> The above referenced methods use schemaId to cache DatumReader and 
> DatumWriter instances. This restricts you to using a schema type of "map" 
> with only a single value set. the caching method should use a more specific 
> identifier like what is returned from fieldSchema.toString() instead of 
> schemaId, so that the caching mechanism doesn't return a reader/writer that 
> doesn't match your data set.



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

[jira] [Commented] (GORA-501) Fix Javadoc for JDK1.8 compliance

[Kevin Ratnasekera (JIRA)]

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

Kevin Ratnasekera commented on GORA-501:


[~lewismc] Looks like the latest build passed without any issues. We can 
resolve this issue.

> Fix Javadoc for JDK1.8 compliance
> -
>
> Key: GORA-501
> URL: https://issues.apache.org/jira/browse/GORA-501
> Project: Apache Gora
>  Issue Type: Task
>  Components: documentation
>Reporter: Lewis John McGibbney
>Assignee: Kevin Ratnasekera
>Priority: Blocker
> Fix For: 0.7
>
>
> Unfortunately it seems like the Jenkins build was not using JDK 1.8 for our 
> CI, I've just configured it and it results in the following
> {code}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 18:07 min
> [INFO] Finished at: 2017-01-28T09:24:19+00:00
> [INFO] Final Memory: 90M/818M
> [INFO] 
> 
> Waiting for Jenkins to finish collecting data
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.8:aggregate (default-cli) on 
> project gora: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:46:
>  warning: no @param for schema
> [ERROR] public static Map getFieldMap(Schema schema) {
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:46:
>  warning: no @return
> [ERROR] public static Map getFieldMap(Schema schema) {
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @param for clazz
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @return
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @throws for java.lang.NoSuchFieldException
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/AvroUtils.java:68:
>  warning: no @throws for java.lang.IllegalAccessException
> [ERROR] public static Schema getSchema(Class clazz)
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:91:
>  warning: no description for @param
> [ERROR] * @param srcOffset
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:92:
>  warning: no description for @param
> [ERROR] * @param srcLength
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:144:
>  warning: no description for @param
> [ERROR] * @param off
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:145:
>  warning: no description for @param
> [ERROR] * @param len
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:166:
>  warning: no description for @param
> [ERROR] * @param s
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:185:
>  warning: no description for @param
> [ERROR] * @param b
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:195:
>  warning: no description for @param
> [ERROR] * @param b
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:207:
>  warning: no description for @param
> [ERROR] * @param val
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:222:
>  warning: no description for @param
> [ERROR] * @param bytes
> [ERROR] ^
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/gora-trunk/gora-core/src/main/java/org/apache/gora/util/ByteUtils.java:231:
>  warning: no description for @param
> [ERROR] * @param bytes
> [ERROR] ^
> [ERROR] 
> 

[jira] [Commented] (GORA-502) Implement Aerospike Datastore

[Lewis John McGibbney (JIRA)]

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

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

dynamite, are you actively working on this [~cguzel] ?

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[jira] [Updated] (GORA-502) Implement Aerospike Datastore

[Lewis John McGibbney (JIRA)]

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

Lewis John McGibbney updated GORA-502:
--
Component/s: gora-aerospike

> Implement Aerospike Datastore
> -
>
> Key: GORA-502
> URL: https://issues.apache.org/jira/browse/GORA-502
> Project: Apache Gora
>  Issue Type: New Feature
>  Components: gora-aerospike, storage
>Affects Versions: 0.6.1
>Reporter: Cihad Guzel
>
> Aerospike is a NoSQL database solution for real-time operational 
> applications, delivering predictable performance at scale, superior uptime, 
> and high availability at the lowest TCO compared to first-generation NoSQL 
> and relational databases. It could be nice to support Aerospike as a 
> datastore at Gora. Aerospike uses Apache v2 license for Java client and uses 
> aGPL license for Aerospike Server Community Edition. 
> (http://www.aerospike.com/products/)



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

[REPORT] Apache Gora

[lewis john mcgibbney]

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

## Description:
 - Apache Gora provides an in-memory data model and persistence for big
data.

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

## Activity:
 - Gora has recently seen some encouraging activity for new community
members
   in the form of bug fixes. We have one blocking issue prior to our 0.7
release.
   This has been pending for quite some time.

## Health report:
 - Gora would benefit from the 0.7 release as we have a numbef of new
datastores
   which, if released, could help the community spirit. We are still
working on
   the 0.7 blocker, however once done we can VOTE.

## PMC changes:

 - Currently 23 PMC members.
 - Kevin Ratnasekera was added to the PMC on Thu Jan 12 2017

## Committer base changes:

 - Currently 23 committers.
 - Kevin Ratnasekera was added as a committer on Wed Dec 07 2016

## Releases:

 - Last release was 0.6.1 on Sun Sep 13 2015

## Mailing list activity:

 - 2016Q4 - 2017Q1 was a reasonably quiet period. We seen encouraging
   figures for our user@ list.

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

 - u...@gora.apache.org:
- 77 subscribers (up 2 in the last 3 months):
- 22 emails sent to list (2 in previous quarter)


## JIRA activity:

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

-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney