Thanks for clearing that. One thing I noticed while ingesting data
is that a lot of tablets are created for the _records table.
Currently I have just 191 entries in records table and there are 177
tablets. I think this is due to the creation of different features
in geomesa because usually when I ingest data in geomesa with one
data type I dont get so many tablets even when the number of entries
are ingested are high. Can you please clear the logic behind
creation of tablets(table splitting) and if it is possible to alter
this behaviour?
Thanks
Vaibhav
On 04/04/2016 06:53 PM, Emilio
Lahr-Vivaz wrote:
Hi Vaibhav,
For your scenario with five different feature types, there
isn't a way through the GeoTools API to query more than one type
that I know of - you'd have to query the two types independently
and merge the results. I would consider whether you really need
five different types - if they have similar fields and you plan
to query them together it might make more sense to have a single
type with some kind of indicator label.
No one is currently working on Accumulo 1.7 support that I
know of, but we would like to add it. If you have a branch, we
are happy to accept merge requests. We'd need to keep the
backwards compatibility with Accumulo 1.5 and 1.6 through
profiles, though, as some of our user base is still on those
versions.
Thanks,
Emilio
On Mon, 2016-04-04 at 18:03 +0530, vaibhav.thapliyal wrote:
Hi,
Thanks for your reply. I got it working mostly by making changes
to my client code which was using geotools.
I have some further questions:
How do i set a 'nullable' hint for the attribute type?
I have a scenario where I have about five features representing
5 different types of geographical entities. For example
Hospitals, schools etc which I have stored under 5 different
feature names. I want to know if I can query more than two
features in a query. For example, find all hospitals and schools
within a range of 10 kms of a given point? Is there a provision
for this in the JAVA api?
Also I want to know if there are plans to extend geomesa for
accumulo 1.7.x, currently I am working with an experimental
branch for 1.7.x
Thanks
Vaibhav
On 04/01/2016 06:11 PM, Emilio
Lahr-Vivaz wrote:
Hi Vaibhav,
In general, GeoMesa allows you to leave most attributes
blank (however you must always include the default
geometry). I don't think that the exception you're getting
is coming from GeoMesa - I did a quick search for that
message and don't see it anywhere. Can you provide more of a
stack trace, or the code you're using?
One thing that might be affecting you is how you create
the simple feature type. In order to use hints like
'index=full', you need to use one of the GeoMesa simple
feature type helpers - either SimpleFeatureTypes.createType,
the SftBuilder or a typesafe config file. If not, then the
index hints you are setting will probably get dropped. In
addition, simple feature types have 'nullable' hints on each
attribute descriptor. In GeoMesa, we allow anything to be
null (except the primary geometry), so we ignore those
settings. However, if you're using GeoTools classes it may
be trying to validate your attribute values at some point.
Thanks,
Emilio
On Fri, 2016-04-01 at 17:40 +0530, vaibhav.thapliyal
wrote:
Dear all,
I have a few questions regarding ingestion using the java
API:
I have created an attributes list as follows:
attributeList = Lists.newArrayList("id:String",
"code:String:index=full",
"name:String",
"address:String",
"location:Point:srid=4326",
"pincode:String",
"email:String",
"url:String",
"dt_stamp:Date",
);
But in my data, there are records that do not have values
for email field and url. Hence I don't set url and email
value using the simpleFeature.setAttribute() function. When
I try and insert this feature in geomesa, I get the
following error:
Could not create ExampleFeature out of provided
feature
Is there a way to do this kind of ingestion where values of
some attributes of a feature might be null?
Thanks
Vaibhav
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users
|
