Bug #9872
Runtime import statement relies on the ImportWorker to read lob data.
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:
Related issues
History
#1 Updated by Artur Școlnic over 1 year ago
In PropertyMapper.readLobData, Importworker is used to retrieve the path to the lob file. Importworker is not supposed to be used in the runtime environment, we need to find another way to specify the path to the lob file so that the readLobData could read the file contents.
#2 Updated by Artur Școlnic over 1 year ago
- Related to Bug #9060: Cache oftenly used values that are immutable added
#3 Updated by Ovidiu Maxiniuc over 1 year ago
The PropertyMapper is one class which was created only during the import, as an utility of ImportWorker. The fact that is used in runtime may not be OK even if the ImportWorker.lobPath is replaced.
OTOH, the runtime of IMPORT avoids code duplication and reuses the PropertyMapper.preprocessBlob(), and PropertyMapper.preprocessClob(). The answer may be to have a context variant of ImportWorker.lobPath.