-
Notifications
You must be signed in to change notification settings - Fork 123
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
remove internal meta-data #3020
Comments
The A plugin running after Note: I actually have no idea, where the
Fixing it in IMO there has to be a way to mark metakeys (and maybe even normal keys) for automatic removal. All the marked keys should then be automatically removed, before the storage plugin is called. |
We once discussed that spec should be the vacuum cleaner to fix everything that is wrong with metadata.
The idea was that spec will be the very last plugin.
Yes, if the metadata is added during
There is no need for automatic removal because the semantics as given in doc/METADATA.ini already tell us what should be removed and what is needed for storage plugins. The spec plugin would need a list of metadata to be removed. This is not super-pretty but the alternatives need code-generation which is too much for 1.0 now. |
Yes, I know (#2700 (comment)), but it is not possible right now. I also think If we don't want to do the cleanup in the core (or the new backend plugin), it should be a separate cleanup plugin.
I don't know, where the
It might be true that |
Fair point. We can also make a new
Nothing should vanish between
For the removal code: certainly. Overall: I do not know. There are many plugins that set metadata to be removed, they all would need to be changed to mark their metadata. Furthermore, this would open the door for many different markers. E.g. for storage plugins we might want to remove different meta-data as for exporting configuration. |
I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue. |
I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue. |
@kodebach reported in #1164:
fixing it in
kdb
is quite straight-forward. But isn't it better to fix it in the spec plugin, then not every tool needs to reimplement it?See also #2700 (currently open because the global position for spec does not work).
The text was updated successfully, but these errors were encountered: