[
https://issues.apache.org/jira/browse/SLING-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618570#comment-13618570
]
Ian Boston commented on SLING-2799:
-----------------------------------
Hi Hatim,
Welcome and think you for registering an interest. Please check out the links I
posted and familiarise yourself with the GSoC process and dates for this year.
It sounds like you have good general experience. You will need to understand a
bit about Sling itself and OSGi in general.
These links might help with background reading.
http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/Resource.html
http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceMetadata.html
http://sling.apache.org/site/discover-sling-in-15-minutes.html
http://www.osgi.org/download/r4v42/r4.cmpn.pdf (chapter 112)
http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html
http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/extending-scr-annotations.html
> Elastic Search backend for Sling: GSoC2013
> ------------------------------------------
>
> Key: SLING-2799
> URL: https://issues.apache.org/jira/browse/SLING-2799
> Project: Sling
> Issue Type: Bug
> Components: Samples
> Reporter: Ian Boston
> Labels: elasticsearch, gsoc, gsoc2013, java, osgi, sling
>
> This is a proposal for GSoC2013: create an Resource Provider that allows
> resources stored in Elastic Search to be exposed as Sling Resources.
> Resources[1] are the basic building blocks of Sling.
> ResourceProviders[2] allow data sources to be added to the core
> ResourceProvider within Sling allowing those data sources to provide
> Resources at pre-determined locations in the resource tree. To put it in more
> familiar terms, implementing and adding a Resource provider is like mounting
> or mapping a network drive.
> A more recent addition to the facilities available in Sling include updatable
> ResourceProviders.
> Elastic Search[3] is a elastically scalable search engine based on Lucene
> that has NoSQL like storage capabilities. Although written in Java, and used
> by many Java applications, it is used by a multitude of scripting communities
> (Python, Ruby, Php) as it exposes a RESTfull Json interface. Its NoSQL like
> capabilities are supported by the ability to index in real time over multiple
> shards and replicas. Notable users of Elastic Search include Wordpress,
> GitHub, FourSquare, Sony and many others.
> Initially this will provide read only resource access, but if there is time
> in the project will allow read write access to a Elastic Search cluster.
> Advanced Java skills are required, some knowledge of OSGi, Sling, Elastic
> Search will be valuable as will a detailed knowledge of HTTP and RESTfull
> architectures.
> The following pages give more information about GSoC @apache:
> * http://www.google-melange.com/gsoc/homepage/google/gsoc2013
> * http://community.apache.org/gsoc.html
> * http://s.apache.org/gsoc2013ideas
> 1 http://sling.apache.org/site/resources.html
> 2
> http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html
> 3 http://www.elasticsearch.org/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
