Difference between revisions of "ESciDoc Cache"
Jump to navigation
Jump to search
m |
m |
||
| Line 8: | Line 8: | ||
*check integration with Lucene for administrative searches additionally | *check integration with Lucene for administrative searches additionally | ||
==Lucene== | |||
*separate index for all latest versions (instead of DBCache) (feasible)? | |||
*for items: an item contain all attributes needed to cross-check the authorization | |||
**instead of appending SQL to filter, would it be possible to append query to the user query that deals with auth data? | |||
**is the problem how to actually derive this query? | |||
*is this also valid for containers? (i.e. an item may be a member of several containers, but i think this has nothing to do) | |||
If this would be possible, no additional cache would be needed? | |||
Revision as of 16:04, 21 October 2009
Berkeley DB[edit]
- high performance
- high availability
- embedded into the application code (no need for separate storage)
- java api
- http://www.oracle.com/database/berkeley-db/index.html
- open source for open source projects
- check integration with Lucene for administrative searches additionally
Lucene[edit]
- separate index for all latest versions (instead of DBCache) (feasible)?
- for items: an item contain all attributes needed to cross-check the authorization
- instead of appending SQL to filter, would it be possible to append query to the user query that deals with auth data?
- is the problem how to actually derive this query?
- is this also valid for containers? (i.e. an item may be a member of several containers, but i think this has nothing to do)
If this would be possible, no additional cache would be needed?