Re: [luciddb-users] LucidDB for Spatial OLAP

[John V. S. <js...@gm...>]

Emily Gouge wrote:
> import foreign schema habc
> from server habc_link
> into habc_extraction_schema;
> 
> no tables showed in the habc_extraction_schema.  "habc" schema in our postgesql database has many 
> tables, but there was no upper case "HABC" schema; so no tables/views were found.  My work around 
> for this was to create upper case schema and upper case views (with upper case column names) in 
> Postgres.  Is there a simpler way to do this?

Yes, LucidDB supports the SQL standard for using double-quotes around 
any identifier to preserve case, so:

import foreign schema "habc"
from server habc_link
into habc_extraction_schema;

> 2.  The second, larger problem I had, is that the Lucid server crashes when I try to load in large 
> amounts of data from our postgresql database.  The script I used to load data and the resulting 
> error message are listed below.  The master_grid table I am trying to load from contains approx. 
> 270,000,000 rows (and about 50 columns; approx 30G of data).  If I make a subset of the table that 
> is approximately 1 million rows (and 5 columns) I can load that data fine.  Any ideas on how to 
> resolve this issue?
> 
> We are running LucidDB (version 0.6.0) on linux [Centos v4.4, Kernal v2.6.9].  Java Version: 1.6.0_01

There have been a lot of bugfixes and enhancements (like support for 
concurrent read/write) checked into Perforce since the 0.6.0 release in 
January.  The crash below looks like an error unwind problem which has 
been fixed.  This means there's probably some other earlier error logged 
before that in /mnt/lucid/luciddb-0.6.0/trace/LucidDbTrace.log.  Could 
you mail the contents of that file to this list (or enough of the tail 
to show what happened before the crash)?  If we can figure out what's 
causing the ealier error, you may be able to get past this without a new 
version.

If not, the latest code is stable enough to put out an 0.7 release 
within a few days to see if that resolves the problem.

(Note that as far as I know, most testing up until now has been on Java 
1.5.)

JVS