[jira] [Commented] (GORA-664) Add datastore for Elasticsearch
[ https://issues.apache.org/jira/browse/GORA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213306#comment-17213306 ] Furkan Kamaci commented on GORA-664: Hi All, Please check the documentation to understand how Apache Gora works. Also, it will be quite helpful to subscribe to the mail list and try to contribute to Apache Gora since you may have some questions about the project and discuss your ideas related to Elasticsearch data store implementation. > 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 >Priority: Major > Labels: outreachy2020 > > 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] [Created] (GORA-617) Fix Inception Year at Gora Pig Module
Furkan KAMACI created GORA-617: -- Summary: Fix Inception Year at Gora Pig Module Key: GORA-617 URL: https://issues.apache.org/jira/browse/GORA-617 Project: Apache Gora Issue Type: Bug Components: gora-pig Affects Versions: 0.8 Reporter: Furkan KAMACI Assignee: Furkan KAMACI Fix For: 0.9 Inception year tag holds the year of the project's inception. So, it should be 2010 for all pom files within Apache Gora project. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GORA-532) Benchmarking Module
[ https://issues.apache.org/jira/browse/GORA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797341#comment-16797341 ] Furkan KAMACI commented on GORA-532: I've shared that link to be a guide for you about preparing a proposal. There are not any benchmarking proposal. You should prepare a proposal as like them. > 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
[ https://issues.apache.org/jira/browse/GORA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797300#comment-16797300 ] Furkan KAMACI commented on GORA-532: [~Sheriffo] you can check previous proposal from Gora Wiki: https://cwiki.apache.org/confluence/display/GORA/ > 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-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783365#comment-16783365 ] Furkan KAMACI commented on GORA-546: You can clarify things about this issue in comments. It helps other people to understand what this issue is really about. All other details, i.e. your potential implementation steps, getting suggestions about this issue can be done on the dev list. > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2019 > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783346#comment-16783346 ] Furkan KAMACI commented on GORA-546: Hi [~LahiruJayasekara] Actually, it is as defined in the description: Writing a custom source and sink connectors which can write/read data from/to Apache Gora data stores. > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2019 > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783331#comment-16783331 ] Furkan KAMACI commented on GORA-450: Hi All Interested Students, I suggest you to check other issues labeled as gsoc2019. I'll drop this issue from GSoC tasks since it doesn't require coding to accomplish. One can solve this issue as a warm-up. > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Major > Labels: gsoc2019 > Fix For: 0.9 > > > We should organize the content and also should have a better UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-450: --- Labels: (was: gsoc2019) > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Major > Fix For: 0.9 > > > We should organize the content and also should have a better UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767931#comment-16767931 ] Furkan KAMACI commented on GORA-546: Send an e-mail to user-subscr...@gora.apache.org For more information, you can check here: http://gora.apache.org/mailing_lists.html > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2019 > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GORA-546) Hazelcast Jet execution engine support
[ https://issues.apache.org/jira/browse/GORA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767568#comment-16767568 ] Furkan KAMACI commented on GORA-546: Hi [~LahiruJayasekara]! Thanks for your interest! I would suggest you check previous reports including mine which is from 2015, [Spark Backend Support for Gora (GORA-386)|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=57311721]. On the other hand, start with checking out the source code, try to compile it, and try to resolve minor issues to get started with project. Also, it is worth to mention that don't forget to subscribe to user list. > Hazelcast Jet execution engine support > -- > > Key: GORA-546 > URL: https://issues.apache.org/jira/browse/GORA-546 > Project: Apache Gora > Issue Type: New Feature >Reporter: Kevin Ratnasekera >Priority: Major > Labels: gsoc2019 > > Now Apache Gora supports Map Reduce and Spark engines. May we should extend > this with Hazelcast Jet. [1][2] Feature should include writing custom source > and sink connectors [3] which can write / read data from / to Apache Gora > data stores. > [1] [https://jet.hazelcast.org/use-cases/fast-batch-processing/] > [2] [https://github.com/hazelcast/hazelcast-jet] > [3] https://jet.hazelcast.org/connectors/batch-connectors/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GORA-532) Benchmarking Module
[ https://issues.apache.org/jira/browse/GORA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764858#comment-16764858 ] Furkan KAMACI commented on GORA-532: Sure! > 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] [Updated] (GORA-532) Benchmarking Module
[ https://issues.apache.org/jira/browse/GORA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-532: --- Labels: gsoc2018 (was: ) > 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 > 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-485) Apache Kudu datastore for Gora
[ https://issues.apache.org/jira/browse/GORA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371981#comment-16371981 ] Furkan KAMACI commented on GORA-485: [~cguzel], go for it! Create a PR when you are ready. So, we can check and make suggestions on there. > Apache Kudu datastore for Gora > -- > > Key: GORA-485 > URL: https://issues.apache.org/jira/browse/GORA-485 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.8 >Reporter: Kevin Ratnasekera >Assignee: Cihad Guzel >Priority: Major > Labels: gora-kudu, gsoc2017 > Fix For: 0.9 > > > Apache Kudu is getting lot of attention. Kudu is a key/value store optimized > for analytic workloads. [1] > [1] > https://blog.cloudera.com/blog/2015/09/kudu-new-apache-hadoop-storage-for-fast-analytics-on-fast-data/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GORA-532) Benchmarking Module
Furkan KAMACI created GORA-532: -- Summary: 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 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-531) Upgrade HBase to 1.2.6
[ https://issues.apache.org/jira/browse/GORA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI resolved GORA-531. Resolution: Fixed > Upgrade HBase to 1.2.6 > -- > > Key: GORA-531 > URL: https://issues.apache.org/jira/browse/GORA-531 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hbase >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Major > Fix For: 0.9 > > > Gora has support for Hbase 1.2.3. We should upgrade it to 1.2.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GORA-528) Add Support for Spark 2.2.1
[ https://issues.apache.org/jira/browse/GORA-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI resolved GORA-528. Resolution: Fixed > Add Support for Spark 2.2.1 > --- > > Key: GORA-528 > URL: https://issues.apache.org/jira/browse/GORA-528 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Major > Fix For: 0.9 > > > Add Spark 2.2.1 support for Spark backend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GORA-531) Upgrade HBase to 1.2.6
Furkan KAMACI created GORA-531: -- Summary: Upgrade HBase to 1.2.6 Key: GORA-531 URL: https://issues.apache.org/jira/browse/GORA-531 Project: Apache Gora Issue Type: Improvement Components: gora-hbase Reporter: Furkan KAMACI Assignee: Furkan KAMACI Fix For: 0.9 Gora has support for Hbase 1.2.3. We should upgrade it to 1.2.6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GORA-528) Add Support for Spark 2.2.1
[ https://issues.apache.org/jira/browse/GORA-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-528: --- Summary: Add Support for Spark 2.2.1 (was: Add support for Spark 2.2.1) > Add Support for Spark 2.2.1 > --- > > Key: GORA-528 > URL: https://issues.apache.org/jira/browse/GORA-528 > Project: Apache Gora > Issue Type: Improvement > Components: gora-core >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI > Fix For: 0.8 > > > Add Spark 2.2.1 support for Spark backend. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GORA-528) Add support for Spark 2.2.1
Furkan KAMACI created GORA-528: -- Summary: Add support for Spark 2.2.1 Key: GORA-528 URL: https://issues.apache.org/jira/browse/GORA-528 Project: Apache Gora Issue Type: Improvement Components: gora-core Reporter: Furkan KAMACI Assignee: Furkan KAMACI Fix For: 0.8 Add Spark 2.2.1 support for Spark backend. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean
[ https://issues.apache.org/jira/browse/GORA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039201#comment-16039201 ] Furkan KAMACI commented on GORA-512: [~djkevincr] [~nishadi] exception is already thrown within a try catch. So, it will be caught there and unnecessary. > Fail at the time of error logging if KeyClass in gora-hbase-mapping is not > the same as the one in the data bean > --- > > Key: GORA-512 > URL: https://issues.apache.org/jira/browse/GORA-512 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hbase >Reporter: Nishadi Kirielle >Assignee: Nishadi Kirielle >Priority: Minor > > In the current implementation, when reading the HBase mapping file, if the > HBase mapping file does not have a matching key class and name to the data > bean, it only logs that information.[1] It does not fail at the time of > detecting it. It fails only at the time of building the mapper [2] when it > detects the table name is null. It will be better if it can fail at the time > of detecting that mapping file is missing the corresponding class. > [1]. > https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797 > [2]. > https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GORA-502) Implement Aerospike Datastore
[ https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953727#comment-15953727 ] Furkan KAMACI commented on GORA-502: Thanks! > 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 > Labels: gsoc2017 > 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-502) Implement Aerospike Datastore
[ https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953619#comment-15953619 ] Furkan KAMACI commented on GORA-502: [~nishadi.k] could you also add final version of your proposal to wiki: https://cwiki.apache.org/confluence/display/GORA/GSoC+2017+Proposals > 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 > Labels: gsoc2017 > 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-485) Apache Kudu datastore for Gora
[ https://issues.apache.org/jira/browse/GORA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931660#comment-15931660 ] Furkan KAMACI commented on GORA-485: [~tugbadogan] I've created a page for GSoC 2017 Proposals: https://cwiki.apache.org/confluence/display/GORA/GSoC+2017+Proposals Please check the previous years' proposals and prepare one. On the other hand, I suggest you to download and compile the project, examine the source code and try to fix some issues as a first step to warm up. Don't hesitate to ask on mail list if you have any questions. > Apache Kudu datastore for Gora > -- > > Key: GORA-485 > URL: https://issues.apache.org/jira/browse/GORA-485 > Project: Apache Gora > Issue Type: New Feature >Affects Versions: 0.8 >Reporter: Kevin Ratnasekera > Labels: gora-kudu, gsoc2017 > Fix For: 0.8 > > > Apache Kudu is getting lot of attention. Kudu is a key/value store optimized > for analytic workloads. [1] > [1] > https://blog.cloudera.com/blog/2015/09/kudu-new-apache-hadoop-storage-for-fast-analytics-on-fast-data/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GORA-502) Implement Aerospike Datastore
[ https://issues.apache.org/jira/browse/GORA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907764#comment-15907764 ] Furkan KAMACI commented on GORA-502: [~nishadi.k] and [~serhatg] I've created a page for GSoC 2017 Proposals: https://cwiki.apache.org/confluence/display/GORA/GSoC+2017+Proposals Please check the previous years' proposals and prepare yourselves. On the other hand, I suggest you to download and compile the project, examine the source code and try to fix some issues as a first step to warm up. Don't hesitate to ask on mail list if you have any questions. > 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 > Labels: gsoc2017 > 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-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295291#comment-15295291 ] Furkan KAMACI commented on GORA-445: [~cguzel] when you create a pull request you can start its name with corresponding issue key. This will trigger integration of Github and Jira and a comment will automatically be placed about your pr at related issue. > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI >Priority: Critical > Fix For: 0.7 > > Attachments: gora-core_dependency_tree.txt, > spark-core_2.10_dependeny_tree.txt > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290982#comment-15290982 ] Furkan KAMACI commented on GORA-439: [~lewismc] can you check this PR? > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI reassigned GORA-450: -- Assignee: Furkan KAMACI > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI > Fix For: 0.8 > > > We should organize the content and also should have a better UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-437) Implement CouchDB Datastore
[ https://issues.apache.org/jira/browse/GORA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI reassigned GORA-437: -- Assignee: Furkan KAMACI > Implement CouchDB Datastore > --- > > Key: GORA-437 > URL: https://issues.apache.org/jira/browse/GORA-437 > Project: Apache Gora > Issue Type: New Feature >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI > Labels: gora-couchdb, storage > Fix For: 0.8 > > > Apache CouchDB is a document-oriented NoSQL database that uses JSON to store > data, JavaScript as its query language using MapReduce, and HTTP for an API. > It could be nice to support CouchDB as a datastore at Gora. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984175#comment-14984175
]
Furkan KAMACI commented on GORA-431:
There is not any boolean parameter at Avro or Hadoop for object reuse. We will
need to change the architecture to implement it. Do I miss anything?
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 0.7
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980961#comment-14980961
]
Furkan KAMACI commented on GORA-431:
[~renato2099], [~lewismc] I found that issue:
https://issues.apache.org/jira/browse/AVRO-911 which argues to remove reusing
objects or not. Conclusion is it has some benefits at some cases.
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 0.7
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-450: --- Fix Version/s: 0.7 > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI > Fix For: 0.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-450) Gora Needs a New Website
Furkan KAMACI created GORA-450: -- Summary: Gora Needs a New Website Key: GORA-450 URL: https://issues.apache.org/jira/browse/GORA-450 Project: Apache Gora Issue Type: Task Reporter: Furkan KAMACI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-450: --- Description: We should organize the content and also should have a better UI. > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI > Fix For: 0.7 > > > We should organize the content and also should have a better UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-450) Gora Needs a New Website
[ https://issues.apache.org/jira/browse/GORA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981486#comment-14981486 ] Furkan KAMACI commented on GORA-450: Solr's website is very good: http://lucene.apache.org/solr/. CouchDB (http://couchdb.apache.org/) and Wicket (http://wicket.apache.org/) has nice websites too. I can also add Storm (http://storm.apache.org/ and Spark (http://spark.apache.org/) to that list. Here is the issue of Solr for its new website: SOLR-6058 > Gora Needs a New Website > > > Key: GORA-450 > URL: https://issues.apache.org/jira/browse/GORA-450 > Project: Apache Gora > Issue Type: Task >Reporter: Furkan KAMACI > Fix For: 0.7 > > > We should organize the content and also should have a better UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978575#comment-14978575 ] Furkan KAMACI commented on GORA-439: When MemStoreTest's tests are ignored it passes all tests. > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI resolved GORA-439. Resolution: Fixed > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-445: --- Attachment: gora-core_dependency_tree.txt I've attached dependency tree of gora-core module. > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > Attachments: gora-core_dependency_tree.txt > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GORA-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977234#comment-14977234 ] Furkan KAMACI edited comment on GORA-445 at 10/27/15 10:07 PM: --- I've attached dependency trees of gora-core module and spark-core 2.10. was (Author: kamaci): I've attached dependency tree of gora-core module. > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > Attachments: gora-core_dependency_tree.txt, > spark-core_2.10_dependeny_tree.txt > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977328#comment-14977328 ] Furkan KAMACI commented on GORA-439: Does anybody has a comment for [~renato2099]'s comment: bq. I am in favour of this, but yeah we might discuss about the API some more to see whether it makes sense to keep what. I mean right now, if those parameters are not being used, sure maybe we can take them out, but I think we should look into why they were put there e.g. passing the dataStore object into the GoraMapper, is this because we can get it through the Query object? I think most of the others are a lot more straight forward. > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-445: --- Attachment: spark-core_2.10_dependeny_tree.txt > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > Attachments: gora-core_dependency_tree.txt, > spark-core_2.10_dependeny_tree.txt > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977335#comment-14977335 ] Furkan KAMACI commented on GORA-445: List of included dependencies' categories: http://mvnrepository.com/artifact/org.apache.spark/spark-core_2.10/1.4.1 > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > Attachments: gora-core_dependency_tree.txt, > spark-core_2.10_dependeny_tree.txt > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-442) Create documentation for GoraSparkEngine
[ https://issues.apache.org/jira/browse/GORA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI resolved GORA-442. Resolution: Fixed > Create documentation for GoraSparkEngine > > > Key: GORA-442 > URL: https://issues.apache.org/jira/browse/GORA-442 > Project: Apache Gora > Issue Type: Task > Components: gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > > [~kamaci] and I discussed putting together documentation for the website > which explains how to use the SparkEngine as well as the demo for using this > with LogManager tutorial. > This issue should document exactly that! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-442) Create documentation for GoraSparkEngine
[ https://issues.apache.org/jira/browse/GORA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972907#comment-14972907 ] Furkan KAMACI commented on GORA-442: Documentation changes done at http://gora.apache.org/current/index.html, http://gora.apache.org/current/gora-core.html and http://gora.apache.org/current/tutorial.html. > Create documentation for GoraSparkEngine > > > Key: GORA-442 > URL: https://issues.apache.org/jira/browse/GORA-442 > Project: Apache Gora > Issue Type: Bug > Components: gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > > [~kamaci] and I discussed putting together documentation for the website > which explains how to use the SparkEngine as well as the demo for using this > with LogManager tutorial. > This issue should document exactly that! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-368) Address flagged Sonar error in Gora package design
[ https://issues.apache.org/jira/browse/GORA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877305#comment-14877305 ] Furkan KAMACI commented on GORA-368: So we can close it :) > Address flagged Sonar error in Gora package design > -- > > Key: GORA-368 > URL: https://issues.apache.org/jira/browse/GORA-368 > Project: Apache Gora > Issue Type: Improvement > Components: build process >Affects Versions: 0.5 >Reporter: Lewis John McGibbney > Fix For: 0.7 > > > Right now the sonar:sonar job is configured on our trunk build to execute the > following target > sonar:sonar -Dsonar.skipPackageDesign=true, this prevents the following > error. We need to address this. > BTW, to reproduce this error, you can download sonarqube and run the Sonar > analysis from here > http://www.sonarqube.org/downloads/ > [ERROR] Failed to execute goal > org.codehaus.sonar:sonar-maven-plugin:4.3:sonar (default-cli) on project > imap-core: Directory contains files belonging to different packages : > /path/to/some/project/sources/package Please fix your source code or use > sonar.skipPackageDesign=true to continue the analysis. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.codehaus.sonar:sonar-maven-plugin:4.3:sonar > (default-cli) on project imap-core: Directory contains files belonging > to different packages : /path/to/some/project/sources/package Please fix > your source code or use sonar.skipPackageDesign=true to continue the > analysis. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(Del -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-445) Review extent of transative dependencies post GORA-386
[ https://issues.apache.org/jira/browse/GORA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI reassigned GORA-445: -- Assignee: Furkan KAMACI > Review extent of transative dependencies post GORA-386 > -- > > Key: GORA-445 > URL: https://issues.apache.org/jira/browse/GORA-445 > Project: Apache Gora > Issue Type: New Feature > Components: build process, gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > > Now that Apache Spark is included within gora-core, I've noticed a hike in > the number of transitive dependencies being pulled as a result of including > gora-core in my project pom.xml. > We should see if we can possibly some of the transitive > dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-368) Address flagged Sonar error in Gora package design
[ https://issues.apache.org/jira/browse/GORA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-368: --- Summary: Address flagged Sonar error in Gora package design (was: Address flagged Sonar error in Gora pakage design) > Address flagged Sonar error in Gora package design > -- > > Key: GORA-368 > URL: https://issues.apache.org/jira/browse/GORA-368 > Project: Apache Gora > Issue Type: Improvement > Components: build process >Affects Versions: 0.5 >Reporter: Lewis John McGibbney > Fix For: 0.7 > > > Right now the sonar:sonar job is configured on our trunk build to execute the > following target > sonar:sonar -Dsonar.skipPackageDesign=true, this prevents the following > error. We need to address this. > BTW, to reproduce this error, you can download sonarqube and run the Sonar > analysis from here > http://www.sonarqube.org/downloads/ > [ERROR] Failed to execute goal > org.codehaus.sonar:sonar-maven-plugin:4.3:sonar (default-cli) on project > imap-core: Directory contains files belonging to different packages : > /path/to/some/project/sources/package Please fix your source code or use > sonar.skipPackageDesign=true to continue the analysis. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.codehaus.sonar:sonar-maven-plugin:4.3:sonar > (default-cli) on project imap-core: Directory contains files belonging > to different packages : /path/to/some/project/sources/package Please fix > your source code or use sonar.skipPackageDesign=true to continue the > analysis. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(Del -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI reassigned GORA-439: -- Assignee: Furkan KAMACI > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-279) Hazelcast module
[ https://issues.apache.org/jira/browse/GORA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747119#comment-14747119 ] Furkan KAMACI commented on GORA-279: This issue is linked to GORA-409 since Hazelcast is a JCache Provider and implementing a JCache data store provides usage of any JCache provider. > Hazelcast module > > > Key: GORA-279 > URL: https://issues.apache.org/jira/browse/GORA-279 > Project: Apache Gora > Issue Type: Wish > Components: gora-hazelcast >Reporter: Julien Nioche > Labels: gsoc2014 > Fix For: 0.7 > > Attachments: gsoc_proposal_draft.odt > > > HazelCast seems to be a popular in-memory data grid > [http://www.hazelcast.com/]. The community edition is under the ASL v2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-418) Multi Execution Engine for Gora
[ https://issues.apache.org/jira/browse/GORA-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-418: --- Description: At the present we support mapreduce engine. We can support multi execution engine for GORA. Here is a useful conversation from mail archive: http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e was:At the present we support mapreduce engine. We can support multi execution engine for GORA > Multi Execution Engine for Gora > --- > > Key: GORA-418 > URL: https://issues.apache.org/jira/browse/GORA-418 > Project: Apache Gora > Issue Type: New Feature >Reporter: Talat UYARER > Labels: gsoc2015 > Fix For: 0.7 > > > At the present we support mapreduce engine. We can support multi execution > engine for GORA. > Here is a useful conversation from mail archive: > http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GORA-359) Add integration to other distributed system frameworks to allow Gora as data ingest
[ https://issues.apache.org/jira/browse/GORA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI resolved GORA-359. Resolution: Duplicate > Add integration to other distributed system frameworks to allow Gora as data > ingest > --- > > Key: GORA-359 > URL: https://issues.apache.org/jira/browse/GORA-359 > Project: Apache Gora > Issue Type: Improvement >Reporter: Henry Saputra > Fix For: 0.7 > > > We already integrate with Giraph as one of the vehicle to ingest data. The > next steps would be to integrated with other distributed systems frameworks > like Apache Spark, Tez, or Flink to naturally allow option to use Gora to > ingest and process data in their workflow [1] > [1] > http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (GORA-359) Add integration to other distributed system frameworks to allow Gora as data ingest
[ https://issues.apache.org/jira/browse/GORA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI closed GORA-359. -- > Add integration to other distributed system frameworks to allow Gora as data > ingest > --- > > Key: GORA-359 > URL: https://issues.apache.org/jira/browse/GORA-359 > Project: Apache Gora > Issue Type: Improvement >Reporter: Henry Saputra > Fix For: 0.7 > > > We already integrate with Giraph as one of the vehicle to ingest data. The > next steps would be to integrated with other distributed systems frameworks > like Apache Spark, Tez, or Flink to naturally allow option to use Gora to > ingest and process data in their workflow [1] > [1] > http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GORA-442) Create documentation for GoraSparkEngine
[ https://issues.apache.org/jira/browse/GORA-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI reassigned GORA-442: -- Assignee: Furkan KAMACI > Create documentation for GoraSparkEngine > > > Key: GORA-442 > URL: https://issues.apache.org/jira/browse/GORA-442 > Project: Apache Gora > Issue Type: Bug > Components: gora-core >Affects Versions: 0.6.1 >Reporter: Lewis John McGibbney >Assignee: Furkan KAMACI > Fix For: 0.7 > > > [~kamaci] and I discussed putting together documentation for the website > which explains how to use the SparkEngine as well as the demo for using this > with LogManager tutorial. > This issue should document exactly that! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-443) Upgrade HBase to 1.1.2
[
https://issues.apache.org/jira/browse/GORA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated GORA-443:
---
Fix Version/s: 0.7
> Upgrade HBase to 1.1.2
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
> Issue Type: Improvement
>Reporter: Ted Yu
> 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.4#6332)
[jira] [Updated] (GORA-443) Upgrade HBase to 1.1.2
[
https://issues.apache.org/jira/browse/GORA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated GORA-443:
---
Component/s: gora-hbase
> Upgrade HBase to 1.1.2
> --
>
> Key: GORA-443
> URL: https://issues.apache.org/jira/browse/GORA-443
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-hbase
>Reporter: Ted Yu
> 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.4#6332)
[jira] [Updated] (GORA-359) Add integration to other distributed system frameworks to allow Gora as data ingest
[ https://issues.apache.org/jira/browse/GORA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-359: --- Description: We already integrate with Giraph as one of the vehicle to ingest data. The next steps would be to integrated with other distributed systems frameworks like Apache Spark, Tez, or Flink to naturally allow option to use Gora to ingest and process data in their workflow [1] [1] http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e was: We already integrate with Giraph as one of the vehicle to ingest data. The nest steps would be to integrated with other distributed systems frameworks like Apache Spark, Tez, or Flink to naturally allow option to use Gora to ingest and process data in their workflow [1] [1] http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e > Add integration to other distributed system frameworks to allow Gora as data > ingest > --- > > Key: GORA-359 > URL: https://issues.apache.org/jira/browse/GORA-359 > Project: Apache Gora > Issue Type: Improvement >Reporter: Henry Saputra > Fix For: 0.7 > > > We already integrate with Giraph as one of the vehicle to ingest data. The > next steps would be to integrated with other distributed systems frameworks > like Apache Spark, Tez, or Flink to naturally allow option to use Gora to > ingest and process data in their workflow [1] > [1] > http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-359) Add integration to other distributed system frameworks to allow Gora as data ingest
[ https://issues.apache.org/jira/browse/GORA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745107#comment-14745107 ] Furkan KAMACI commented on GORA-359: This issue is related to and duplicated by this one: GORA-418. Spark integration is done by GORA-386 which is related to GORA-418. So, we can close one of them and than create individual issues for Tez, Flink etc. > Add integration to other distributed system frameworks to allow Gora as data > ingest > --- > > Key: GORA-359 > URL: https://issues.apache.org/jira/browse/GORA-359 > Project: Apache Gora > Issue Type: Improvement >Reporter: Henry Saputra > Fix For: 0.7 > > > We already integrate with Giraph as one of the vehicle to ingest data. The > nest steps would be to integrated with other distributed systems frameworks > like Apache Spark, Tez, or Flink to naturally allow option to use Gora to > ingest and process data in their workflow [1] > [1] > http://mail-archives.apache.org/mod_mbox/gora-dev/201407.mbox/%3cCAGaRif2UkGhVc4mp295hL2bX5LuRu3=p5o-mq3yfeuoaaes...@mail.gmail.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-425) Allow different tables per DataStore object
[ https://issues.apache.org/jira/browse/GORA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734316#comment-14734316 ] Furkan KAMACI commented on GORA-425: It works! I probably had some DNS etc. issues. Btw it could be nice to have that feature. So, if I can have time I would like to take care of it. > Allow different tables per DataStore object > --- > > Key: GORA-425 > URL: https://issues.apache.org/jira/browse/GORA-425 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hbase >Affects Versions: 0.6 >Reporter: Renato Javier Marroquín Mogrovejo > Fix For: 0.7 > > > Issue described by Harry Papaxenopoulos in the mailing list. > http://www.mail-archive.com/dev%40gora.apache.org/msg05949.html > We should extend this feature to the other data stores as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-438) Erroneous Exception Message at IOUtils.java
Furkan KAMACI created GORA-438: -- Summary: Erroneous Exception Message at IOUtils.java Key: GORA-438 URL: https://issues.apache.org/jira/browse/GORA-438 Project: Apache Gora Issue Type: Bug Reporter: Furkan KAMACI Priority: Minor Fix For: 0.7 Erroneous exception message: bq. cannot write to DataOutput of instance: at *read* method of _IOUtils.java_ should be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-438) Erroneous Exception Message at IOUtils.java
[ https://issues.apache.org/jira/browse/GORA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-438: --- Description: Erroneous exception message: bq. cannot write to DataOutput of instance: at *readObject* method of _IOUtils.java_ should be fixed. was: Erroneous exception message: bq. cannot write to DataOutput of instance: at *read* method of _IOUtils.java_ should be fixed. > Erroneous Exception Message at IOUtils.java > --- > > Key: GORA-438 > URL: https://issues.apache.org/jira/browse/GORA-438 > Project: Apache Gora > Issue Type: Bug >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Erroneous exception message: > bq. cannot write to DataOutput of instance: > at *readObject* method of _IOUtils.java_ should be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-437) Implement CouchDB Datastore
[ https://issues.apache.org/jira/browse/GORA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-437: --- Summary: Implement CouchDB Datastore (was: CouchDB Datastore) > Implement CouchDB Datastore > --- > > Key: GORA-437 > URL: https://issues.apache.org/jira/browse/GORA-437 > Project: Apache Gora > Issue Type: New Feature >Reporter: Furkan KAMACI > Labels: gora-couchdb, storage > Fix For: 0.7 > > > Apache CouchDB is a document-oriented NoSQL database that uses JSON to store > data, JavaScript as its query language using MapReduce, and HTTP for an API. > It could be nice to support CouchDB as a datastore at Gora. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-437) CouchDB Datastore
[ https://issues.apache.org/jira/browse/GORA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-437: --- Labels: gora-couchdb storage (was: gora-couchdb) > CouchDB Datastore > - > > Key: GORA-437 > URL: https://issues.apache.org/jira/browse/GORA-437 > Project: Apache Gora > Issue Type: New Feature >Reporter: Furkan KAMACI > Labels: gora-couchdb, storage > Fix For: 0.7 > > > Apache CouchDB is a document-oriented NoSQL database that uses JSON to store > data, JavaScript as its query language using MapReduce, and HTTP for an API. > It could be nice to support CouchDB as a datastore at Gora. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-439) Remove Unused Method Parameters
Furkan KAMACI created GORA-439: -- Summary: Remove Unused Method Parameters Key: GORA-439 URL: https://issues.apache.org/jira/browse/GORA-439 Project: Apache Gora Issue Type: Improvement Reporter: Furkan KAMACI Priority: Minor Fix For: 0.7 Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-439) Remove Unused Method Parameters
[ https://issues.apache.org/jira/browse/GORA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732100#comment-14732100 ] Furkan KAMACI commented on GORA-439: I've finished this improvement. I'll create a pull request as soon as my latest pull request is considered: https://github.com/apache/gora/pull/42 > Remove Unused Method Parameters > --- > > Key: GORA-439 > URL: https://issues.apache.org/jira/browse/GORA-439 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.7 > > > Remove unused method parameters and make API signatures clean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-437) CouchDB Datastore
Furkan KAMACI created GORA-437: -- Summary: CouchDB Datastore Key: GORA-437 URL: https://issues.apache.org/jira/browse/GORA-437 Project: Apache Gora Issue Type: Task Reporter: Furkan KAMACI Fix For: 0.7 Apache CouchDB is a document-oriented NoSQL database that uses JSON to store data, JavaScript as its query language using MapReduce, and HTTP for an API. It could be nice to support CouchDB as a datastore at Gora. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-436) Improve Source Code as Java 7 Compatible
[ https://issues.apache.org/jira/browse/GORA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732015#comment-14732015 ] Furkan KAMACI commented on GORA-436: [~lewismc] I've created PR as: https://github.com/apache/gora/pull/41 > Improve Source Code as Java 7 Compatible > > > Key: GORA-436 > URL: https://issues.apache.org/jira/browse/GORA-436 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.6.1 > > > Improvements for diamond operators, automatic resource handling, exception > collapsing and iterations. These changes will make source code more > understandable and readable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-435) Clean Up Code and Fix Potential Bugs
Furkan KAMACI created GORA-435: -- Summary: Clean Up Code and Fix Potential Bugs Key: GORA-435 URL: https://issues.apache.org/jira/browse/GORA-435 Project: Apache Gora Issue Type: Improvement Reporter: Furkan KAMACI Priority: Minor Fix For: 0.6.1 Fix potential bugs, make performance improvements and clean code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-436) Improve Source Code as Java 7 Compatible
[ https://issues.apache.org/jira/browse/GORA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731372#comment-14731372 ] Furkan KAMACI commented on GORA-436: I've finished this improvement. I'll create a pull request as soon as my latest pull request is considered: https://github.com/apache/gora/pull/39 > Improve Source Code as Java 7 Compatible > > > Key: GORA-436 > URL: https://issues.apache.org/jira/browse/GORA-436 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.6.1 > > > Improvements for diamond operators, automatic resource handling, exception > collapsing and iterations. These changes will make source code more > understandable and readable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-436) Improve Source Code as Java 7 Compatible
Furkan KAMACI created GORA-436: -- Summary: Improve Source Code as Java 7 Compatible Key: GORA-436 URL: https://issues.apache.org/jira/browse/GORA-436 Project: Apache Gora Issue Type: Improvement Reporter: Furkan KAMACI Priority: Minor Fix For: 0.6.1 Improvements for diamond operators, automatic resource handling, exception collapsing and iterations. These changes will make source code more understandable and readable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-266) Lucene datastore for Gora
[ https://issues.apache.org/jira/browse/GORA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731498#comment-14731498 ] Furkan KAMACI commented on GORA-266: Is this patch ready to merge? > Lucene datastore for Gora > - > > Key: GORA-266 > URL: https://issues.apache.org/jira/browse/GORA-266 > Project: Apache Gora > Issue Type: New Feature > Components: gora-lucene >Reporter: Lewis John McGibbney >Assignee: Scott Stults >Priority: Minor > Labels: features > Fix For: 0.7 > > Attachments: GORA-266.patch > > > Sometimes we don't need to set up, administer, maintain and configure a > running solr server(s). > Sometime we just want to write to Lucene index files and read directly from > them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-433) Non-Final Public Static Fields Should Be Final
[ https://issues.apache.org/jira/browse/GORA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729630#comment-14729630 ] Furkan KAMACI commented on GORA-433: [~lewismc] I've created a new pull request after you comment about "rebase". > Non-Final Public Static Fields Should Be Final > --- > > Key: GORA-433 > URL: https://issues.apache.org/jira/browse/GORA-433 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Assignee: Furkan KAMACI >Priority: Minor > Fix For: 0.6.1 > > > Non-final public static fields can be changed by external classes (by a > malicious code or accidentally). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729848#comment-14729848
]
Furkan KAMACI commented on GORA-431:
[~lewismc] I'm changing Fix Version/s from 0.6.1 to 0.7 due to we need to test
its effects as [~renato2099] mentioned.
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 0.6.1
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GORA-434) Documents are Not Committed Into Solr Store
Furkan KAMACI created GORA-434: -- Summary: Documents are Not Committed Into Solr Store Key: GORA-434 URL: https://issues.apache.org/jira/browse/GORA-434 Project: Apache Gora Issue Type: Bug Components: gora-solr Reporter: Furkan KAMACI Fix For: 0.6.1 I was testing to write into Solr database and I realized that it doesn't commit documents which are at last buffer when buffer is not equal to default commit size. For example, run LogAnalytics example with a configuration of reading from Hbase and persisting results into Solr. Result size should be 3300 but when you check Solr you will see that it is less than it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-434) Documents are Not Committed Into Solr Store
[ https://issues.apache.org/jira/browse/GORA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729725#comment-14729725 ] Furkan KAMACI commented on GORA-434: There was a comment for not flushing: bq. In testing, the index gets closed before the commit in flush() can happen so an exception gets thrown I've run the tests and didn't get any error. If so, we should fix the tests otherwise it is a major bug when writing into SolrStore. > Documents are Not Committed Into Solr Store > --- > > Key: GORA-434 > URL: https://issues.apache.org/jira/browse/GORA-434 > Project: Apache Gora > Issue Type: Bug > Components: gora-solr >Reporter: Furkan KAMACI > Fix For: 0.6.1 > > > I was testing to write into Solr database and I realized that it doesn't > commit documents which are at last buffer when buffer is not equal to default > commit size. For example, run LogAnalytics example with a configuration of > reading from Hbase and persisting results into Solr. Result size should be > 3300 but when you check Solr you will see that it is less than it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated GORA-431:
---
Fix Version/s: (was: 0.6.1)
0.7
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 0.7
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GORA-433) Non-Final Public Static Fields Should Be Final
[ https://issues.apache.org/jira/browse/GORA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-433: --- Summary: Non-Final Public Static Fields Should Be Final (was: Make Final Non-Final Public Static Fields ) > Non-Final Public Static Fields Should Be Final > --- > > Key: GORA-433 > URL: https://issues.apache.org/jira/browse/GORA-433 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.6.1 > > > Non-final public static fields can be changed by external classes (by a > malicious code or accidentally). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728742#comment-14728742
]
Furkan KAMACI commented on GORA-431:
These are from latest e-mails at mail list:
Me:
bq. Issue for general serialization mechanism for Map Reduce:
https://issues.apache.org/jira/browse/HADOOP-1986 and here is the main usage of
that parameter:
https://avro.apache.org/docs/1.7.6/api/java/org/apache/avro/generic/GenericDatumReader.html#read(D,
org.apache.avro.io.Decoder) [~renato2099], I've checked Hadoop source codes
and I see that we have to find an appropriate way to pass that property. We do
not instantiate that class at Gora. What do you suggest?
Renato:
bq. Thanks for taking the time and looking into this. I agree with you, there
is something fuzzy going on there. So our persistent classes extent
org.apache.avro.specific.SpecificRecord and use their specific
DatumReader/Writer which in turn use the the methods that you are pointing out.
And yes, we should find a way to pass this into the datastores (which shouldn't
be too hard) but we should also double check if it makes sense to allow the
user to set it or not. I mean is it always better to have it set as
(smaller memory footprint)? or is there any case when using the object between
serialization that could cause wrong behaviour if we were reusing the object? I
don't know the actual effect on setting this to true or false. Could you please
create a simple test where we could see the different behaviour of setting this
to true or false? That would be great as it'd help everybody understand better
what was the reasoning for setting this parameter always true.
[~lewismc] I should create a test case for it and according to that test we can
decide whether to remove it or add as a config.
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Priority: Minor
> Fix For: 0.6.1
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GORA-425) Allow different tables per DataStore object
[ https://issues.apache.org/jira/browse/GORA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728753#comment-14728753 ] Furkan KAMACI commented on GORA-425: [~renato2099] it seems that link for mail archive you mentioned at description doesn't work? > Allow different tables per DataStore object > --- > > Key: GORA-425 > URL: https://issues.apache.org/jira/browse/GORA-425 > Project: Apache Gora > Issue Type: Improvement > Components: gora-hbase >Affects Versions: 0.6 >Reporter: Renato Javier Marroquín Mogrovejo > Fix For: 0.7 > > > Issue described by Harry Papaxenopoulos in the mailing list. > http://www.mail-archive.com/dev%40gora.apache.org/msg05949.html > We should extend this feature to the other data stores as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-433) Make Final Non-Final Public Static Fields
[ https://issues.apache.org/jira/browse/GORA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-433: --- Description: Non-final public static fields can be changed by external classes (by a malicious code or accidentally). (was: Non-final public static fields can be changed by external classes (by a malicious code or accidently).) > Make Final Non-Final Public Static Fields > -- > > Key: GORA-433 > URL: https://issues.apache.org/jira/browse/GORA-433 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Minor > Fix For: 0.6.1 > > > Non-final public static fields can be changed by external classes (by a > malicious code or accidentally). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-432) Simplify if Statements
[ https://issues.apache.org/jira/browse/GORA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-432: --- Fix Version/s: 0.6.1 > Simplify if Statements > -- > > Key: GORA-432 > URL: https://issues.apache.org/jira/browse/GORA-432 > Project: Apache Gora > Issue Type: Improvement >Reporter: Furkan KAMACI >Priority: Trivial > Fix For: 0.6.1 > > > There are some _if_ statements which can be simplified to make code more > readable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-432) Simplify if Statements
Furkan KAMACI created GORA-432: -- Summary: Simplify if Statements Key: GORA-432 URL: https://issues.apache.org/jira/browse/GORA-432 Project: Apache Gora Issue Type: Improvement Reporter: Furkan KAMACI Priority: Trivial There are some _if_ statements which can be simplified to make code more readable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GORA-433) Make Final Non-Final Public Static Fields
Furkan KAMACI created GORA-433: -- Summary: Make Final Non-Final Public Static Fields Key: GORA-433 URL: https://issues.apache.org/jira/browse/GORA-433 Project: Apache Gora Issue Type: Improvement Reporter: Furkan KAMACI Priority: Minor Fix For: 0.6.1 Non-final public static fields can be changed by external classes (by a malicious code or accidently). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727340#comment-14727340
]
Furkan KAMACI commented on GORA-431:
Check here for previous e-mails: http://markmail.org/message/jj5afxbdffk5v4bx
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Priority: Minor
> Fix For: 0.6.1
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GORA-386) Gora Spark Backend Support
[ https://issues.apache.org/jira/browse/GORA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727287#comment-14727287 ] Furkan KAMACI commented on GORA-386: [~lewismc] did you make any modification before you run the tests? How did you test it? > Gora Spark Backend Support > -- > > Key: GORA-386 > URL: https://issues.apache.org/jira/browse/GORA-386 > Project: Apache Gora > Issue Type: New Feature > Components: gora-core >Reporter: Talat UYARER >Assignee: Furkan KAMACI > Labels: gsoc2015 > Fix For: 0.6.1 > > Attachments: connection_refused.txt > > > Now Gora supports Map Reduce Framework. With this umbrella issue we try to > develop Apache Spark Backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-431) reuseObjects is Not Used
[
https://issues.apache.org/jira/browse/GORA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furkan KAMACI updated GORA-431:
---
Description:
here is a method as:
{code}
public static void setIOSerializations(Configuration conf, boolean
reuseObjects)
{code}
at GoraMapReduceUtils.java
However, reuseObjects is never used at that method. On the other hand it is
always true at PersistentDeserializer.deserialize()
was:
here is a method as:
public static void setIOSerializations(Configuration conf, boolean
reuseObjects)
at GoraMapReduceUtils.java
However, reuseObjects is never used at that method.
> reuseObjects is Not Used
>
>
> Key: GORA-431
> URL: https://issues.apache.org/jira/browse/GORA-431
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-core
>Reporter: Furkan KAMACI
>Priority: Minor
> Fix For: 0.6.1
>
>
> here is a method as:
> {code}
> public static void setIOSerializations(Configuration conf, boolean
> reuseObjects)
> {code}
> at GoraMapReduceUtils.java
> However, reuseObjects is never used at that method. On the other hand it is
> always true at PersistentDeserializer.deserialize()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GORA-431) reuseObjects is Not Used
Furkan KAMACI created GORA-431: -- Summary: reuseObjects is Not Used Key: GORA-431 URL: https://issues.apache.org/jira/browse/GORA-431 Project: Apache Gora Issue Type: Bug Components: gora-core Reporter: Furkan KAMACI Priority: Minor Fix For: 0.6.1 here is a method as: public static void setIOSerializations(Configuration conf, boolean reuseObjects) at GoraMapReduceUtils.java However, reuseObjects is never used at that method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-386) Gora Spark Backend Support
[ https://issues.apache.org/jira/browse/GORA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715661#comment-14715661 ] Furkan KAMACI commented on GORA-386: Here is my repository for this issue: https://github.com/kamaci/gora Gora Spark Backend Support -- Key: GORA-386 URL: https://issues.apache.org/jira/browse/GORA-386 Project: Apache Gora Issue Type: New Feature Components: gora-core Reporter: Talat UYARER Assignee: Furkan KAMACI Labels: gsoc2015 Fix For: 0.7 Now Gora supports Map Reduce Framework. With this umbrella issue we try to develop Apache Spark Backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-386) Gora Spark Backend Support
[ https://issues.apache.org/jira/browse/GORA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715667#comment-14715667 ] Furkan KAMACI commented on GORA-386: I've ignored word count test at here: https://github.com/kamaci/gora/blob/master/gora-hbase/src/test/java/org/apache/gora/hbase/mapreduce/TestHBaseStoreWordCount.java#L65 due to the connection error it throws. I've attached full stack trace as connection_refused.txt Gora Spark Backend Support -- Key: GORA-386 URL: https://issues.apache.org/jira/browse/GORA-386 Project: Apache Gora Issue Type: New Feature Components: gora-core Reporter: Talat UYARER Assignee: Furkan KAMACI Labels: gsoc2015 Fix For: 0.7 Attachments: connection_refused.txt Now Gora supports Map Reduce Framework. With this umbrella issue we try to develop Apache Spark Backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GORA-386) Gora Spark Backend Support
[ https://issues.apache.org/jira/browse/GORA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-386: --- Attachment: connection_refused.txt Gora Spark Backend Support -- Key: GORA-386 URL: https://issues.apache.org/jira/browse/GORA-386 Project: Apache Gora Issue Type: New Feature Components: gora-core Reporter: Talat UYARER Assignee: Furkan KAMACI Labels: gsoc2015 Fix For: 0.7 Attachments: connection_refused.txt Now Gora supports Map Reduce Framework. With this umbrella issue we try to develop Apache Spark Backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-416) Error when populating data into Cassandra super column - InvalidRequestException(why:supercolumn parameter is not optional for super CF sc
[
https://issues.apache.org/jira/browse/GORA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550984#comment-14550984
]
Furkan KAMACI commented on GORA-416:
That's OK [~talat]!
Error when populating data into Cassandra super column -
InvalidRequestException(why:supercolumn parameter is not optional for super
CF sc
--
Key: GORA-416
URL: https://issues.apache.org/jira/browse/GORA-416
Project: Apache Gora
Issue Type: Bug
Components: gora-cassandra
Affects Versions: 0.6
Environment: Nutch 2.4-SNAPSHOT, Gora 0.6.1-SNAPSHOT, Hadoop 2.5.2,
Cassandra 2.0.7
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
Priority: Blocker
Fix For: 0.6.1
Attachments: GORA-416.patch
Error when populating data into Cassandra super column.
{code}
lmcgibbn@LMC-032857 /usr/local/2webgui/runtime/local(master) $ ./bin/nutch
fetch 1425410774-370456822
FetcherJob: starting at 2015-03-03 11:27:57
FetcherJob: batchId: 1425410774-370456822
FetcherJob: threads: 10
FetcherJob: parsing: false
FetcherJob: resuming: false
FetcherJob : timelimit set for : -1
2015-03-03 11:27:58.101 java[3267:1903] Unable to load realm info from
SCDynamicStore
Using queue mode : byHost
Fetcher: threads: 10
QueueFeeder finished: total 1 records. Hit by time limit :0
fetching http://nutch.apache.org/ (queue crawl delay=5000ms)
-finishing thread FetcherThread1, activeThreads=1
-finishing thread FetcherThread2, activeThreads=1
-finishing thread FetcherThread3, activeThreads=1
-finishing thread FetcherThread4, activeThreads=1
-finishing thread FetcherThread5, activeThreads=1
-finishing thread FetcherThread6, activeThreads=1
-finishing thread FetcherThread7, activeThreads=1
-finishing thread FetcherThread8, activeThreads=1
Fetcher: throughput threshold: -1
-finishing thread FetcherThread9, activeThreads=1
Fetcher: throughput threshold sequence: 5
-finishing thread FetcherThread0, activeThreads=0
0/0 spinwaiting/active, 1 pages, 0 errors, 0.2 0 pages/s, 82 82 kb/s, 0 URLs
in 0 queues
-activeThreads=0
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:supercolumn parameter is not optional for super
CF sc)
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:52)
at
me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:260)
at
me.prettyprint.cassandra.model.ExecutingKeyspace.doExecuteOperation(ExecutingKeyspace.java:113)
at
me.prettyprint.cassandra.model.MutatorImpl.execute(MutatorImpl.java:243)
at
me.prettyprint.cassandra.model.MutatorImpl.insert(MutatorImpl.java:69)
at
org.apache.gora.cassandra.store.HectorUtils.insertColumn(HectorUtils.java:46)
at
org.apache.gora.cassandra.store.CassandraClient.addColumn(CassandraClient.java:293)
at
org.apache.gora.cassandra.store.CassandraStore.addOrUpdateField(CassandraStore.java:512)
at
org.apache.gora.cassandra.store.CassandraStore.addOrUpdateField(CassandraStore.java:598)
at
org.apache.gora.cassandra.store.CassandraStore.flush(CassandraStore.java:316)
at
org.apache.gora.cassandra.store.CassandraStore.close(CassandraStore.java:160)
at
org.apache.gora.mapreduce.GoraRecordWriter.close(GoraRecordWriter.java:56)
at
org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.close(ReduceTask.java:550)
at
org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:629)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:389)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$ReduceTaskRunnable.run(LocalJobRunner.java:319)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: InvalidRequestException(why:supercolumn parameter is not optional
for super CF sc)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result$batch_mutate_resultStandardScheme.read(Cassandra.java:28082)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result$batch_mutate_resultStandardScheme.read(Cassandra.java:28068)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:28002)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
[jira] [Commented] (GORA-416) Error when populating data into Cassandra super column - InvalidRequestException(why:supercolumn parameter is not optional for super CF sc
[
https://issues.apache.org/jira/browse/GORA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550859#comment-14550859
]
Furkan KAMACI commented on GORA-416:
[~lewismc] Sure! I'll work on it.
Error when populating data into Cassandra super column -
InvalidRequestException(why:supercolumn parameter is not optional for super
CF sc
--
Key: GORA-416
URL: https://issues.apache.org/jira/browse/GORA-416
Project: Apache Gora
Issue Type: Bug
Components: gora-cassandra
Affects Versions: 0.6
Environment: Nutch 2.4-SNAPSHOT, Gora 0.6.1-SNAPSHOT, Hadoop 2.5.2,
Cassandra 2.0.7
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
Priority: Blocker
Fix For: 0.6.1
Attachments: GORA-416.patch
Error when populating data into Cassandra super column.
{code}
lmcgibbn@LMC-032857 /usr/local/2webgui/runtime/local(master) $ ./bin/nutch
fetch 1425410774-370456822
FetcherJob: starting at 2015-03-03 11:27:57
FetcherJob: batchId: 1425410774-370456822
FetcherJob: threads: 10
FetcherJob: parsing: false
FetcherJob: resuming: false
FetcherJob : timelimit set for : -1
2015-03-03 11:27:58.101 java[3267:1903] Unable to load realm info from
SCDynamicStore
Using queue mode : byHost
Fetcher: threads: 10
QueueFeeder finished: total 1 records. Hit by time limit :0
fetching http://nutch.apache.org/ (queue crawl delay=5000ms)
-finishing thread FetcherThread1, activeThreads=1
-finishing thread FetcherThread2, activeThreads=1
-finishing thread FetcherThread3, activeThreads=1
-finishing thread FetcherThread4, activeThreads=1
-finishing thread FetcherThread5, activeThreads=1
-finishing thread FetcherThread6, activeThreads=1
-finishing thread FetcherThread7, activeThreads=1
-finishing thread FetcherThread8, activeThreads=1
Fetcher: throughput threshold: -1
-finishing thread FetcherThread9, activeThreads=1
Fetcher: throughput threshold sequence: 5
-finishing thread FetcherThread0, activeThreads=0
0/0 spinwaiting/active, 1 pages, 0 errors, 0.2 0 pages/s, 82 82 kb/s, 0 URLs
in 0 queues
-activeThreads=0
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:supercolumn parameter is not optional for super
CF sc)
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:52)
at
me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:260)
at
me.prettyprint.cassandra.model.ExecutingKeyspace.doExecuteOperation(ExecutingKeyspace.java:113)
at
me.prettyprint.cassandra.model.MutatorImpl.execute(MutatorImpl.java:243)
at
me.prettyprint.cassandra.model.MutatorImpl.insert(MutatorImpl.java:69)
at
org.apache.gora.cassandra.store.HectorUtils.insertColumn(HectorUtils.java:46)
at
org.apache.gora.cassandra.store.CassandraClient.addColumn(CassandraClient.java:293)
at
org.apache.gora.cassandra.store.CassandraStore.addOrUpdateField(CassandraStore.java:512)
at
org.apache.gora.cassandra.store.CassandraStore.addOrUpdateField(CassandraStore.java:598)
at
org.apache.gora.cassandra.store.CassandraStore.flush(CassandraStore.java:316)
at
org.apache.gora.cassandra.store.CassandraStore.close(CassandraStore.java:160)
at
org.apache.gora.mapreduce.GoraRecordWriter.close(GoraRecordWriter.java:56)
at
org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.close(ReduceTask.java:550)
at
org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:629)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:389)
at
org.apache.hadoop.mapred.LocalJobRunner$Job$ReduceTaskRunnable.run(LocalJobRunner.java:319)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: InvalidRequestException(why:supercolumn parameter is not optional
for super CF sc)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result$batch_mutate_resultStandardScheme.read(Cassandra.java:28082)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result$batch_mutate_resultStandardScheme.read(Cassandra.java:28068)
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:28002)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
[jira] [Updated] (GORA-262) Add support for HTTPClient authentication in gora-solr
[ https://issues.apache.org/jira/browse/GORA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Furkan KAMACI updated GORA-262: --- Attachment: GORA-262.patch Add support for HTTPClient authentication in gora-solr Key: GORA-262 URL: https://issues.apache.org/jira/browse/GORA-262 Project: Apache Gora Issue Type: Improvement Components: gora-solr Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Fix For: 0.7 Attachments: GORA-262.patch This is the next logical progression once GORA-260 is addressed. Security is always an issue when writing into Solr. This issue should introduce exactly that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-262) Add support for HTTPClient authentication in gora-solr
[ https://issues.apache.org/jira/browse/GORA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14372417#comment-14372417 ] Furkan KAMACI commented on GORA-262: There is no way to test secure HTTPClient within Solr test package with JettySolrRunner (without using reflection). It is not tested at Apache Solr project too (it can be tested via external Solr war). On the other hand ConcurrentUpdateSolrServer does not have a public accessor to get HTTPClient. I have to test it with Nutch approach before adding to patch. I'll create documentation for this patch. Add support for HTTPClient authentication in gora-solr Key: GORA-262 URL: https://issues.apache.org/jira/browse/GORA-262 Project: Apache Gora Issue Type: Improvement Components: gora-solr Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Fix For: 0.7 Attachments: GORA-262.patch This is the next logical progression once GORA-260 is addressed. Security is always an issue when writing into Solr. This issue should introduce exactly that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-386) Gora Spark Backend Support
[ https://issues.apache.org/jira/browse/GORA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363102#comment-14363102 ] Furkan KAMACI commented on GORA-386: [~talat] I would like to apply GSoC for this issue. I'll share my application proposal with you. Gora Spark Backend Support -- Key: GORA-386 URL: https://issues.apache.org/jira/browse/GORA-386 Project: Apache Gora Issue Type: New Feature Components: gora-core Reporter: Talat UYARER Labels: gsoc2015 Fix For: 0.7 Now Gora supports Map Reduce Framework. With this umbrella issue we try to develop Apache Spark Backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GORA-262) Add support for HTTPClient authentication in gora-solr
[ https://issues.apache.org/jira/browse/GORA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360991#comment-14360991 ] Furkan KAMACI commented on GORA-262: [~lewismc] what kind of authentication is mentioned at this issue? Setting up credentials on SolrServer/HttpClient level ([Security-Solrj|http://wiki.apache.org/solr/SolrSecurity#SolrJ]) or a more generic way of security: [SOLR-4470|https://issues.apache.org/jira/browse/SOLR-4470] If you can clarify it I can implement this issue. Add support for HTTPClient authentication in gora-solr Key: GORA-262 URL: https://issues.apache.org/jira/browse/GORA-262 Project: Apache Gora Issue Type: Improvement Components: gora-solr Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Fix For: 0.7 This is the next logical progression once GORA-260 is addressed. Security is always an issue when writing into Solr. This issue should introduce exactly that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
