Support #9658
database import clarifications
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Greg Shah over 1 year ago
There have been changes over the years where are not fully reflected in our import docs. There are also areas never documented. This task is intended to fill in those gaps.
Here are some items I know about:
- Importing on a runtime-only system.
- This is the idea that you don't have all of the normal project gorp in production installations.
- What stuff needs to be in the application jar file?
- How do you run import (there is a script now)?
- Importing
_sec-auth*tables.- What is the data needed for?
- Where does it come from?
- How to get it into the database?
- Multi-tenant considerations for import. (this one probably should be done along with the changes for #9093)
- How to import an empty database? (see #7894)
- Understanding the import command output.
- Guidance on import performance, thread and resource usage.
- Properly specifying encoding.
- Issues (and for each one, how to fix them)
- encoding mismatches
- index length problems with some db dialects
- data integrity (e.g. duplicate records in an index that is marked unique)
- missing id generator
- Do we have full documentation for manually running the import command? (full syntax of the "raw" command, not just the
import.shwhich is just a helper)
Now is the time to get this documentation fixed so that we don't spend our lives answering the same questions and working the same problems over and over.