You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2008/11/13 05:17:44 UTC
[jira] Created: (SOLR-853) Make DIH API friendly
Make DIH API friendly
---------------------
Key: SOLR-853
URL: https://issues.apache.org/jira/browse/SOLR-853
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler
Reporter: Noble Paul
DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
* Lucene users directly
* Run DIH remotely with SolrJ
* By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SOLR-853) Make DIH API friendly
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647801#action_12647801 ]
noble.paul edited comment on SOLR-853 at 11/14/08 9:49 PM:
-----------------------------------------------------------
Removes dependency on non-common util directly.
Need to add {{LuceneDataImporter}} and {{SolrJDataImporter}} and give examples on how this can be used externally
was (Author: noble.paul):
Removes dependency on non-common util directly.
Need to add {{LuceneDataImporter}} and {{SolrJDataImporter }} and give examples on how this can be used externally
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-853) Make DIH API friendly
Posted by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655568#action_12655568 ]
Shalin Shekhar Mangar commented on SOLR-853:
--------------------------------------------
It can surely be used to write to HBase and CouchDB :)
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-853) Make DIH API friendly
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650033#action_12650033 ]
Noble Paul commented on SOLR-853:
---------------------------------
bq.Once you decide you want a modular design, why limit it to storing in Lucene?
It is possible , but DIH is designed to create target documents in a denormalized form (a single table) . This is quite unique to Lucene.
While a few users might find it useful, it can't be generalized. The moment it is made possible , there may be requests for enhancements specific to DB . I do not wish to get into the domain of Kettle or Talend.
But I shall leave the core generic enough to be used by others
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-853) Make DIH API friendly
Posted by "Lance Norskog (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649983#action_12649983 ]
Lance Norskog commented on SOLR-853:
------------------------------------
Once you decide you want a modular design, why limit it to storing in Lucene? If it can read from a DB, why not write to it as well?
RSS -> relational DB -> Solr is a better system design than RSS -> Solr because we should store the raw data in a DB, not store it directly in Solr.
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-853) Make DIH API friendly
Posted by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-853:
---------------------------------------
Fix Version/s: 1.5
Marking for 1.5
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.5
>
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-853) Make DIH API friendly
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul updated SOLR-853:
----------------------------
Attachment: SOLR-853.patch
Removes dependency on non-common util directly.
Need to add {{LuceneDataImporter}} and {{SolrJDataImporter }} and give examples on how this can be used externally
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SOLR-853) Make DIH API friendly
Posted by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar reassigned SOLR-853:
------------------------------------------
Assignee: Shalin Shekhar Mangar
> Make DIH API friendly
> ---------------------
>
> Key: SOLR-853
> URL: https://issues.apache.org/jira/browse/SOLR-853
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Reporter: Noble Paul
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-853.patch
>
>
> DIH currently can only be run inside Solr. But the core of DIH is quite independent of Solr. There are only a few points where it requires Solr core classes.They can be isolated out and we have an API in hand. If we limit the dependency down to common util then DIH can be used by
> * Lucene users directly
> * Run DIH remotely with SolrJ
> * By any other tools using Lucene as their underlying datastore
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.