sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <>
Subject [jira] [Updated] (SLING-2795) Apache Solr backend for Apache Sling
Date Thu, 08 Mar 2018 15:16:00 GMT


Robert Munteanu updated SLING-2795:
    Labels: gsoc gsoc2013 gsoc2018 java osgi sling solr  (was: gsoc gsoc2013 java osgi sling

> Apache Solr backend for Apache Sling
> ------------------------------------
>                 Key: SLING-2795
>                 URL:
>             Project: Sling
>          Issue Type: New Feature
>          Components: Samples
>            Reporter: Bertrand Delacretaz
>            Priority: Major
>              Labels: gsoc, gsoc2013, gsoc2018, java, osgi, sling, solr
> This is a proposal for GSoC 2013: create a Java/OSGi backend that allows Sling to use
an Apache Solr server for content storage.
> Interested students are welcome to get in touch with the Sling community via its mailing
lists to discuss the project, see
> Recent additions to the Sling resource management support using any existing content
store as a backend for content storage, and creating an example ResourceProvider [1] that
uses Apache Solr as its backend would be a good example of that.
> This support for arbitrary content stores is relatively new in Sling, so we might discover
some missing features or incomplete implementations along the way. The student will need to
interact closely with the Sling community to discuss any improvements needed to reach this
project's goals.
> As Solr is probably not well suited for storing large binaries, a hybrid store will probably
be needed, where "small" data items are stored directly in Solr and large, binary values stored
on a filesystem-based structure like the Jackrabbit DataStore.
> Advanced Java skills are required, as is good knowledge of HTTP protocols and clients
and knowledge of automated testing tools to be able to validate the results.
> The following pages give more information about GSoC @apache:
> *
> *
> *
> [1]

This message was sent by Atlassian JIRA

View raw message