[jira] [Commented] (GORA-119) implement a filter enabled scan in gora
[ https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000971#comment-14000971 ] Hudson commented on GORA-119: - FAILURE: Integrated in Nutch-nutchgora #1015 (See [https://builds.apache.org/job/Nutch-nutchgora/1015/]) NUTCH-1674 Use batchId filter to enable scan (GORA-119) for Fetch,Parse,Update,Index (Tien Nguyen Manh and Alparslan Avcı via jnioche) (jnioche: http://svn.apache.org/viewvc/nutch/branches/2.x/?view=rev&rev=1594813) * /nutch/branches/2.x/CHANGES.txt * /nutch/branches/2.x/src/java/org/apache/nutch/crawl/DbUpdateMapper.java * /nutch/branches/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java * /nutch/branches/2.x/src/java/org/apache/nutch/fetcher/FetcherJob.java * /nutch/branches/2.x/src/java/org/apache/nutch/indexer/IndexingJob.java * /nutch/branches/2.x/src/java/org/apache/nutch/parse/ParserJob.java * /nutch/branches/2.x/src/java/org/apache/nutch/storage/Mark.java * /nutch/branches/2.x/src/java/org/apache/nutch/storage/StorageUtils.java > implement a filter enabled scan in gora > --- > > Key: GORA-119 > URL: https://issues.apache.org/jira/browse/GORA-119 > Project: Apache Gora > Issue Type: Improvement >Affects Versions: 0.2 > Environment: gora hbase gora-core gora-hbase >Reporter: raf shin > Labels: filter, gora-core, gora-hbase, scan > Fix For: 0.4 > > Attachments: GORA-119-v1.txt, GORA-119v2.patch, GORA-119v3.patch, > GORA-119v3_94port.patch, gora-119-v1.1.patch, gora-119_v2.patch > > > it'll be very of help to implement a filtered scan to reduce the time of scan > in gora-core and gora-hbase components. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000932#comment-14000932 ] Lewis John McGibbney commented on GORA-277: --- This is excellent. We would just host it in the trunk codebase I would imagine or alternatively we could bring the code in to a /plugins directory in our SCM. [~hsaputra] wdyt? What have you done before with plugins? > Create gora-maven-plugin > > > Key: GORA-277 > URL: https://issues.apache.org/jira/browse/GORA-277 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler >Reporter: Lewis John McGibbney > Fix For: 0.5 > > > Recently the motivation for this one came when I used the avro-maven-plugin > but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes > using the GoraCompiler a piece of cake and really lowers the barrier to > generating Gora compliant Java beans. > Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000904#comment-14000904 ] Damien Raude-Morvan commented on GORA-277: -- Yes, we could like to contribute this to Apache ? You to you want to integrate this patch ? Is there a "contrib" module where we can host a "non-maven" project like this ? > Create gora-maven-plugin > > > Key: GORA-277 > URL: https://issues.apache.org/jira/browse/GORA-277 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler >Reporter: Lewis John McGibbney > Fix For: 0.5 > > > Recently the motivation for this one came when I used the avro-maven-plugin > but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes > using the GoraCompiler a piece of cake and really lowers the barrier to > generating Gora compliant Java beans. > Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (GORA-277) Create gora-maven-plugin
[ https://issues.apache.org/jira/browse/GORA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000904#comment-14000904 ] Damien Raude-Morvan edited comment on GORA-277 at 5/17/14 10:18 PM: Yes, we could like to contribute this to Apache ! You to you want to integrate this patch ? Is there some kind of "contrib" module where we can host a "non-maven" project like this ? was (Author: drazzib): Yes, we could like to contribute this to Apache ? You to you want to integrate this patch ? Is there a "contrib" module where we can host a "non-maven" project like this ? > Create gora-maven-plugin > > > Key: GORA-277 > URL: https://issues.apache.org/jira/browse/GORA-277 > Project: Apache Gora > Issue Type: Improvement > Components: gora-compiler >Reporter: Lewis John McGibbney > Fix For: 0.5 > > > Recently the motivation for this one came when I used the avro-maven-plugin > but IIRC this was originally proposed by [~ekohlwey] some time ago. It makes > using the GoraCompiler a piece of cake and really lowers the barrier to > generating Gora compliant Java beans. > Hopefully we can write this for the 0.5 development drive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000903#comment-14000903 ] Damien Raude-Morvan commented on GORA-199: -- Hi [~lewismc], * I've updated version in GoraMongodbTestDriver to use latest PRODUCTION release * I've removed reference to Nutch stuff for my branch * Could you please provide a template for code formating (for Eclipse or IntelliJ IDEA maybe ?) * TestMongoStore: references to StateManager are in comments but yeah, I need to work a bit on this one to update it for trunk > Support MongoDB in GORA > --- > > Key: GORA-199 > URL: https://issues.apache.org/jira/browse/GORA-199 > Project: Apache Gora > Issue Type: New Feature > Components: storage >Affects Versions: 0.2.1 >Reporter: Fabien Poulard >Assignee: Damien Raude-Morvan >Priority: Minor > Labels: contrib, patch > Fix For: 0.5 > > Attachments: GORA-119-trunk.patch, GORA-199.patch, GORA-199v2.patch, > GORA-199v3.patch, gora-mongodb-src.tar.gz, > org.apache.gora.mongodb.store.TestMongoStore.txt > > > Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [VOTE] Move Gora Source to Apache Git
Hi, 2014-05-15 19:44 GMT+02:00 Lewis John Mcgibbney : > > Please VOTE for the above, the VOTE will be open for at least 72 hours. > Thank you all very much. > Lewis > > [X] +1 Lets move to Git > [ ] +0/-0 Don't care > [ ] -1 I don't want to move to Git (please provide reasoning) > As I've already said, +1 for Git migration ! -- Damien
[jira] [Commented] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000871#comment-14000871 ] Lewis John McGibbney commented on GORA-199: --- Great [~talat] some comments * .version(Version.Main.V2_6) in GoraMongodbTestDriver should be upraded * There are many references to Nutch stuff... we should not have this... this was explained in the above conversation * Code formatting is not correct. * TestMongoStore needs more work. There are references to StateManager!!! Also I doubt thus patch will pass tests... we need to fix that if we want to commit it prior to UNION and filter support. I'll not work on these issues this weekend as I have other stuff to do (also I'm updating the Gora site) but will work on them next week. Thanks for updating the patch. > Support MongoDB in GORA > --- > > Key: GORA-199 > URL: https://issues.apache.org/jira/browse/GORA-199 > Project: Apache Gora > Issue Type: New Feature > Components: storage >Affects Versions: 0.2.1 >Reporter: Fabien Poulard >Assignee: Damien Raude-Morvan >Priority: Minor > Labels: contrib, patch > Fix For: 0.5 > > Attachments: GORA-119-trunk.patch, GORA-199.patch, GORA-199v2.patch, > GORA-199v3.patch, gora-mongodb-src.tar.gz, > org.apache.gora.mongodb.store.TestMongoStore.txt > > > Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [VOTE] Move Gora Source to Apache Git
+1 Working with Git is very easy. 2014-05-17 21:37 GMT+03:00 Renato Marroquín Mogrovejo : > +1 > On May 17, 2014 6:05 PM, "Alfonso Nishikawa" > wrote: > >> +1 >> -- Talat UYARER Websitesi: http://talat.uyarer.com Twitter: http://twitter.com/talatuyarer Linkedin: http://tr.linkedin.com/pub/talat-uyarer/10/142/304
[jira] [Updated] (GORA-199) Support MongoDB in GORA
[ https://issues.apache.org/jira/browse/GORA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Talat UYARER updated GORA-199: -- Attachment: GORA-119-trunk.patch Hi All, I create a patch for our trunk. Now It can compile. But I don't work for Union and Filter support. This patch generated for migrating [~drazzib]'s work to our trunk. [~drazzib], I have time at Sunday, Can I work about Union and filter support ? > Support MongoDB in GORA > --- > > Key: GORA-199 > URL: https://issues.apache.org/jira/browse/GORA-199 > Project: Apache Gora > Issue Type: New Feature > Components: storage >Affects Versions: 0.2.1 >Reporter: Fabien Poulard >Assignee: Damien Raude-Morvan >Priority: Minor > Labels: contrib, patch > Fix For: 0.5 > > Attachments: GORA-119-trunk.patch, GORA-199.patch, GORA-199v2.patch, > GORA-199v3.patch, gora-mongodb-src.tar.gz, > org.apache.gora.mongodb.store.TestMongoStore.txt > > > Support 10gen MongoDB datastore in GORA. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-328) Change and document default TTL value in gora-cassandra
[ https://issues.apache.org/jira/browse/GORA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000849#comment-14000849 ] Lewis John McGibbney commented on GORA-328: --- Default is 60 seconds. This is too low and a higher threshold needs to be set. Patch coming up. > Change and document default TTL value in gora-cassandra > --- > > Key: GORA-328 > URL: https://issues.apache.org/jira/browse/GORA-328 > Project: Apache Gora > Issue Type: Bug > Components: gora-cassandra >Affects Versions: 0.4 >Reporter: Lewis John McGibbney >Priority: Critical > Fix For: 0.5 > > > Adding TTLs (GORA-154) is a big move forward (thanks [~renato2099]) :) > In an scenario however where no TTL value is included, logging becomes very > verbose and a default value of 60 is set. 60 whats? > We can fix this easily and should also document it on the gora-cassandra > documentation. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GORA-167) Make Cassandra keyspace consistency configurable within gora.properties
[ https://issues.apache.org/jira/browse/GORA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000851#comment-14000851 ] Lewis John McGibbney commented on GORA-167: --- This did not make it in to trunk a the backport of code from GORA-94 killed it off. We should port it to trunk. > Make Cassandra keyspace consistency configurable within gora.properties > --- > > Key: GORA-167 > URL: https://issues.apache.org/jira/browse/GORA-167 > Project: Apache Gora > Issue Type: Improvement > Components: gora-cassandra >Affects Versions: 0.2.1 >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Minor > Fix For: 0.5 > > Attachments: GORA-167.patch, GORA-167v2.patch, GORA-167v3.patch, > GORA-167v4.patch, GORA-167v5.patch > > > Current in CassandraClient#checkKeyspace() consistency is hard coded such > that consistency level is .ONE which permits consistency to wait until one > replica has responded. This could be improved to enable users to specify > other consistency profiles e.g. > ANY: Wait until some replica has responded. > ONE: Wait until one replica has responded. > TWO: Wait until two replicas have responded. > THREE: Wait until three replicas have responded. > LOCAL_QUORUM: Wait for quorum on the datacenter the connection was > stablished. > EACH_QUORUM: Wait for quorum on each datacenter. > QUORUM: Wait for a quorum of replicas (no matter which datacenter). > ALL: Blocks for all the replicas before returning to the client. > Configuration should be made available through gora.properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (GORA-328) Change and document default TTL value in gora-cassandra
[ https://issues.apache.org/jira/browse/GORA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney reassigned GORA-328: - Assignee: Lewis John McGibbney > Change and document default TTL value in gora-cassandra > --- > > Key: GORA-328 > URL: https://issues.apache.org/jira/browse/GORA-328 > Project: Apache Gora > Issue Type: Bug > Components: gora-cassandra >Affects Versions: 0.4 >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Critical > Fix For: 0.5 > > > Adding TTLs (GORA-154) is a big move forward (thanks [~renato2099]) :) > In an scenario however where no TTL value is included, logging becomes very > verbose and a default value of 60 is set. 60 whats? > We can fix this easily and should also document it on the gora-cassandra > documentation. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [VOTE] Move Gora Source to Apache Git
+1 On May 17, 2014 6:05 PM, "Alfonso Nishikawa" wrote: > +1 >
Re: GSoC
Hi All, I want a few things to clarify from you. I have understood both the Gora and Hazelcast Separately. I Have tried out tutorials and codes for both separately. But, I wanted to know exactly where the Hazelcast fits inside the Gora ? what you expect from this module to the Gora ? what role Hazelcast should play inside the Gora? I have included all the use cases of Hazelcast in my proposal. At that time, I didn't have much understanding on Gora. So, I included all the use cases Hazelcast provide. Now, I need to know which of those use cases community prefers to have in this module ? Thanks, Ahsan On Tue, May 13, 2014 at 3:18 PM, Renato Marroquín Mogrovejo < renatoj.marroq...@gmail.com> wrote: > Hi Ahsan, > > No problem at all, but please let's try to synchronize a little bit more > often so we don't have too many risks for the project. Let's try to talk at > the end of the week at some time to asses how we are doing. > Take care man. > > > Renato M. > > > 2014-05-10 5:29 GMT+02:00 ahsan shamsudeen : > > Hi Renato, >> >> sorry for the delayed response. I went on a trip over the last week and >> away from my computer. >> >> I am currently following the tutorials provided by the community members. >> Btw, Now, I could able to understand the Gora framework and in a position >> to get start with the project. >> >> Thank you very much . >> >> >> On Thu, May 8, 2014 at 2:54 PM, Renato Marroquín Mogrovejo < >> renatoj.marroq...@gmail.com> wrote: >> >>> Hi Ahsan, >>> >>> I haven't heard from you in a couple of days. How are things going man? >>> Are you being able to do any progress? Would you like to discuss anything? >>> Just ping me if you have any doubts or thoughts. >>> >>> >>> Renato M. >>> >> >> >
Re: [VOTE] Move Gora Source to Apache Git
+1
