Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
kdb export metadata #2738
There are three solutions to this:
Personally, I think the first solution is the best, but circumventing all validation plugins might cause problems.
NOTE: I didn't provide steps for reproduction, even though this is a bug report. The bug is obvious from the code:
Thank you for reporting the bug!
Yes, this is a bug. It should be removed by post-processing the KeySet.
This is a quite new idea (proposed in #2724). Yes, it also makes sense for
It also could be done easily in postprocessing.
Even if you would call a full kdbGet, you might need to postprocess some metadata as the storage plugin used for exporting might not support internal or origvalue.
Bugs are always obvious from the code once you understand the code. Nevertheless showing the wanted behavior is important. Otherwise the new implementation might still not do what you expected.
@llukask hopefully will address these problems.
Yes, it would. But this is a bug of INI as it actually should use "order" and not "internal/order".
Didn't removing the meta-data of the parentKey also fix the problem?
Yes, but I didn't actually suggest dropping any metadata in
I don't think post-processing is a good solution. It requires that
Actually it should use
Otherwise that would mean storage plugins are not allowed to use any
The export plugin might be a different one than the one that is used within kdbGet.
The idea would be that doc/METADATA.md defines the behavior.
There is the "order" metadata, only INI does not use it. (And now causes many problems.)