|Re: [geomesa-users] Using the Java API - NoClassDefFoundError|
log4j:WARN No appenders could be found for logger (org.apache.hadoop.conf.Configuration.deprecation).I've attached the Java file here. It is basically identical to the documentation, createFeatureType() succeeds, but createFeature() throws the above exception. One thing I noticed is that the documentation refers to "IndexEntryType.getTypeSpec()", which is appended to the Feature Schema, but that does not appear to be provided by GeoMesa currently. The only reference to it in the current codebase is in a unit test. I'm not sure if my errors are caused because my feature schema is missing some essential types.
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2014-05-22 19:21:58.181 java[2387:1903] Unable to load realm info from SCDynamicStore
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: org.geotools.feature.SchemaException: Error decoding srs: 4326
... 5 more
Caused by: org.opengis.referencing.NoSuchAuthorityCodeException: No code "EPSG:4326" from authority "EPSG" found for object of type "EngineeringCRS".
... 9 more
You are welcome, I'm glad that did it.
You need the geomesa-core artifact.
We have recently changed the way we support accumulo version and the name of the artifact for accumulo1.5 is:
On 05/21/2014 07:47 PM, Connor Manning wrote:
Hi Hunter, thanks for that - explicitly including Hadoop solved that issue.
I have a further question now - previously my project was manually
managed without Maven and I've since converted it (due to run-time
ClassDefNotFound errors that were likely caused by improperly managed
So what is the proper was to introduce a Maven dependency on a locally
installed GeoMesa so I can make use of the full API? Is there perhaps
a sample pom somewhere that illustrates this? My initial inclination
But this is not correct, and it does not pull in all of GeoMesa's
dependencies. I would assume there's a better way than adding a
similar block for each Jar nested in
Thanks for your help and patience,
On Mon, May 19, 2014 at 7:45 AM, Hunter Provyn <fhp@xxxxxxxx> wrote:
The short answer is yes, you need to add the hadoop client not to the
accumulo iterators lib/ext but as a compiled dependency in your project
GeoMesa depends on the hadoop-client but does not include it in the jar.
If you add the following to the pom of your project, that should resolve the
On 05/17/2014 05:21 PM, Connor Manning wrote:
Hello, I am trying to get some basic functionality for writing and reading
with GeoMesa from Java. I'm working from documentation.pdf in the
after doing a Maven install, and then I have placed all of the
subdirectories from there in my Java classpath (according to Section 2.3 in
Then I wrote a small Java program that just creates a DataStore like in
Section 3, which builds with no errors - however when running it there are
many errors. I am just trying a mock Accumulo instance for now, but I do
have Accumulo, Hadoop, and Zookeeper installed.
It looks like the root cause of the failure is
"java.lang.ClassNotFoundException: org.apache.hadoop.io.Writable". Do I
need to add libraries from my Hadoop installation in addition to the HDFS
jar in geomesa-dist?
Attached are my simple Java file I'm trying to run, the terminal output, and
brief build/run scripts to demonstrate what my classpath looks like.
Thanks for any pointers in the right direction,
geomesa-users mailing list
geomesa-users mailing list
Description: Binary data
Back to the top