Conversation
new manifest support
ec51181 to
a4be288
Compare
c2e1781 to
48795e9
Compare
0c9c953 to
448f434
Compare
8328918 to
5d72cc7
Compare
fad8e9a to
23bf22e
Compare
e74dbcf to
d88c0f9
Compare
52d0686 to
d88d972
Compare
bfffc96 to
1e5d699
Compare
| for metadata in metadata_list: | ||
| if not metadata.get('key') and metadata.get('value'): | ||
| continue | ||
| key = metadata['key'] |
There was a problem hiding this comment.
@kudj tohle uz jsem rikal v predchozim commentu, ktery je ted nedohledatelny (protoze jsi delal force-push, na tohle bacha pokazdy musis udelat pull nebo radsi rebase kdyz je v destination zmena. Jinak prepises praci nekomu jinymu). Table metadata ma simplified strukturu v novym manifestu jako key:value, takze {key:x, value:x} nebude fungovat.
There was a problem hiding this comment.
|
Uz to vypada dobre, jen par veci:
|
| for col in val: | ||
| if col not in self.columns: | ||
| self.schema[col] = ColumnDefinition() | ||
| self.schema[col] = ColumnDefinition() |
There was a problem hiding this comment.
Promin ale tohle porad neni to co jsem myslel 4f3c6dd#diff-6615ea46ac4ee88c1db70b9f0623e257843f25b60b46d65de76a2c8fdbac64bcR1246 tady to potichu zarve a uzivatel si bude myslet ze se neco stalo, ale nic se nestalo. Zachoval bych tu puvodni funkcionalitu a tady prepsal cely schema a vyhodil ten check
There was a problem hiding this comment.
změněno, takže uživatel si může přepsat celé schema jen nastavením columns a jenom to vypíše warning?
|
@davidesner native_types a new_manifest nahrazeny legacy_manifestem který se nastavuje podle KBC_DATA_TYPE_SUPPORT |
No description provided.