Serge Monkewitz, I'm trying to avoid adding many more configuration parameters to the config files but there are some parameters that we need to load to CSS and which need to come from config files. In the first version of the loader I added (copied from our existing *.param files) few options, all at top level:
- dirTable – name of the director table
- dirColName – column name containing ID of object in director table
- dirTable1,2; dirColName1,2 – same things for match tables
- storageClass
The dirColName I think is the same as the part.id parameter that is used by duplicator (will it be ever used by partitioner?) so we are duplicating the same info in one file. I was thinking about merging this into single set of options, e.g.:
- part.director – replaces dirTable
- part.id – instead of dirColName
- part.director1,2; part.id1,2 – for match tables
Does it make sense or do you think we should not mess with part.* option and create separate "section" for data loader and CSS parameters?
The actual question that I wanted to ask is how to identify director table from configuration information. If part.director is defined then I could just compare that with the current table name but I'm not sure that it makes sense to specify part.director for director table itself. Another option is to see if part.pos is specified and part.id is not (or if that part.id == id) which would mean that this is a partitioned table but there is no director for it which implies that it is itself a director. I'm not sure I'm thinking clearly now, what do you think?
Serge Monkewitz, I'm trying to avoid adding many more configuration parameters to the config files but there are some parameters that we need to load to CSS and which need to come from config files. In the first version of the loader I added (copied from our existing *.param files) few options, all at top level:
The dirColName I think is the same as the part.id parameter that is used by duplicator (will it be ever used by partitioner?) so we are duplicating the same info in one file. I was thinking about merging this into single set of options, e.g.:
Does it make sense or do you think we should not mess with part.* option and create separate "section" for data loader and CSS parameters?
The actual question that I wanted to ask is how to identify director table from configuration information. If part.director is defined then I could just compare that with the current table name but I'm not sure that it makes sense to specify part.director for director table itself. Another option is to see if part.pos is specified and part.id is not (or if that part.id == id) which would mean that this is a partitioned table but there is no director for it which implies that it is itself a director. I'm not sure I'm thinking clearly now, what do you think?