[jira] [Updated] (KNOX-1066) Update Operations via SOLR to Knox Fail
[ https://issues.apache.org/jira/browse/KNOX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1066: --- Affects Version/s: 1.3.0 1.0.0 1.1.0 1.2.0 > Update Operations via SOLR to Knox Fail > > > Key: KNOX-1066 > URL: https://issues.apache.org/jira/browse/KNOX-1066 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 0.12.0, 0.13.0, 1.0.0, 1.1.0, 1.2.0, 1.3.0 >Reporter: Rick Kellogg >Assignee: Rick Kellogg >Priority: Major > Attachments: PreemptiveHttpSolrClient.java > > > When using the Java SOLRJ HttpSolrClient, any operation that relies upon a > POST HTTP operation fails authentication when proxied via Knox. This is > because the SOLRJ API only supports traditional challenge/response basic > authentication. For any update style operation the SOLRJ client refuses to > retry the operation as it might lead to duplicate data, etc. If this were a > GET operation, it would retry the operation and include the appropriate > authentication header. > Therefore preemptive authentication must be used for updates to succeed. > Unfortunately, the Apache HttpClient construction is hidden from the client > in the form of the HttpSolrClient.Builder class. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1066) Update Operations via SOLR to Knox Fail
[ https://issues.apache.org/jira/browse/KNOX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated KNOX-1066: -- Fix Version/s: (was: 0.14.0) > Update Operations via SOLR to Knox Fail > > > Key: KNOX-1066 > URL: https://issues.apache.org/jira/browse/KNOX-1066 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 0.12.0, 0.13.0 >Reporter: Rick Kellogg >Assignee: Rick Kellogg >Priority: Major > Attachments: PreemptiveHttpSolrClient.java > > > When using the Java SOLRJ HttpSolrClient, any operation that relies upon a > POST HTTP operation fails authentication when proxied via Knox. This is > because the SOLRJ API only supports traditional challenge/response basic > authentication. For any update style operation the SOLRJ client refuses to > retry the operation as it might lead to duplicate data, etc. If this were a > GET operation, it would retry the operation and include the appropriate > authentication header. > Therefore preemptive authentication must be used for updates to succeed. > Unfortunately, the Apache HttpClient construction is hidden from the client > in the form of the HttpSolrClient.Builder class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-1066) Update Operations via SOLR to Knox Fail
[ https://issues.apache.org/jira/browse/KNOX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1066: -- Component/s: (was: Server) Site > Update Operations via SOLR to Knox Fail > > > Key: KNOX-1066 > URL: https://issues.apache.org/jira/browse/KNOX-1066 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 0.12.0, 0.13.0 >Reporter: Rick Kellogg >Assignee: Rick Kellogg > Fix For: 0.14.0 > > Attachments: PreemptiveHttpSolrClient.java > > > When using the Java SOLRJ HttpSolrClient, any operation that relies upon a > POST HTTP operation fails authentication when proxied via Knox. This is > because the SOLRJ API only supports traditional challenge/response basic > authentication. For any update style operation the SOLRJ client refuses to > retry the operation as it might lead to duplicate data, etc. If this were a > GET operation, it would retry the operation and include the appropriate > authentication header. > Therefore preemptive authentication must be used for updates to succeed. > Unfortunately, the Apache HttpClient construction is hidden from the client > in the form of the HttpSolrClient.Builder class. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KNOX-1066) Update Operations via SOLR to Knox Fail
[ https://issues.apache.org/jira/browse/KNOX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1066: -- Fix Version/s: 0.14.0 > Update Operations via SOLR to Knox Fail > > > Key: KNOX-1066 > URL: https://issues.apache.org/jira/browse/KNOX-1066 > Project: Apache Knox > Issue Type: Bug > Components: Server >Affects Versions: 0.12.0, 0.13.0 >Reporter: Rick Kellogg >Assignee: Rick Kellogg > Fix For: 0.14.0 > > Attachments: PreemptiveHttpSolrClient.java > > > When using the Java SOLRJ HttpSolrClient, any operation that relies upon a > POST HTTP operation fails authentication when proxied via Knox. This is > because the SOLRJ API only supports traditional challenge/response basic > authentication. For any update style operation the SOLRJ client refuses to > retry the operation as it might lead to duplicate data, etc. If this were a > GET operation, it would retry the operation and include the appropriate > authentication header. > Therefore preemptive authentication must be used for updates to succeed. > Unfortunately, the Apache HttpClient construction is hidden from the client > in the form of the HttpSolrClient.Builder class. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KNOX-1066) Update Operations via SOLR to Knox Fail
[ https://issues.apache.org/jira/browse/KNOX-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Kellogg updated KNOX-1066: --- Attachment: PreemptiveHttpSolrClient.java > Update Operations via SOLR to Knox Fail > > > Key: KNOX-1066 > URL: https://issues.apache.org/jira/browse/KNOX-1066 > Project: Apache Knox > Issue Type: Bug > Components: Server >Affects Versions: 0.12.0, 0.13.0 >Reporter: Rick Kellogg >Assignee: Rick Kellogg > Attachments: PreemptiveHttpSolrClient.java > > > When using the Java SOLRJ HttpSolrClient, any operation that relies upon a > POST HTTP operation fails authentication when proxied via Knox. This is > because the SOLRJ API only supports traditional challenge/response basic > authentication. For any update style operation the SOLRJ client refuses to > retry the operation as it might lead to duplicate data, etc. If this were a > GET operation, it would retry the operation and include the appropriate > authentication header. > Therefore preemptive authentication must be used for updates to succeed. > Unfortunately, the Apache HttpClient construction is hidden from the client > in the form of the HttpSolrClient.Builder class. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
