New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle LOBs that exist outside the database #346
Comments
This will be implemented as a filter module. An abstract class will ease the development of new filter modules for different file access protocols (e.g. S3). A default implementation for file system access protocol will be implemented. |
tomasmferreira
added a commit
that referenced
this issue
Apr 11, 2019
tomasmferreira
added a commit
that referenced
this issue
Apr 12, 2019
…lobs Implemented the option to add filter modules in between import and export modules when running dbptk: DBPTK help now shows available filter module names; Using -help <filter name> displays the list of parameters received by that filter; Using --filter or -f with the name of one or more filters (separated by ',') injects these filters (in the same order they are written in) into the workflow; Passing parameters to the filters is done using --filter<n>-<param long name> or -f<n><param short name> (where 'n' is the position of the filter in the list [starting at 1]). Implemented base system to support different types of external lobs: Added filter module to support handling of external lobs which can be added to the workflow using '--filter external-lobs', this filter requires at least two parameters: '--filter<n>-column-list [path to file]' which points to the file containing the list of columns in the database that reference external lobs (this file follows the same syntax as the one exported from the 'list-tables' module; '--filter<n>-reference-type [reference type]' which defines the strategy used to fetch the external lobs (ex.: file-system); Implemented abstract class ExternalLOBSCellHandler to ease the development of solutions for different types of external lobs by simply initializing a implementation of this class and passing it to the ExternalLOBSFilter. Implemented solution for external lobs on local file system
tomasmferreira
added a commit
that referenced
this issue
Apr 12, 2019
…lobs Implemented the option to add filter modules in between import and export modules when running dbptk: DBPTK help now shows available filter module names; Using -help <filter name> displays the list of parameters received by that filter; Using --filter or -f with the name of one or more filters (separated by ',') injects these filters (in the same order they are written in) into the workflow; Passing parameters to the filters is done using --filter<n>-<param long name> or -f<n><param short name> (where 'n' is the position of the filter in the list [starting at 1]). Implemented base system to support different types of external lobs: Added filter module to support handling of external lobs which can be added to the workflow using '--filter external-lobs', this filter requires at least two parameters: '--filter<n>-column-list [path to file]' which points to the file containing the list of columns in the database that reference external lobs (this file follows the same syntax as the one exported from the 'list-tables' module; '--filter<n>-reference-type [reference type]' which defines the strategy used to fetch the external lobs (ex.: file-system); Implemented abstract class ExternalLOBSCellHandler to ease the development of solutions for different types of external lobs by simply initializing a implementation of this class and passing it to the ExternalLOBSFilter. Implemented solution for external lobs on local file system
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If binary files are stored outside from the database (in file system) they should be handled like internal LOBs
The text was updated successfully, but these errors were encountered: