Re: [luciddb-users] What to do to physically import the data to LucidDB?

[Mark C. <mar...@li...>]

It's just a link. You'd have to create a table with the fields you want in
another database in LucidDB, and do a INSERT INTO [LucidDB table] SELECT *
FROM [postgres table]

Mark Cahill
Data Analyst
YouVersion





On 2/24/12 5:38 PM, "bibudh" <bi...@gm...> wrote:

>
>   Hi,
>    I am trying to import 5 tables from my transactional PostgreSQL DB to
>LucidDB. Initially I created a JDBC FDW. Now, as per the following post,
>Lucid does not physically import the data, but imports only the metadata.
>
>   
>http://www.luciddb.org/forums/discussion/353/-pertaining-to-indexes-on-for
>eign-tables./p1
>
>    This was evident when I did EXPLAIN PLAN for one of the queries. I
>could
>see MedJdbcQueryRel at the lowest level, with foreignSql statements,
>rather
>than FennelValuesRel.
>
>    However, after this, I exported my data to .csv files and loaded
>using a
>file wrapper. After that, when I do EXPLAIN PLAN for a query, I see
>FlatFileFennelRel at the lowest level, and not FennelValuesRel. Does this
>mean the data is physically only in the files and not in Lucid?
>
>    My question is, what do I need to do to make sure the data gets
>PHYSICALLY loaded to the LucidDB tables, so that I can create bitmap
>indexes
>and use them successfully? Also, for MedJdbcQueryRel queries, are the
>indexes already in the PostgreSQL DB used?
>
>    I have already tried the following for import
>
>    insert into EXTRACTION_SCHEMA."people" select * from
>sandbox."public"."people";
>
>    but it gives the following error:
>
>    Error: Optimizer failed to find a valid physical implementation for
>relational expression
>rel#1445:TableModificationRel.NONE(child=HepRelVertex#1446,table=[LOCALDB,
>EXTRACTION_SCHEMA,
>people],operation=INSERT,updateColumnList=[],flattened=true); see trace
>for
>partially optimized plan. Details: reason is [Node's traits (NONE) do not
>match required traits (ITERATOR)]; while preparing statement [explain plan
>for insert into EXTRACTION_SCHEMA."people" select * from
>sandbox."public"."people"]. (state=,code=0)
>
>    Also, I guess import is probably not the preferred method for tables
>with millions of rows?
>
>    Thanks
>             Bibudh
>
>--
>View this message in context:
>http://luciddb-users.1374590.n2.nabble.com/What-to-do-to-physically-import
>-the-data-to-LucidDB-tp7316306p7316306.html
>Sent from the luciddb-users mailing list archive at Nabble.com.
>
>--------------------------------------------------------------------------
>----
>Virtualization & Cloud Management Using Capacity Planning
>Cloud computing makes use of virtualization - but cloud computing
>also focuses on allowing computing to be delivered as a service.
>http://www.accelacomm.com/jaw/sfnl/114/51521223/
>_______________________________________________
>luciddb-users mailing list
>luc...@li...
>https://lists.sourceforge.net/lists/listinfo/luciddb-users