You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2011/03/15 19:40:30 UTC
[jira] Created: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
------------------------------------------------------------------------------------------------------------------
Key: STANBOL-115
URL: https://issues.apache.org/jira/browse/STANBOL-115
Project: Stanbol
Issue Type: Improvement
Components: Enhancer, Entity Hub
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
The Stanbol Enhancer Full Launcher includes the
- Entityhub and
- Referenced Site based Entity Tagging Enhancement Engine
both currently require a manually configuration by the User.
In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
Details are described in this Mail:
http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
This needs to be improved by
(1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
(2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Resolved: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
Posted by Fabian Christ <ch...@googlemail.com>.
Hi Rupert,
> Rupert Westenthaler resolved STANBOL-115.
> -----------------------------------------
>
> Resolution: Fixed
>
> with revision #1081910 the full launcher of the Stanbol Enhancer starts up a "ready to use" version of
> - the Entityhub
> - a ReferencedSite for DBpedia.org (remote access & search, local caching of accessed entities
> - EntityTagging Enhancement Engine using the DBPedia.org ReferencedSite
Cool! Nice work. Will check it out soon.
Thank you!
- Fabian
[jira] Commented: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007357#comment-13007357 ]
Rupert Westenthaler commented on STANBOL-115:
---------------------------------------------
This configuration requires the DBpedia.org SPARQL endpoint to be up and running to search for Entities and download them if they are not in the local cache (and the cache will be empty during the integration test).
However I could add checks for the "org.apache.stanbol.*ReferencedSiteEntityTaggingEnhancementEngine" and an additional call to "http://localhost:8080/entityhub/sites/referenced" with the result "http:\/\/*\/entityhub\/site\/dbPedia\/" to the EnhancerTestBase.checkEnginesReady() method.
This will not require the remote service to be available and still validate the configuration.
In addition I could alter/update the DefaultConfigTest to check for the new configuration files
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007396#comment-13007396 ]
Rupert Westenthaler commented on STANBOL-115:
---------------------------------------------
I would rather do that within STANBOL-92, because this issue is about packing also a local index that can be used in combination with the ReferencedSiteEntityTaggingEnhancementEngine. Than such an integration test can run offline and there would be no danger to make Hudson unhappy if the SPARQL service at dbpedia.org is unavailable.
In addition as soon as STANBOL-92 is resolved we can also
- remove the Autotagger
- replace the EntityMentionEnhancementEngine with the ReferencedSiteEntityTaggingEnhancementEngine
- remove the CachingDereferencerEngine
- replace the EntityCacheProvider with Entityhub functionality provide an EntityCacheProvider implementation based on the Entityhub
BTW: I have added the checks for the configured ReferencedSiteEntityTaggingEnhancementEngine and the dbPedia ReferencedSite to the EnhancerTestBase.checkEnginesReady() method with revision #1082095
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-115.
-----------------------------------------
Resolution: Fixed
with revision #1081910 the full launcher of the Stanbol Enhancer starts up a "ready to use" version of
- the Entityhub
- a ReferencedSite for DBpedia.org (remote access & search, local caching of accessed entities
- EntityTagging Enhancement Engine using the DBPedia.org ReferencedSite
Note that bundling of local index for dbPedia and dbPediaTopics is covered by STANBOL-93 and STANBOL-92 and not part of this one.
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved STANBOL-115.
-----------------------------------------
Resolution: Fixed
Ok, adding tests as part of STANBOL-92 makes perfect sense, thanks for the explanation!
Marking this issue resolved again, sorry for the noise.
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (STANBOL-115) Provide Default
Configuration and Automatic Initialization for the Entityhub in the Stanbol
Enhancer Full Launcher
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007396#comment-13007396 ]
Rupert Westenthaler edited comment on STANBOL-115 at 3/16/11 10:03 AM:
-----------------------------------------------------------------------
I would rather do that within STANBOL-92, because this issue is about packing also a local index that can be used in combination with the ReferencedSiteEntityTaggingEnhancementEngine. Than such an integration test can run offline and there would be no danger to make Hudson unhappy if the SPARQL service at dbpedia.org is unavailable.
In addition as soon as STANBOL-92 is resolved we can also
- remove the Autotagger
- replace the EntityMentionEnhancementEngine with the ReferencedSiteEntityTaggingEnhancementEngine
- remove the CachingDereferencerEngine
- replace the EntityCacheProvider with Entityhub functionality or provide an EntityCacheProvider implementation based on the Entityhub
BTW: I have added the checks for the configured ReferencedSiteEntityTaggingEnhancementEngine and the dbPedia ReferencedSite to the EnhancerTestBase.checkEnginesReady() method with revision #1082095
was (Author: rwesten):
I would rather do that within STANBOL-92, because this issue is about packing also a local index that can be used in combination with the ReferencedSiteEntityTaggingEnhancementEngine. Than such an integration test can run offline and there would be no danger to make Hudson unhappy if the SPARQL service at dbpedia.org is unavailable.
In addition as soon as STANBOL-92 is resolved we can also
- remove the Autotagger
- replace the EntityMentionEnhancementEngine with the ReferencedSiteEntityTaggingEnhancementEngine
- remove the CachingDereferencerEngine
- replace the EntityCacheProvider with Entityhub functionality provide an EntityCacheProvider implementation based on the Entityhub
BTW: I have added the checks for the configured ReferencedSiteEntityTaggingEnhancementEngine and the dbPedia ReferencedSite to the EnhancerTestBase.checkEnginesReady() method with revision #1082095
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz reopened STANBOL-115:
-----------------------------------------
Assignee: (was: Rupert Westenthaler)
Could you suggest an integration test that we could add under enhancer/integration-tests to verify that this config is correctly activated?
If you can supply a curl/http scenario I'm happy to write the test class(es), or feel free to write it based on the existing ones.
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (STANBOL-115) Provide Default Configuration and
Automatic Initialization for the Entityhub in the Stanbol Enhancer Full
Launcher
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007390#comment-13007390 ]
Bertrand Delacretaz commented on STANBOL-115:
---------------------------------------------
I was more looking at testing a use case of this new components, is that possible out of the box?
Otherwise as you say the test can just check that the components are present, but if the test is also an usage example that's much better
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-115
> URL: https://issues.apache.org/jira/browse/STANBOL-115
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
> - Entityhub and
> - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
> http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira