[ 
https://issues.apache.org/jira/browse/SOLR-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385545#comment-14385545
 ] 

Mark Haase commented on SOLR-7316:
----------------------------------

Thanks, Shawn.

{quote}
I will admit that sometimes we don't give enough thought to the complete novice 
user in what we do
{quote}

I have to clarify a misperception here: I'm not a _complete novice_ to Solr, 
just new to Solr 5. I used Solr quite a bit back in the 1.4 days, and I spent a 
lot of time back then carefully crafting my schema.xml, declaring dynamic 
fields, etc. (Note that most of what I did back in those days is no provided 
out-of-the-box in the Solr basic_config, which would be serendipitous if I 
could figure out how to actually use basic_config.) I have several applications 
still in production, quietly humming along with Solr 1.4.

So in some ways, I'm both the novice user and the experienced user.

I'm not insisting that it needs to be brain-dead easy. This is a complicated 
domain, and I'm willing to put in time reading and learning. I'm not objecting 
to a learning curve; I'm objecting to a culture of shoddy documentation and 
"works for me #wontfix" responses to bugs. It appears that *none* of the Solr 
expert guys are using Solr instances installed by the installation script, as 
evidenced by [this issue|https://issues.apache.org/jira/browse/SOLR-7323] where 
the response is, "why did you set your SOLR_HOME to /var/solr/data?" Umm... I 
didn't. _That's the installation script's default._

> API to create a core is broken
> ------------------------------
>
>                 Key: SOLR-7316
>                 URL: https://issues.apache.org/jira/browse/SOLR-7316
>             Project: Solr
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 5.0
>            Reporter: Mark Haase
>
> *Steps To Reproduce*
> {code}
> curl 
> 'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&instanceDir=new_core'
> {code}
> *Expected Result*
> Create a core called "new_core".
> *Actual Result*
> {quote}
> Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused 
> by: Can't find resource 'solrconfig.xml' in classpath or 
> '/var/solr/data/new_core/conf'
> {quote}
> Somebody on solr-users tells me:
> {quote}
> The CoreAdmin API requires that the instanceDir already exist, with a
> conf directory inside it that contains solrconfig.xml, schema.xml, and
> any other necessary config files.
> {quote}
> Huh? Where is this magical knowledge mentioned in the [API 
> documentation|https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API]?
> Another user on the list serve says:
> {quote}
> In fact, yes. The thing to remember here is that you're using a much
> older approach that had its roots in the pre-cloud days.
> {quote}
> *The whole point of creating APIs is to abstract out details that the caller 
> doesn't need to know, and yet this API requires an understanding of Solr's 
> internal file structure and history of the project?* I'm speechless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to