Hi, For several projects we need an search and index service with a REST interface. This needs to be tenantaware service and a tenant may define several indices.
Proposal for the REST interface (the index is the resource): - GET calls: - /rest/index/[indexname]/?q=... : search in index according to query - /rest/index/ : list of all indices - /rest/index/[indexname]/schema : schema of the index - POST calls: - /rest/index/[indexname] : creates an index with index name as identifier - PUT calls: - /rest/index/[indexname]/ : update the index (eg adding a document) - /rest/index/[indexname]/schema : updates the schema of the index - DELETE calls: - /rest/index/[indexname] : deletes index Implementation will be Solr embedded in an OSGi bundle. Remarks: - admin webinterface is not included. Only interface is a REST interface - default JSON interface (/solr/select?q=...) will be removed - authorization will be added - REST interface as described above will be added I suppose this will be a new subproject for Amdatu? Do we agree on this REST interface? Are there use cases where this REST interface is insufficient? Regards, Mark.
