Re: [luciddb-users] LucidDB for Spatial OLAP

[Emily G. <eg...@re...>]

 > As a workaround, you could try loading the data in large chunks of rows
 > via a WHERE clause on some partitioning key (if there is one in the
 > source data).

I tried this, however I am still getting Java heap space errors.  This query should return only one row.

select "x","y", "ecosec_v2_code", "lwdpbc_code", "bececolwd_v2_code", "dra_code" from 
habc_extraction_schema."master_grid" where "x" = 0 and"y" = 0;

causes:
Error: java.lang.OutOfMemoryError: Java heap space (state=,code=0)


I have noticed that adding the where clause to the query does not change the query being run on the 
postgresql database.  Both cases cause a "SELECT * FROM "habc"."master_grid"" query to be run on the 
postgresql database with no where clause.

Any ideas on how the query:
select "x","y", "ecosec_v2_code", "lwdpbc_code", "bececolwd_v2_code", "dra_code" from 
habc_extraction_schema."master_grid" where "x" = 0 and"y" = 0;

is being converted to a:
select * from "habc"."master_grid"

Thanks again.