[
https://issues.apache.org/jira/browse/GORA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13545732#comment-13545732
]
Ferdy Galema commented on GORA-195:
---
Hi,
I agree that we should either
a) Throw
[
https://issues.apache.org/jira/browse/GORA-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500874#comment-13500874
]
Ferdy Galema commented on GORA-187:
---
Hi,
Could you clarify a bit? What is the current
[
https://issues.apache.org/jira/browse/GORA-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema closed GORA-178.
-
Resolution: Fixed
Committed @ trunk ref 1409139.
HBase fix ivy.xml to use the correct
[
https://issues.apache.org/jira/browse/GORA-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13494873#comment-13494873
]
Ferdy Galema commented on GORA-178:
---
I wasn't sure, but going for pure Maven is fine
[
https://issues.apache.org/jira/browse/GORA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13450518#comment-13450518
]
Ferdy Galema commented on GORA-103:
---
Thanks for the quick reply. Note that you did
[
https://issues.apache.org/jira/browse/GORA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13450518#comment-13450518
]
Ferdy Galema edited comment on GORA-103 at 9/7/12 10:02 PM
[
https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444760#comment-13444760
]
Ferdy Galema edited comment on GORA-119 at 8/30/12 6:35 PM:
Hi
[
https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444760#comment-13444760
]
Ferdy Galema commented on GORA-119:
---
Hi Renato,
Unfortunately it is not yet in trunk. I
[
https://issues.apache.org/jira/browse/GORA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439653#comment-13439653
]
Ferdy Galema commented on GORA-89:
--
Hi Lewis,
Totally forgot about this issue. I am willing
Hi Ed,
I agree that the overwritten state should be introduced into Gora. For
example, from an API perspective it is currently difficult to do the
following: Clear a map and put some new entries in them. A way to do this
now is to make sure that a client inputs the entire map so that it
+1.
FYI: I downloaded the sources zip, build all modules succesfully (mvn clean
install -DskipTests) and used the core and hbase artifact succesfully in an
client deployment. I ran a testcrawl with Nutch2.x.
On Fri, Jul 27, 2012 at 12:12 PM, Kazuomi Kashii kazu...@kashii.net wrote:
[X] +1
[
https://issues.apache.org/jira/browse/GORA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424915#comment-13424915
]
Ferdy Galema commented on GORA-162:
---
+1. Agree with 2 space indents. Of all formatting
Hi,
You are correct about HBase. HTable indeed uses the user thread to maintain
a buffer for Put operations. Delete operations are not buffered,
unfortunately. That's what makes deletes tremendously slow. There is a
batchdelete, but there are still some issues that makes it slower than a
Hi,
Does 0.2.x mean that is not created from trunk but from the 0.2 branch
(that is created from the 0.2 tag)? If this is the case, do we have to
merge specific changes from trunk? Or what is exactly the idea?
Ferdy
On Mon, Jul 23, 2012 at 11:12 PM, Kazuomi Kashii kazu...@kashii.net wrote:
+1
Ah ok. So let's see if I got this right:
Even though we might be calling it 0.2.1, we can still use trunk for the
release. So the version number is just a semantic to indicate if it is a
minor or major release. (The latter typically introducing major features or
incompatibilities). 0.2.1 does not
[
https://issues.apache.org/jira/browse/GORA-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419076#comment-13419076
]
Ferdy Galema commented on GORA-155:
---
True. the delete(T obj) should be implemented.
Note
[
https://issues.apache.org/jira/browse/GORA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419248#comment-13419248
]
Ferdy Galema commented on GORA-94:
--
Wow that is HUGE patch. I tried to apply on trunk head
[
https://issues.apache.org/jira/browse/GORA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418159#comment-13418159
]
Ferdy Galema commented on GORA-94:
--
Ok.
About the CharSequence and ByteBuffer types
[
https://issues.apache.org/jira/browse/GORA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema reopened GORA-150:
---
Assignee: Ferdy Galema
I noticed there is something wrong with this implementation. (It does
[
https://issues.apache.org/jira/browse/GORA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema resolved GORA-150.
---
Resolution: Fixed
reverted, and recommited patch v2.
Introduce Configuration
[
https://issues.apache.org/jira/browse/GORA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-150:
--
Attachment: GORA-150-v2.patch
Introduce Configuration property schema.prefix
Ferdy Galema created GORA-150:
-
Summary: Introduce Configuration property preferred.schema.name
Key: GORA-150
URL: https://issues.apache.org/jira/browse/GORA-150
Project: Apache Gora
Issue Type
[
https://issues.apache.org/jira/browse/GORA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema closed GORA-150.
-
Resolution: Fixed
Tested and committed.
Introduce Configuration property
[
https://issues.apache.org/jira/browse/GORA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-150:
--
Attachment: GORA-150.patch
Introduce Configuration property preferred.schema.name
[
https://issues.apache.org/jira/browse/GORA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13417096#comment-13417096
]
Ferdy Galema commented on GORA-126:
---
I now realize that this issue tries to change too
[
https://issues.apache.org/jira/browse/GORA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13417763#comment-13417763
]
Ferdy Galema edited comment on GORA-94 at 7/18/12 10:31 PM:
Hi
Ferdy Galema created GORA-146:
-
Summary: HBaseStore does not properly set endkey
Key: GORA-146
URL: https://issues.apache.org/jira/browse/GORA-146
Project: Apache Gora
Issue Type: Bug
Welcome!
On Mon, Jun 11, 2012 at 6:39 PM, Kazuomi Kashii kazu...@kashii.net wrote:
I am Kazuomi Kashii, and my profile at LinkedIn is:
http://www.linkedin.com/in/kazuomikashii
I introduced Cassandra to our indexing platform, and developed my own
client library,
but wanted to migrate it to
Hi,
It is indeed a bit odd that state is both exposed by the StateManager and
the Persistent object itself, now that you mention it. Also it seems that
some Persistent uses completely bypass the StateManager. For example see
WebPage in gora-core/src/examples, method getOutlinks(). This method
[
https://issues.apache.org/jira/browse/GORA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-128:
--
Attachment: (was: GORA-128.patch)
HBaseStore should be configurable to work with different
[
https://issues.apache.org/jira/browse/GORA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281619#comment-13281619
]
Ferdy Galema commented on GORA-128:
---
My previously suggested patch is not necessary
[
https://issues.apache.org/jira/browse/GORA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271165#comment-13271165
]
Ferdy Galema commented on GORA-127:
---
Patch looks good. +1
Result objects
[
https://issues.apache.org/jira/browse/GORA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271226#comment-13271226
]
Ferdy Galema commented on GORA-128:
---
Hi Raf,
This was something I already had running
[
https://issues.apache.org/jira/browse/GORA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-128:
--
Attachment: GORA-128.patch
HBaseStore should be configurable to work with different qurom other
Ferdy Galema created GORA-129:
-
Summary: redundant conf field in HBaseStore
Key: GORA-129
URL: https://issues.apache.org/jira/browse/GORA-129
Project: Apache Gora
Issue Type: Bug
[
https://issues.apache.org/jira/browse/GORA-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema closed GORA-129.
-
Resolution: Fixed
committed
redundant conf field in HBaseStore
FYI: I committed this change to ease Eclipse integration with the IvyDE
plugin. (Just like I did to Nutch some time ago). Even though I know Maven
is the official supported build tool for Gora, I still have some uses with
the Ivy support.
Ferdy
On Tue, May 8, 2012 at 1:28 PM, fe...@apache.org
Thanks Lewis, report is great.
On Tue, May 8, 2012 at 1:42 PM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
Hi Guys,
I've been a tad busy as of late and usually pass on this report prior
to sending it off to board but didn't get it produced in quite as much
time as I would have
[
https://issues.apache.org/jira/browse/GORA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema resolved GORA-118.
---
Resolution: Won't Fix
Ok. Please note that deletes are currently still pretty inefficient to process
Hi,
While Lewis and I were discussing over NUTCH-1205, we identified
the Properties object as the major source of trouble/confusion when
configuring datastores. First and foremost, it's makes no sense that we
have 2 ways to configure a store, namely via Configuration and Properties.
Besides this
[
https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13262804#comment-13262804
]
Ferdy Galema commented on GORA-119:
---
Yeah therefore it is very important to design
[
https://issues.apache.org/jira/browse/GORA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13262814#comment-13262814
]
Ferdy Galema commented on GORA-119:
---
(Not to undermine your comments about it becoming
[
https://issues.apache.org/jira/browse/GORA-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257287#comment-13257287
]
Ferdy Galema commented on GORA-120:
---
Hey Lewis,
Thanks for noticing. GORA-33 exactly
[
https://issues.apache.org/jira/browse/GORA-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema closed GORA-120.
-
Resolution: Fixed
Dirty fields are not correctly applied after serialization and map clearance
[
https://issues.apache.org/jira/browse/GORA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256416#comment-13256416
]
Ferdy Galema commented on GORA-118:
---
Is this not simply achieved by setting flush
Issue Type: Bug
Reporter: Ferdy Galema
Fix For: 0.3
Dirty fields are not correctly applied in these situations:
-All entries in the map are incorrectly made dirty when a Persistent is
deserialized.
-Also, due to a separate bug all non-map entries that are deserialized
[
https://issues.apache.org/jira/browse/GORA-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-120:
--
Attachment: GORA-120-v1.txt
Dirty fields are not correctly applied after serialization and map
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247248#comment-13247248
]
Ferdy Galema commented on GORA-76:
--
Hi Lewis,
Although it's true that there is the MXBean
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247290#comment-13247290
]
Ferdy Galema commented on GORA-76:
--
You sure you included all in the patch? I'm getting
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247334#comment-13247334
]
Ferdy Galema commented on GORA-76:
--
I'm fine with committing, that way we will find out
Hi Eric,
You are right on both issues. There should be an option to turn of
autoflushing when creating the HBaseStore. I think the gora properties file
is a nice place for this option.
And indeed a flush should flush all threadlocal instances. I implemented
the threadlocal code for the
Hi Lewis,
I'm not sure what the problem with your Gora build is, but I hope this
helps somewhat: Generally I don't have the problem of hanging builds when
running mvn clean test. And I just ran the tests in head and there does
not seem to be a problem. Also test run without failures.
Ferdy.
On
[
https://issues.apache.org/jira/browse/GORA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema closed GORA-105.
-
Resolution: Fixed
committed.
DataStoreFactory does not properly support multiple stores
[
https://issues.apache.org/jira/browse/GORA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-105:
--
Attachment: GORA-105-v2.patch
Done. Annotating the various creator methods was... inspiring. To reduce
Components: schema, storage
Reporter: Ferdy Galema
Priority: Blocker
Fix For: 0.2
DataStoreFactory has a single, static properties field. This is completely
unacceptable, because that way when multiple stores are instantiated in the
same JVM, the last store instance
[
https://issues.apache.org/jira/browse/GORA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-105:
--
Attachment: GORA-105.patch
DataStoreFactory does not properly support multiple stores
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated GORA-76:
-
Attachment: GORA-76.patch
Upgrade to Hadoop 1.0.0
---
Key: GORA
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13224701#comment-13224701
]
Ferdy Galema commented on GORA-76:
--
Well o.a.g.mapreduce.DataStoreMapReduceTestBase[0
: Ferdy Galema
This issue is for tracking a possible Hypertable datastore implementation.
Hypertable is a HBase-like column-oriented datastore.
http://www.hypertable.com/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
We could simply change the 'build' references in the gora script to the
appropiate 'target' folders?
On Fri, Mar 2, 2012 at 8:15 PM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
This is to do with the last couple lines of the gora bash script.
It specifies that we should be adding
Hi Lewis,
Thanks for the hint. I ran a local build (mvn clean install) and it
succeeded. It is strange why suddenly the ci failed because my last commit
did not change any build or maven configuration at all. Just some source
files..
On Thu, Mar 1, 2012 at 5:20 PM, Lewis John Mcgibbney
[
https://issues.apache.org/jira/browse/GORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13218139#comment-13218139
]
Ferdy Galema commented on GORA-76:
--
Ok I will try to use the same packages for Gora
[
https://issues.apache.org/jira/browse/GORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210973#comment-13210973
]
Ferdy Galema commented on GORA-84:
--
Good point. I haven't upgraded it yet in Nutchgora
63 matches
Mail list logo
