Can you elaborate on how this would be implemented?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2019
It is in D894 ;)
hmm wait nvm, it should still be fixed
Forget about it, it's directly caused by T861
Dec 21 2018
Dec 19 2018
I suppose it all depends on the current storage's configuration.
Dec 18 2018
In the objstorage's pathslicing implementation, there is the get_stream implementation which is not used [1]
Dec 13 2018
Dec 6 2018
Dec 4 2018
Dec 3 2018
Nov 30 2018
Resolved by D758.
This comes from a discussion between myself and @vlorentz . To summarize my position: I would like to be able to tell downstream users "the keys we use in our metadata are (a subset of) the codemeta ones". AFAICT that means that they should be able to look them up here: https://codemeta.github.io/terms/ . As such, we should not use keys like schema:author, but simply author; similarly we should not use codemeta:issueTracker but simply issueTracker.
Nov 29 2018
Nov 28 2018
As we got around ~5b contents for now, i went for 100000 ranges of ~50k each
It's been scheduled and content indexers are now consuming again.
Nov 27 2018
Nov 21 2018
And it's done:
Let me fix that.
Actually, that's not a duplicate
yes, it is ;)
Only fossology_license_indexer needs that.
Nov 20 2018
By the way, status on this: