[
https://issues.apache.org/jira/browse/SOLR-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487890#comment-16487890
]
Mark Miller commented on SOLR-10299:
------------------------------------
If you could use Solr in an embedded way that requires minimal to no
maintenance, okay great. But Solr does not excel at that.
If someone figures out how to use Solr in a convenient way, great. But it's a
slippery slope. What if search goes down? Don't we work on SolrCloud? Shouldn't
it be fault tolerant and always running? Shouldn't the search experience itself
be A++ in all cases?
I'm open to any solution that ends up making sense. But from my viewpoint, we
just want some good enough keyword search that we don't have to maintain, and
then for something better we can clearly link out to managed services like
LucidFind that will showcase Solr much better than we will over the long term.
> Provide search for online Ref Guide
> -----------------------------------
>
> Key: SOLR-10299
> URL: https://issues.apache.org/jira/browse/SOLR-10299
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Priority: Major
>
> The POC to move the Ref Guide off Confluence did not address providing
> full-text search of the page content. Not because it's hard or impossible,
> but because there were plenty of other issues to work on.
> The current HTML page design provides a title index, but to replicate the
> current Confluence experience, the online version(s) need to provide a
> full-text search experience.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
