[Registry-dev] Post 1.1 feature list for Registry core & product

[Afkham Azeez]

This looks very similar to HQL (Hibernate) ;)

Azeez

Chathura C. Ekanayake wrote:
> 
> I think it is also useful to introduce a data model independent simple 
> query language to the registry. Below is an example:
> 
> author = 'chathura' (search for all resources added by the author chathura)
> 
> author = 'chathura' and tags = 'java' (search for all resources added by 
> the author chathura and tagged as java)
> 
> content contains 'project A' and (media-type = 'application/xml' or 
> media-type = 'application/zip')
> 
> We can improve such query language to cover wide range of use cases. And 
> we can let the API users to invoke such queries directly from the API.
> 
> Collection results = registry.executeQuery("author = 'chathura' and tags 
> = 'java'");
> 
> We can also introduce a simple text field in the UI to which users can 
> directly type in and execute such queries.
> 
> Query processor model in the registry allows us to implement support for 
> such query language as a QueryProcessor and plug it in to the registry. 
> But we may have to introduce a new API method to execute queries 
> directly as shown above.
> 
> Thoughts...
> 
> Thanks,
> Chathura
> 
> 
> Afkham Azeez wrote:
>> Some  thoughts from a discussion we had this afternoon.
>>
>> 1. Content Search
>> Based on Apache Lucene (http://lucene.apache.org/). Kalani will be 
>> implementing this.
>>
>> 2. Indexing Content for improving search response times
>> This is related to the item#1 above and will be implemented by Kalani.
>>
>> 3. Notifications
>> I think we need to develop a Carbon notifications component. We will 
>> be able to plug-in different notification mechanisms such as email, 
>> SMS, IM etc. Also external parties should be able to send messages to 
>> this component on event such as a resource being changed, commented on 
>> or tagged, potential DoS attack detected by the throttling component, 
>> fatal error occurring, a member detecting the failure of another 
>> member in a cluster etc.
>>
>> 4. Clustering
>> For HA and scalability
>>
>> 5. Registry Federation + Hierarchical registries
>>
>> 6. DB specific optimizations
>> This is a feature available in other registries such a Jackrabbit. We 
>> can optimize the queries, the way pagination is handled etc. based on 
>> the underlying DB.
>>
>> I think we should be able to implement items#1,2,3 for the next 
>> release of registry. Any idea of a tentative release date?
>>
>> BTW Do we need a standalone version of the registry product that will 
>> simply run out of the box? This can be easily done by bundling the 
>> registry.war with the standalone embedded tomcat server contained in 
>> Carbon core, and will contain a configured Derby database.
>>
>> Anything else? Thoughts please.
>>
>> Thanks
>> Azeez
>>
>>
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>