Uwe Schaefer
Uwe Schaefer
this is done by the major rewrite that is part of 0.8
After some discussions of offering type conversion or not, we agreed on doing preferrably: `@MetaData("myKey") Optional myOptionalValue` or (for those who know what they're doing) `@MetaData("myKey") String myOptionalValue` where myOptionalValue...
After discussing in several 1:1 meetings, there does not seem to be an easy solution. We'd need to go back to the whiteboard to plan a (probably major) structural change....
If we go for it, we must not forget that if the filesystem option of blacklisting is used, we need to make sure, all the ids are inserted into the...
While we're on it, we'd want to replace the term blacklist by exclusionlist.
Maybe much easier would be to change (as in update) the namespace of excluded facts to "EXCLUDED_". This way they could stick around and are still readable, but will never...
Thinking about it, a meta "excluded:true" would probably have the same effect if we add the respective criterion to pgquerybuilder.
with ->/->> notation, we could force pg to leave the query execution as is and filter afterwards: ``` postgres=> explain analyze select * from fact where header @> '{"ns":"organisation"}' AND...
Not sure if this is in scope, or should be addressed one level down (grpc-java)?
Good occasion to explore OpenRewrite