[
https://issues.apache.org/jira/browse/SOLR-14066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994706#comment-16994706
]
Tim Allison commented on SOLR-14066:
------------------------------------
{quote}Then be “DIH is no longer part of Apache but thrives in its new home at
github...”
{quote}
Is the notion that we'd break different components of DIH into different
personal repos on github, like: [https://github.com/dadoonet/fscrawler]
I worry about moving critical code to personal repos, even though it can be
forked/maintained by others. And, by "critical", I appreciate and completely
agree with Jan's point about how it should be "demo only", but is in fact used
across the land in production. :(
I'm very much in favor of moving Tika, at least, out of Solr...but to where?
Smaller, less pressing question: does this mean green fields (start fresh) for
https://issues.apache.org/jira/browse/SOLR-7632?
In short, rather than implementing SOLR-7632, we should start a side project
that uses tika-server as the default?
> Deprecate DIH
> -------------
>
> Key: SOLR-14066
> URL: https://issues.apache.org/jira/browse/SOLR-14066
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - DataImportHandler
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Fix For: 8.4
>
>
> DataImportHandler has outlived its utility. DIH doesn't need to remain inside
> Solr anymore. Let us deprecate DIH in 8.4 (and remove it from the Solr distro
> in 9x or 10x).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
