RE: adding documents to a secured solr server.

2017-11-02 Thread Phil Scadden
Yes, that worked. -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: Thursday, 2 November 2017 6:14 p.m. To: solr-user@lucene.apache.org Subject: Re: adding documents to a secured solr server. On 11/1/2017 10:04 PM, Phil Scadden wrote: > For testing, I changed

Re: adding documents to a secured solr server.

2017-11-01 Thread Shawn Heisey
On 11/1/2017 10:04 PM, Phil Scadden wrote: For testing, I changed to HttpSolrClient and specifying the core on process and commit instead of opening it as server/core. This time worked... sort of. Despite deleting the entire index with deletebyquery and seeing that it was empty in the coreAdmi

RE: adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
November 2017 5:04 p.m. To: solr-user@lucene.apache.org Subject: RE: adding documents to a secured solr server. For testing, I changed to HttpSolrClient and specifying the core on process and commit instead of opening it as server/core. This time worked... sort of. Despite deleting the entire index

RE: adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
ess to the server. This is a frustrating problem. -Original Message- From: Shawn Heisey [mailto:elyog...@elyograg.org] Sent: Thursday, 2 November 2017 3:55 p.m. To: solr-user@lucene.apache.org Subject: Re: adding documents to a secured solr server. On 11/1/2017 8:13 PM, Phil Scadden wrot

RE: adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
: adding documents to a secured solr server. On 11/1/2017 8:13 PM, Phil Scadden wrote: > 14:52:45,962 DEBUG ConcurrentUpdateSolrClient:177 - starting runner: > org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner@6e > eba4a > 14:52:46,224 WARN ConcurrentUpdateSolrClient:343

Re: adding documents to a secured solr server.

2017-11-01 Thread Shawn Heisey
On 11/1/2017 8:13 PM, Phil Scadden wrote: 14:52:45,962 DEBUG ConcurrentUpdateSolrClient:177 - starting runner: org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner@6eeba4a 14:52:46,224 WARN ConcurrentUpdateSolrClient:343 - Failed to parse error response from http://online-dev.gn

Re: adding documents to a secured solr server.

2017-11-01 Thread Shawn Heisey
On 11/1/2017 7:59 PM, Phil Scadden wrote: After some digging, I tried this approach... solr = new ConcurrentUpdateSolrClient.Builder(solrUrl) .withQueueSize(20) .build(); SolrInputDocument up = new SolrInputDocument(); up.addFiel

RE: adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
w UpdateRequest(); up.setBasicAuthCredentials("solrAdmin",password); up.deleteByQuery("*:*"); up.setCommitWithin(1000); up.process(solr); -Original Message- From: Phil Scadden [mailto:p.scad...@gns.cri.nz] Sent: Thursday, 2 No

RE: adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
om: Phil Scadden [mailto:p.scad...@gns.cri.nz] Sent: Thursday, 2 November 2017 11:28 a.m. To: solr-user@lucene.apache.org Subject: adding documents to a secured solr server. Solrj QueryRequest object has a method to set basic authorization username/password but what is the equivalent way to p

adding documents to a secured solr server.

2017-11-01 Thread Phil Scadden
Solrj QueryRequest object has a method to set basic authorization username/password but what is the equivalent way to pass authorization when you are adding new documents to an index? ConcurrentUpdateSolrClient solr = new ConcurrentUpdateSolrClient(solrProperties.getServer(),10,2); ...