You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Ali Anil Sinaci (Created) (JIRA)" <ji...@apache.org> on 2012/01/26 16:24:38 UTC
[jira] [Created] (STANBOL-469) LDPath integration to Contenthub
LDPath integration to Contenthub
--------------------------------
Key: STANBOL-469
URL: https://issues.apache.org/jira/browse/STANBOL-469
Project: Stanbol
Issue Type: New Feature
Components: Content Hub
Reporter: Ali Anil Sinaci
LDPath should be integrated so that all modules of Contenthub can operate through LDPath programs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (STANBOL-469) LDPath integration to Contenthub
Posted by "Ali Anil Sinaci (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194530#comment-13194530 ]
Ali Anil Sinaci commented on STANBOL-469:
-----------------------------------------
This is resolved through the following features and improvements:
- LDPath has been integrated into Contenthub.
* Several Solr cores can be managed through LDProgramManager of Contenthub.
* Each LDPath program corresponds to a unique Solr core. LDPath programs (hence Solr cores) are uniquely identified through their names. LDProgramManager and SolrCoreManager provides the required synchronization between Solr cores and LDPath programs.
* Submitted LDPath programs are saved into separate files and accessed via a simple cache mechanism.
* CRD operations for LDPath programs are provided through LDProgramManager
* ClerezzaBackend is implemented as an LDPath backend.
* LDProgramManager has a special method (executeProgram) to execute the LDPath programs on Clerezza MGraphs.
* REST services are ready for LDProgramManager functionalities.
* Contenthub Store and Search parts (all interfaces and REST APIs) are adjusted so that they can operate with LDPath programs.
> LDPath integration to Contenthub
> --------------------------------
>
> Key: STANBOL-469
> URL: https://issues.apache.org/jira/browse/STANBOL-469
> Project: Stanbol
> Issue Type: New Feature
> Components: Content Hub
> Reporter: Ali Anil Sinaci
>
> LDPath should be integrated so that all modules of Contenthub can operate through LDPath programs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-469) LDPath integration to Contenthub
Posted by "Ali Anil Sinaci (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ali Anil Sinaci resolved STANBOL-469.
-------------------------------------
Resolution: Fixed
> LDPath integration to Contenthub
> --------------------------------
>
> Key: STANBOL-469
> URL: https://issues.apache.org/jira/browse/STANBOL-469
> Project: Stanbol
> Issue Type: New Feature
> Components: Content Hub
> Reporter: Ali Anil Sinaci
>
> LDPath should be integrated so that all modules of Contenthub can operate through LDPath programs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira