Weird, it looks like somehow my object's close method being called twice (I
guess maybe I did instance copy). I managed to find a way to fix it, and no
longer seeing that exception. Thanks again.
--
View this message in context:
http://apache-accumulo.1065345.n5.nabble.com/c-thrift-client-crash
I think one of the prior problems was JIRA karma and GPG keys (SVN commit
access), but I can't recall. Hopefully you can get those barriers knocked
out in short order.
On Tue, Apr 26, 2016, 14:52 Josh Elser wrote:
> Thanks, Dave.
>
> For those not following along on dev@commons.a.o -- I do not s
Github user dhutchis commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61145524
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache So
Thanks, Dave.
For those not following along on dev@commons.a.o -- I do not see any
roadblocks which would completely negate my ability to act as release
manager. I believe history can show us that the community there is not
capable of making a release of commons-vfs (as it's been 4+ years). As
Yeah, for building a real security-tagging system, the labeling that
Accumulo does is only one "piece of the puzzle". For example, you would
likely have external systems that define the authorizations that your
users would have. The authorization and labeling that Accumulo does is a
hard piece
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61133856
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache S
Github user ShawnWalker commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61128227
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache
I'm sorry, I'm not terribly familiar to the proxy as I was making the RPC
calls in my client. I did not come across that exception. Do you know if
that is your local client or an exception generated in the proxy and
returned to you?
On Tue, Apr 26, 2016 at 11:30 AM z11373 wrote:
> Marc, have you
Hi Again guys,
Thanks Josh & Dylan for the suggestions, here are our updates regarding the
data ingestion & visibility issues.
We've tried several workaround and used some of the suggestions offered for
our particular issues, and we've decided for the data ingestion to use the
bulk ingestion as t
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61119582
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache S
Josh,
I see that you have made progress. Let me know how I can help get this
released.
Dave
- Original Message -
From: "Josh Elser"
To: dev@accumulo.apache.org
Sent: Monday, April 25, 2016 2:57:45 PM
Subject: Re: On the future of our commons-vfs2 dynamic classloading
implementat
Github user ShawnWalker commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61118538
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache
Marc, have you seen this exception before?
The write was successful, the code closes the writer and connection when the
object is destroyed, which I believe throwing this exception somehow.
terminate called after throwing an instance of
'apache::thrift::transport::TTransportException'
what(): C
Shawn -- you win the gold star for the day from me. This is exactly the
fear I had, but had an inability put it into words correctly :)
Valerio/chutium -- The common scenario I have run into is that
processing jobs (your use of Spark) can read data from S3 and ingest it
into the database (Accu
RFiles (Accumulo's primary data storage mechanism) are immutable and lazily
deleted (by the GC process). Read-after-write consistency for new files
should be sufficient for them. I suspect the only real gotchas would be:
NativeS3FileSystem has a 5G max file size, and NativeS3FileSystem is very
sl
Hi Josh,
about the guarantees of s3, according to this doc from amazon:
https://docs.aws.amazon.com/ElasticMapReduce/latest/ReleaseGuide/emr-plan-consistent-view.html
> Amazon S3 buckets in xxx, xxx regions provide read-after-write consistency
> for put requests of new objects and eventual consis
Github user dhutchis commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/96#discussion_r61037738
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/SyncingTabletLocator.java
---
@@ -0,0 +1,108 @@
+/*
+ * Licensed to the Apache So
17 matches
Mail list logo
