BTW I think a consultant/consuntancy would do good business in taking ownership of DIH. Loads of people use it and some will come looking to pay for help! Heck, even a user of my tiny HTTP Proxy Servlet https://github.com/mitre/HTTP-Proxy-Servlet/ inquired about paid support! If I was still a freelancer, I think I would jump at this opportunity.
~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Thu, Oct 15, 2020 at 5:08 PM David Smiley <[email protected]> wrote: > I'm glad you're raising this because I've been meaning get more visibility > on a proposal I made in JIRA: > > https://issues.apache.org/jira/browse/SOLR-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203524#comment-17203524 > > <https://issues.apache.org/jira/browse/SOLR-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203524#comment-17203524>Pertinent > part: > >> This is a great example of the problem because I'd rather we not log a >> warning about the DIH being deprecated – it is being *moved*. The >> deprecation notion is *sometimes* only useful for those maintaining Solr >> itself (us committers). Maybe we could just remove the annotation and only >> use the javadoc @deprecatedtag for plugins we know are *moving*? >> > > Obviously this doesn't address most of Eric's point, but I think it would > be helpful in avoiding undue concern amongst our users. > Looking at https://cwiki.apache.org/confluence/display/SOLR/Deprecations > it appears we're moving 3 plugins. (1) DIH, (2) Velocity: a javadoc > @deprecated tag could be added to VelocityResponseWriter (currently doesn't > have an annotations), and (3) HDFS: HdfsDirectoryFactory could get > a @deprecated tag and remove the @Deprecated annotation. > > Cool? > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Thu, Oct 15, 2020 at 3:21 PM Eric Pugh <[email protected]> > wrote: > >> I noticed that we’re getting tickets like SOLR-14938 opened that are all >> about the future of DIH. I know some of my own clients are asking about it >> as well. I suspect we will get more and more of these! >> >> I wonder if there are any ideas/suggestions on how to better communicate >> that DIH isn’t going away, and indeed, it’s moving to a better place (I >> hope!). Do we want to add to the UI a message about “join the new >> community at https://github.com/rohitbemax/dataimporthandler”? >> >> Having said that, I see issues opening at >> https://github.com/rohitbemax/dataimporthandler and not being closed, so >> I do have some concerns that a supportive community may not actually be >> forming. >> >> >> Eric >> >> _______________________ >> *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 >> | http://www.opensourceconnections.com | My Free/Busy >> <http://tinyurl.com/eric-cal> >> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed >> <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> >> This e-mail and all contents, including attachments, is considered to be >> Company Confidential unless explicitly stated otherwise, regardless >> of whether attachments are marked as such. >> >>
