Page Comparison

We can encounter several failures while importing content/data in Asta7 for several reasons. So far our approach for handling failures has been to throw an exception and abort the import. But this approach is not user-friendly as most of the failures are recoverable.

...

Info
This tool will be used only for the Single Archive and Excel import from Asta7

Table of Contents

style	none

Failures and Possible Solutions

...

Failure	Solutions	Challenges
AMID conflict	Regenarate Genarate	Replace all `objectReference`
PK conflict (Single PK only for now)	Regenaret Genarate if UUID Input from the user	Replace all `FK` How to handle composite PK? Should we generate other types? If so then how?
PK conflict (Single PK only for now)	Input from the user	Requires user interaction
Unique conflict	Regenarate Genarate if UUID	Should we generate other types? If so then how?
	Input from the user	Requires user interaction
	Set `null` if nullable
FVP Unique conflict (Root entities only for now)	Regenarate if FVP Genarate
	Input from the user	Requires user interaction
	Set `null` if nullable
FK conflict (Not yet supported)	Set `null` if nullable
NULL conflict	Genarate	Regenarate Generate dummy values if not UUID Regenarate if or FVP and root
NULL conflict	Input from the user	Requires user interaction
Wrong type	Genarate	Regenarate Generate dummy values if not UUID Regenarate if or FVP and root
	Input from the user	Requires user interaction
	Set `null` if nullable
Wrong length	Trim extra
	Input from the user	Trim extra Requires user interaction
	Set `null` if nullable

System Entities

For this section, we need to consider the system root entities like AKTOR, TAG, etc. and ignore AMID/PK conflicts for all sub-entities. We should add some have added options for handling AMID/PK/Unique/FVP Unique conflicts for the system root entities.

Failure

Solutions

Challenges

AMID/PK/Unique/FVP Unique conflict

Ignore

Replace with the conflicted row
Replace with a chosen row (Maybe later)
If ignored then need to ignore Ignore the whole subtree for this row as wellIf replaced need to replace
Highest precedence

Replace with the conflicted row

Replace all objectReference and FK as well
If replaced need to keep Keep the relation objects but change their FK
2nd highest precedence
Should we consider the possible new sub-entity objects?
Should we consider the possible changes for this subtree?

Replace with a chosen row (Maybe later)

Implementation

We can divide the implementation into four key steps.

...

As before we will try to import the data without any changes. In case of an exception, we will analyze the exception to check if it is a resolvable exception (AMID/PK conflict, NULL conflict, etc.). If resolvable then the import job dialog will show a button to start the resolving process.

...

Clicking the Resolve button will start the 2nd step.

...

Conflict Resolution Options

After clicking the Resolve button a new tab will be opened. The tab will start a background job In the tab, there will be options to choose how do you want to proceed. There will be options present per conflict type. Either you can gather the conflicts beforehand, or gather and solve them while importing, and the third option is to mix both, meaning gather some types beforehand but resolve the rest while importing.

Conflict Type	Default Solutions (Used while importing)
AMID	Generate
AMID	Fail (Throw exception)
PK	Generate (Available if all are UUID)
PK	Fail (Throw exception)
UNIQUE	Generate (Available if all are UUID)
UNIQUE	Fail (Throw exception)
FVP_UNIQUE	Generate
FVP_UNIQUE	Fail (Throw exception)
FK (Not supported yet)	Set `null` if nullable
FK (Not supported yet)	Fail (Throw exception)
REQUIRED	Generate a dummy value
REQUIRED	Fail (Throw exception)
TYPE	Set `null` if nullable or Generate a dummy value
TYPE	Fail (Throw exception)
LENGTH	Trim the extra part
LENGTH	Fail (Throw exception)
SYSTEM ENTITY	Generate (Generate new UUID or FVP)
	Ignore
	Replace with the conflicted row
	Fail (Throw exception)

If all the types are set to resolve at import time then the Resolve and Import button will be shown. In this case, the 3rd step is not needed anymore. Otherwise, you can proceed to the 3rd step by clicking the Gather Conflicts button.

Gather and Show Conflicts with Possible Solutions

After clicking the Gather Conflicts button a background job will be started, which will go through the import file and gather all the resolvable conflicts for the chosen types. After gathering all the conflict they will be shown in a table with possible solutions to choose from. The conflicts will be grouped by the entity name and the conflict the 3rd step will begintype. It is also possible to pick a solution for the whole group.

Info
The current limit for gathering conflicts is 100010,000.

Show Conflicts and Possible Solutions

Once the conflict-gathering job is done the tab will show all the conflicts in a table.

...

The table contains the following columns

...

Column

...

Description

...

Entity Name

...

Resolve and Import

Clicking the Resolve and Import button will begin the 4th and final step. In this step, the import will run again. All the conflicts gathered beforehand and conflicts gathered while running will be resolved based on the chosen solution.

Things To Do

Support Excel import
Support Composite PK
Support FK conflict
Generate other types than UUID
Optimize using temporary table and/or files rather than the memory
Add more types of solutions

Versions Compared

Old Version 13

New Version 14

Key