Feature #1664
data import improvements
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
Related issues
History
#1 Updated by Eric Faulhaber over 11 years ago
- performance improvement: re-architect threading to distribute work in a more granular way (preserve prioritization by table, but allow multiple threads to run within the import of a single table to avoid the "critical path" problem);
- make schema generation independent of Hibernate (today we rely on Hibernate tools past end-of-life, which have some issues for us);
- we currently cannot re-create the schema to properly use text instead of varchar for string data, due to some changes we made in the P2J<-->Hibernate data bindings;
- make index creation independent of Hibernate (today we let Hibernate generate the index creation DDL; we need more flexibility);
- abstract out PostgreSQL-specific code (running the ANALYZE command after each table is imported) into a more database-independent model.
#2 Updated by Greg Shah over 11 years ago
- Target version set to Deployment and Management Improvements
#3 Updated by Greg Shah over 7 years ago
- Target version deleted (
Deployment and Management Improvements)
#4 Updated by Eric Faulhaber over 3 years ago
- Related to Feature #4723: make it significantly easier to run database import added
#5 Updated by Eric Faulhaber over 3 years ago
- Estimated time deleted (
48.00)
Note that as of FWD trunk rev 11348, Hibernate is no longer used. As such, the Hibernate-specific issues noted above no longer are relevant.
The other issues remain.