Thanks Andrea! I will let you know how I make out and whether (read: when)
I run into trouble next.
For the historical record, I mistyped and meant HBase, not Hive, but the
questions and responses are the same.
For the curious, HBase is a distributed database built on the Hadoop
platform, and is capable of handling petabytes of data, including binary
data like map tiles. It is an open source implementation of Google's
BigTable architecture.
On Nov 12, 2011 11:59 AM, "Andrea Aime" <[email protected]>
wrote:
> On Sat, Nov 12, 2011 at 4:48 PM, Chris Shain <[email protected]> wrote:
>
>> All,
>>
>> I am exploring the possibility of developing a new GeoServer data store
>> extension (along the lines of the sql server/oracle/teradata extensions)
>> for the Hive distributed database. This would presumably allow me to store
>> geo data at very large scale with excellent response time. I am
>> particularly interested in storing map overlay features (i.e. individual
>> address points with associated data and area overlays, like zip codes,
>> states, counties, etc).
>>
>> I have a few questions:
>>
>> 1) Does this seem feasible, e.g. are there any obvious roadblocks to this
>> or am I unlikely to succeed for some technical reason that I haven't seen
>> yet?
>>
>
> I guess you need some way to spatially index your data so that you can
> respond quickly to bbox queries.
> Not knowing much about hive, if it's able to repond to a "like" query fast
> you could use geohashing to
> turn a spatial entity into a string.
>
>
>>
>> 2) What pieces of plumbing would I need to write? As I mentioned, this
>> datastore is non-relational and does not have a formal structured query
>> language like SQL, so my assumption is that I likely need to build some
>> sort of predicate analyzer/query builder, but I'm OK with that. My main
>> question is around the integration points with GeoServer.
>>
>>
> You need to write your own DataStore implementation
>
>
>> 3) What is the recommended process for deploying/testing/debugging? I
>> have read the developer manual, but it seems a little thin
>>
>
> DataStores are GeoTools abstractions, you should look into the GeoTools
> manuals.
> Starting points:
> http://docs.geotools.org/stable/tutorials/advanced/datastore.html
> and have a look at any ContentDataStore based implementation.
> There are various, the jdbc stores, the aggregating store, property data
> store ng,
> the ogr store, etc, have a look here:
> http://svn.osgeo.org/geotools/trunk/
>
> Cheers
> Andrea
>
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
