[jira] Commented: (SOLR-2256) CommonsHttpSolrServer.deleteById(emptyList) causes SolrException: missing_content_stream
[ https://issues.apache.org/jira/browse/SOLR-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991191#comment-12991191 ] Stevo Slavic commented on SOLR-2256: I've experienced similar behavior with SolrJ 1.4.1 - later discovered that actual problem was that index schema was outdated, it was missing a field which was present in document. CommonsHttpSolrServer.deleteById(emptyList) causes SolrException: missing_content_stream Key: SOLR-2256 URL: https://issues.apache.org/jira/browse/SOLR-2256 Project: Solr Issue Type: Bug Components: clients - java Affects Versions: 1.4.1 Reporter: Maxim Valyanskiy Priority: Minor Call to deleteById method of CommonsHttpSolrServer with empty list causes following exception: org.apache.solr.common.SolrException: missing_content_stream missing_content_stream request: http://127.0.0.1:8983/solr/update/javabin at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:435) at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:244) at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:105) at org.apache.solr.client.solrj.SolrServer.deleteById(SolrServer.java:106) at ru.org.linux.spring.SearchQueueListener.reindexMessage(SearchQueueListener.java:89) Here is TCP stream captured by Wireshark: = POST /solr/update HTTP/1.1 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 User-Agent: Solr[org.apache.solr.client.solrj.impl.CommonsHttpSolrServer] 1.0 Host: 127.0.0.1:8983 Content-Length: 20 wt=javabinversion=1 = HTTP/1.1 400 missing_content_stream Content-Type: text/html; charset=iso-8859-1 Content-Length: 1401 Server: Jetty(6.1.3) = [ html reply skipped ] === -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (SOLR-1218) maven artifact for webapp
[
https://issues.apache.org/jira/browse/SOLR-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912429#action_12912429
]
Stevo Slavic commented on SOLR-1218:
Voted for the issue too.
As a temporary workaround, to reference solr.war but still keep solr config
files in IDE under version control, I use following config:
{code:title=pom.xml|borderStyle=solid}
...
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
configuration
stopPort${jetty.stop.port}/stopPort
stopKeyfoo/stopKey
webApp${env.SOLR_HOME}/example/webapps/solr.war/webApp
tempDirectory${project.build.directory}/jetty-tmp/tempDirectory
systemProperties
systemProperty
namesolr.solr.home/name
value${basedir}/src/main/solr/home/value
/systemProperty
systemProperty
namesolr.data.dir/name
value${project.build.directory}/solr/data/value
/systemProperty
systemProperty
namesolr_home/name
value${env.SOLR_HOME}/value
/systemProperty
/systemProperties
/configuration
executions
execution
idstart-jetty/id
phasepre-integration-test/phase
goals
goaldeploy-war/goal
/goals
configuration
daemontrue/daemon
webAppConfig
contextPath/solr/contextPath
tempDirectory${project.build.directory}/jetty-tmp/tempDirectory
/webAppConfig
connectors
connector
implementation=org.eclipse.jetty.server.nio.SelectChannelConnector
port${jetty.http.port}/port
/connector
/connectors
/configuration
/execution
execution
idstop-jetty/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
/plugin
...
{code}
And update the SOLR_HOME environment variable with move to new Solr
installation/version. This is easy for development environment, not for CI
(Hudson). That's why solr.war on public repo would be handy.
maven artifact for webapp
-
Key: SOLR-1218
URL: https://issues.apache.org/jira/browse/SOLR-1218
Project: Solr
Issue Type: New Feature
Affects Versions: 1.3
Reporter: Benson Margulies
It would be convenient to have a packagingwar/packaging maven project for
the webapp, to allow launching solr from maven via jetty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (SOLR-1977) Misplaced maven artifacts
[ https://issues.apache.org/jira/browse/SOLR-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886635#action_12886635 ] Stevo Slavic commented on SOLR-1977: Checked, works fine now. Thanks! Issue can be closed. Misplaced maven artifacts - Key: SOLR-1977 URL: https://issues.apache.org/jira/browse/SOLR-1977 Project: Solr Issue Type: Bug Components: Build Affects Versions: 1.4.1 Reporter: Stevo Slavic Maven artifacts of recently released Solr 1.4.1 at maven central repository have been uploaded to a wrong path. See related mailinglist topic for more details [here|http://lucene.472066.n3.nabble.com/Re-ANN-Solr-1-4-1-Released-td922236.html]. Maybe this can be solved by reporting issue at [Maven Evangelsim|http://jira.codehaus.org/browse/MEV] or [Maven Upload Requests|http://jira.codehaus.org/browse/MAVENUPLOAD]. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Created: (SOLR-1977) Misplaced maven artifacts
Misplaced maven artifacts - Key: SOLR-1977 URL: https://issues.apache.org/jira/browse/SOLR-1977 Project: Solr Issue Type: Bug Components: Build Affects Versions: 1.4.1 Reporter: Stevo Slavic Maven artifacts of recently released Solr 1.4.1 at maven central repository have been uploaded to a wrong path. See related mailinglist topic for more details [here|http://lucene.472066.n3.nabble.com/Re-ANN-Solr-1-4-1-Released-td922236.html]. Maybe this can be solved by reporting issue at [Maven Evangelsim|http://jira.codehaus.org/browse/MEV] or [Maven Upload Requests|http://jira.codehaus.org/browse/MAVENUPLOAD]. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
