g/core/8_8_0/changes/Changes.html
- -----
Noble Paul
-BEGIN PGP SIGNATURE-
Version: FlowCrypt Email Encryption 8.0.0
Comment: Seamlessly send and receive encrypted email
wsFzBAEBCgAGBQJgF/RnACEJEMOP9ew/z9s+FiEEz85fu5IMPHRc7uCEw4/1
7D/P
and if it is a critical feature for users.
> >
> > Another possibility is to offer a replacement for the feature using a
> > different API
> >
> > Your feedback will help us decide on what a potential solution should be
> >
> > --
> > -
> > Noble Paul
>
feedback will help us decide on what a potential solution should be
--
-
Noble Paul
ns
> > > > > > added to stats, facet and time series. Streaming expressions
> > added to
> > > > > > /export handler. Drill Streaming Expression for efficient and
> > accurate
> > > > > > high cardinality aggregation.
> > > > > >
> > > > > > * Package manager: Support for cluster (CoreContainer) level
> > plugins.
> > > > > >
> > > > > > * Health Check: HealthCheckHandler can now require that all cores
> > are
> > > > > > healthy before returning OK.
> > > > > >
> > > > > > * Zookeeper read API: A read API at /api/cluster/zk/* to fetch
> > raw ZK
> > > > > > data and view contents of a ZK directory.
> > > > > >
> > > > > > * Admin UI: New panel with security info in admin UI's dashboard.
> > > > > >
> > > > > > * Query DSL: Support for {param:ref} and {bool: {excludeTags:""}}
> > > > > >
> > > > > > * Ref Guide: Major redesign of Solr's documentation.
> > > > > >
> > > > > >
> > > > > > Please read CHANGES.txt for a full list of new features and
> > changes:
> > > > > >
> > > > > >
> > > > > > <https://lucene.apache.org/solr/8_6_0/changes/Changes.html>
> > > > > >
> > > > > >
> > > > > > Solr 8.6.0 also includes features, optimizations and bugfixes in
> > the
> > > > > > corresponding Apache Lucene release:
> > > > > >
> > > > > >
> > > > > > <https://lucene.apache.org/core/8_6_0/changes/Changes.html>
> > > > > >
> > > > > >
> > > > > > Note: The Apache Software Foundation uses an extensive mirroring
> > > > network
> > > > > > for
> > > > > >
> > > > > > distributing releases. It is possible that the mirror you are
> > using may
> > > > > > not have
> > > > > >
> > > > > > replicated the release yet. If that is the case, please try another
> > > > mirror.
> > > > > >
> > > > > > This also applies to Maven access.
> > > > > >
> > > >
> >
--
-
Noble Paul
eplication requests from the
> > slave.
> >
> > Delegator/handler is a common pattern, but it is not the pattern
> > that describes traditional Solr replication.
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org
> > http://observer.wunderwood.org/ (my blog)
> >
> >
--
-
Noble Paul
veryone just pitch in and do it on this list.
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org
> > http://observer.wunderwood.org/ (my blog)
> >
> >
--
-
Noble Paul
I really do not see a reason why a master/slave terminology is a problem.
We do not have slavery anywhere in the world. Should we also remove it from
the dictionary?
The old mode is going to go away anyway. Why waste time bikeshedding on
this?
On Thu, Jun 18, 2020, 12:04 PM Trey Grainger wrote:
-- Forwarded message -
From: Noble Paul
Date: Tue, Apr 28, 2020, 4:40 PM
Subject: [ANNOUNCE] Apache Solr 7.7.3 released
To:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
28 April 2020, Apache Solr™ 7.7.3 available
The Lucene PMC is pleased to announce the release of Apache
Thanks ishan
On Wed, Dec 4, 2019, 3:32 PM Ishan Chattopadhyaya
wrote:
> ## 3 December 2019, Apache Solr™ 8.3.1 available
>
> The Lucene PMC is pleased to announce the release of Apache Solr 8.3.1.
>
> Solr is the popular, blazing fast, open source NoSQL search platform
> from the Apache Lucene p
query response such as
> facet. Are there any other options available?
>
> Thanks,
> Wei
--
-
Noble Paul
Thanks Colvin.
Can you share the details in the ticket?
I plan to debug this today.
It's unlikely to be a synchronization issue because
serialization/deserialization usually happens in single thread.
On Sun, Nov 24, 2019, 4:09 AM Colvin Cowie
wrote:
> https://issues.apache.org/jira/browse/SOLR
must be something in ours (or
> something missing from it) that is making the problem appear, in
> combination with the code change.
>
> Thanks
>
>
> On Wednesday, 20 November 2019, Noble Paul wrote:
>
> > Can you share the test please
> >
> > On Thu, Nov 21, 2
Can you share the test please
On Thu, Nov 21, 2019 at 7:02 AM Noble Paul wrote:
>
> Thanks Colvin, I'll take a look
>
> On Thu, Nov 21, 2019 at 4:24 AM Colvin Cowie
> wrote:
> >
> > I've identified the change which has caused the problem to materialize
printable characters are part of it)
> >
> > So far we've not been able to reproduce the problem on a collection with a
> > single shard, so it does seem like the problem is only happening internally
> > when updates are distributed to the other shards... But that's not been
> > totally verified.
> >
> > We've also only encountered the problem on one of the collections we build
> > (the data within each collection is generally the same though. The ids are
> > slightly different - but still strings. The main difference is that this
> > problematic index is built using an Iterator to *solrj
> > org.apache.solr.client.solrj.SolrClient.add(String,
> > Iterator)* - the *SolrInputDocument*s are not being
> > reused in the client, I checked that -, while the other index is built by
> > streaming CSVs to Solr.)
> >
> >
> > We will look into it further, but if anyone has any ideas of what might
> > have changed in 8.3 from 8.1 / 8.2 that could cause this, that would be
> > helpful.
> >
> > Cheers
> > Colvin
> >
> >
--
-
Noble Paul
How are you consuming the output? Are you using solrj?
On Tue, Jun 18, 2019, 1:27 AM Andy Reek wrote:
> Hi Solr team,
>
>
> we are using Solr in version 7.1 as search engine in our online shop (SAP
> Hybris). And as a task I needed to migrate to the most recent Solr in
> version 7 (7.7). Doing t
y. I don't want to make many changes as this is part of our
> production at this time.
>
>
>
>
>
> From: Noble Paul
>
> Sent: Wednesday, September 4, 2019 12:14 AM
>
> To: solr-user@lucene.apache.org
>
> Subject: Re: Solr 7.7.2 Autoscaling policy - Poor
s. If you are not the intended recipient, or believe that you
> have received this communication in error, please do not read, print, copy,
> retransmit, disseminate, or otherwise use the information. Please delete this
> email and attachments, without reading, printing, copying, forwarding or
> saving them, and notify the Sender immediately by reply email. No
> confidentiality or privilege is waived or lost by any transmission in error.
--
-
Noble Paul
blem doing it this way.
>
> ... and that this is precisely what I do _not_ want to do,
> unless I have to.
>
> I want to use a JAR file uploaded to the collection's znode,
> as the user guide strongly suggests is possible.
> (And also again, no, I don't want to configure/use the Blob Store.)
>
--
-
Noble Paul
uestion is, how can I optimize this? Is there any kind of "bulk" or
> > "transaction-base" way of doing schema configuration? I.e.: send all my
> > deletes, followed with all my adds, and then issue a commit for the change
> > to take effect. If I switch to SolrJ (does it offer schema management?)
> > will that help?
> >
> > Thanks in advanced.
> >
> > Steve
>
--
-
Noble Paul
>
> - Toke Eskildsen, Royal Danish Library
>
>
--
-----
Noble Paul
ath": "/admin/file", "role": ["
> collection_user"]}
>
> I am still not able to restrict another user from accessing other
> collection files like solrconfig, solr-data-config etc.
>
> If it possible to define permission at collection-level to this path?
>
> Thanks,
> Antony
--
-
Noble Paul
he.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:481)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient$1.call(HttpSolrClient.java:284)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient$1.call(HttpSolrClient.java:280)
> ... 5 more
> Caused by: javax.crypto.IllegalBlockSizeException: Invalid input.
> at com.rsa.cryptoj.o.fy.engineDoFinal(Unknown Source)
> at javax.crypto.Cipher.doFinal(Unknown Source)
> at
> org.apache.solr.util.CryptoKeys$RSAKeyPair.encrypt(CryptoKeys$RSAKeyPair.java:63)
> ... 17 more
>
> I appreciate any suggestions you can offer.
>
> Thanks,
> Adam
--
-
Noble Paul
n of Solr that this would work with
> three instances of Solr running on each server?
>
> If so how?
>
> Thanks again for your help.
>
> On 9/26/18, 9:11 AM, "Noble Paul" wrote:
>
> I'm not sure if it is pertinent to ask you to move to the latest Solr
ving replicas of shard do you have a suggestion of
> how one might accomplish the multiple availability zone with multiple
> instances of Solr running on each server?
>
> Thanks
>
> On 9/26/18, 12:56 AM, "Noble Paul" wrote:
>
> The rules suggested by Steve
t; instances that each have a smaller heap, and divide their indexes between
> > them. In my opinion, when you have enough index data on an instance that it
> > requires a huge heap, instead of running two or more instances on one
> > server, it's time to add more servers.
> >
> > Thanks,
> > Shawn
> >
--
-
Noble Paul
ode. However, the other rule should
> prevent this: {"replica": "<2", "shard": "#EACH", "node": "#ANY"}
> So by using both rules, that should mean "no more than six replicas on a
> node, where all the replicas on that nod
:false}
> etc
> So having more than one RF in an AZ is a technical “violation”, but if
> placement minimizes non-strict violations, replicas would tend to get placed
> correctly.
>
>
> Given a working set of rules, I’m still having trouble with two things:
>
> 1. I’ve manually created the “.system” collection, as it didn’t seem to
> get created automatically. However, autoscaling activity is not getting
> logged to it.
> 2. I can’t seem to figure out how to scale up.
> * I’d presumed editing the collection’s “replicationFactor” would do
> the trick, but it does not.
> * The “node-up” trigger will serve to replace lost replicas, but won’t
> otherwise take advantage of additional capacity.
>
>i.
> There’s a UTILIZENODE command in 7.2, but it appears that’s still something
> you need to trigger manually.
>
> Anyone played with this stuff?
--
-
Noble Paul
ges.html or in the
>> >> CHANGES.txt file accompanying the release.
>> >>
>> >> Solr 7.1 also includes many other new features as well as numerous
>> >> optimizations and bugfixes of the corresponding Apache Lucene release.
>> >>
>> >> Please report any feedback to the mailing lists
>> >> (http://lucene.apache.org/solr/discussion.html)
>> >>
>> >> Note: The Apache Software Foundation uses an extensive mirroring
>> >> network for distributing releases. It is possible that the mirror you
>> >> are using may not have replicated the release yet. If that is the
>> >> case, please try another mirror. This also goes for Maven access.
>> >>
>> >> --
>> >> Regards,
>> >> Shalin Shekhar Mangar.
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> >> For additional commands, e-mail: dev-h...@lucene.apache.org
>> >>
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
--
-
Noble Paul
tor "~" it not set.
>>>>
>>>> The result of the call is:
>>>> shard1 --> server2:7574 / server1:8983
>>>> shard2 --> server1:7574 / server3:8983
>>>> shard3 --> server2:8983 / server3:7574
>>>>
>>>> The expected result should be (at least!!!) shard1 --> server_x:8983 /
>>>> server_y:8983
>>>> where "_x" and "_y" can be anything between 1 and 3 but must be different.
>>>>
>>>> I think the problem is somewhere in "class ReplicaAssigner" with
>>>> "tryAllPermutations"
>>>> and "tryAPermutationOfRules".
>>>>
>>>> Regards
>>>> Bernd
>>>>
>>>
--
-
Noble Paul
System.out.println("successful"+ Utils.toJSON(res.asMap(5)));
seems to work for me.
which version of Solr and SolrJ are you using
On Sun, Apr 16, 2017 at 11:40 AM, Zheng Lin Edwin Yeo
wrote:
> Ok, thank you.
>
> Regards,
> Edwin
>
> On 15 April 2017 at 08:05, Noble Paul wrote:
grF8c="}
> },
> "authorization":{
>"class":"solr.RuleBasedAuthorizationPlugin",
>"user-role":{"solr":"admin"},
>"permissions":[{"name":"security-edit",
> &
ient.solrj.SolrClient.commit(SolrClient.java:484)
> at org.apache.solr.client.solrj.SolrClient.commit(SolrClient.java:463)
> at testing.indexing(testing.java:3063)
> at testing.main(testing.java:329)
>
> Regards,
> Edwin
>
>
> On 12 April 2017 at 14:28, Noble Paul wro
;> This will caused a null pointer exception.
>> Exception in thread "main" java.lang.NullPointerException
>>
>> How should we go about putting these codes, so that the error can be
>> prevented?
>>
>> Regards,
>> Edwin
>>
>>
--
-
Noble Paul
I think it's a reasonable
> approach or am I missing something?
>
> Thanks!
--
-----
Noble Paul
303933.html
> Sent from the Solr - User mailing list archive at Nabble.com.
--
-----
Noble Paul
t;
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Custom-auth-plugin-not-loaded-in-SolrCloud-tp4245670p4248340.html
> Sent from the Solr - User mailing list archive at Nabble.com.
--
-----
Noble Paul
A 5.3.2 release is coming up which will back port the fixes introduced in
5.4
On Dec 17, 2015 10:25 PM, "tine-2" wrote:
> Noble Paul നോബിള് नोब्ळ् wrote
> > It works as designed.
> >
> > Protect the read path [...]
>
> Works like described in 5.
I have opened https://issues.apache.org/jira/browse/SOLR-8429
On Wed, Dec 16, 2015 at 9:32 PM, Noble Paul wrote:
> I don't this behavior is intuitive. It is very easy to misunderstand
>
> I would rather just add a flag to "authentication" plugin section
> which says &q
, unless assigned proper roles
> 3) if a user is assigned the default “read” rule, and a collection adds a
> custom “/myselect” handler, that one is unavailable until the user gets it
> assigned
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.co
--
> soledede_w...@ehsy.com
>
--
-----
Noble Paul
ult in a security breach like today.
>
> /Jan
--
-----
Noble Paul
gt;
> -Dsolr.security.mode=open : As today - paths not configured are wide
> open
> -Dsolr.security.mode=authenticated : Paths not configured are open to any
> authenticated user
> -Dsolr.security.mode=explicit : Paths not configured are closed to all.
> All acccess is explicitly configured
>
> /Jan
--
-
Noble Paul
other else.
>>
>>
>>
>>--
>>View this message in context:
>>http://lucene.472066.n3.nabble.com/how-to-secure-standalone-solr-tp4244866.html
>>Sent from the Solr - User mailing list archive at Nabble.com.
>
--
-
Noble Paul
option.
>
>
> On Fri, Dec 11, 2015 at 8:06 PM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
>> Shouldn't this be the znode version? Why put a version in
>> security.json? Or is the idea that the user will upload security.json
>> only once a
uld expect that the behavior is the same as with invalid
> credentials. Is there a special reason why it behaves like this? I’m
> wondering because I’m working on a custom authentication plugin and was
> looking into the existing ones to understand how they work.
> :
> : Thanks,
> :
> : tine
>
> -Hoss
> http://www.lucidworks.com/
--
-
Noble Paul
components with the Authentication API and the Authorization API (in a
>> script, if one wants to automate the process: although such a script would
>> have to include plain-text passwords)?
>>
>> I figured there is no harm in asking.
>>
>
>
>
> --
> Anshum Gupta
--
-
Noble Paul
those served by Jetty)?
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>> 18. nov. 2015 kl. 20.31 skrev Upayavira :
>>
>> I'm very happy for the admin UI to be served another way - i.e. not
>> direct from Jetty, if that
://gist.github.com/janhoy/d18854c75461816fb947
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>> 18. nov. 2015 kl. 14.54 skrev Noble Paul :
>>
>> As of now the admin-ui calls are not protected. The static calls are
>> served
create the permission called 'admin-ui' and protect
> everything under /admin/ui/ for example? Along with the root HTML link
> too.
>
> Upayavira
>
> On Wed, Nov 18, 2015, at 07:46 AM, Noble Paul wrote:
>> The authentication plugin is not expensive if you are talkin
r
>> apis/resources
>> > > secure not towards securing/controlling data during search.
>> > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/display/solr/Authentication+and+Authorization+Plugins
>> > >
>> > >
>> > > Please share your thoughts.
>> > >
>> > > Thanks,
>> > > Susheel
>> > >
>> >
>> >
>> >
>> > --
>> > Scott Stults | Founder & Solutions Architect | OpenSource Connections,
>> LLC
>> > | 434.409.2780
>> > http://www.opensourceconnections.com
>> >
>>
>>
>>
>> --
>> --
>>
>> Benedetti Alessandro
>> Visiting card : http://about.me/alessandro_benedetti
>>
>> "Tyger, tyger burning bright
>> In the forests of the night,
>> What immortal hand or eye
>> Could frame thy fearful symmetry?"
>>
>> William Blake - Songs of Experience -1794 England
>>
--
-
Noble Paul
;> > see the UI would be more conventional, and therefore lead to less
>> > confusion. Is it possible for us to protect the UI static files, only
>> > for the sake of user experience, rather than security?
>> >
>> > Upayavira
>> >
>> > On Tue, Nov 10, 20
window and says
> "the server http://(my host):8983 requires a username and password"
--
-----
Noble Paul
min UI stats page
Known issues:
* On Windows, bin/solr.cmd script fails to start correctly when using
relative path with -s parameter. Use absolute path as a workaround .
https://issues.apache.org/jira/browse/SOLR-8073
See the CHANGES.txt file included with the release for a full list of
cha
Wrong title
On Thu, Sep 24, 2015 at 10:55 PM, Noble Paul wrote:
> 24 September 2015, Apache Solr™ 5.3.1 available
>
>
> The Lucene PMC is pleased to announce the release of Apache Solr 5.3.1
>
>
> Solr is the popular, blazing fast, open source NoSQL search platform
>
release yet. If that is the
case, please try another mirror. This also goes for Maven access.
Noble Paul
on behalf of Lucene PMC
;
>>> ERROR: Failed to get system information from http://localhost:8983/solr
>>> due
>>> to: org.apache.http.client.ClientProtocolException: Expected JSON response
>>> from server but received:
>>>
>>>
>>>
>>>
>>>
>>> Error 401 Unauthorized
>>>
>>>
>>>
>>> HTTP ERROR 401
>>>
>>> Problem accessing /solr/admin/info/system. Reason:
>>>
>>> UnauthorizedPowered by
>>> Jetty://
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
--
-
Noble Paul
ectly running system with solr
> 3.x and one core and now taking it to solr cloud 5.2.x into production
> seems to be stoped by simple authorization problems.
>
> Thank you in advane for any help.
>
>
>
> 2015-09-10 20:42 GMT+02:00 Noble Paul :
>
>> Check this https:
sic Authentification?
>
> Thank you for any help
--
-----
Noble Paul
json after startup of the Solr instances. If I shutdown and bring
>> the instances back up, the security is no longer in place and I have to
>> upload the security.json again for it to take effect.
>>
>> - Kevin
>>
>> > On Sep 3, 2015, at 10:29 PM, Noble Paul wr
Both these are committed. If you could test with the latest 5.3 branch
it would be helpful
On Wed, Sep 2, 2015 at 5:11 PM, Noble Paul wrote:
> I opened a ticket for the same
> https://issues.apache.org/jira/browse/SOLR-8004
>
> On Wed, Sep 2, 2015 at 1:36 PM, Kevin Lee wrote:
&
ions aren’t working, but the one to the
> request handler at the /browse path is.
>
>
>> On Sep 1, 2015, at 11:03 PM, Noble Paul wrote:
>>
>> " However, after uploading the new security.json and restarting the
>> web browser,"
>>
>> The browser rememb
]
> }
> }
> }
>
> Also tried adding the permission using the Authorization API, but no effect,
> still isn’t protecting the Collections API from being invoked without a
> username password. I do see in the Solr logs that it sees the updates
&
Looks like there is a bug in that . On start/restart the security.json
is not loaded
I shall open a ticket
https://issues.apache.org/jira/browse/SOLR-8000
On Tue, Sep 1, 2015 at 1:01 PM, Noble Paul wrote:
> I'm investigating why restarts or first time start does not read the
> se
I'm investigating why restarts or first time start does not read the
security.json
On Tue, Sep 1, 2015 at 1:00 PM, Noble Paul wrote:
> I removed that statement
>
> "If activating the authorization plugin doesn't protect the admin ui,
> how does one protect access to it
n't see
> any plugin enabled even though security.json is already in zookeeper and then
> after they are started and the security.json is uploaded again I see it
> reconfigure to use the plugin.
>
> Thanks,
> Kevin
>
>> On Aug 31, 2015, at 11:22 PM, Noble Paul wrote:
tion/json' -d '{"set-user": {"user" : “password" }}'
>>
>> Issue the following command to add permission to users
>> curl -u solr:SolrRocks -H 'Content-type:application/json' -d '{
>> "set-user-role" : {"admin": ["search-user", "admin"]}}'
>> http://localhost:8983/solr/admin/authorization
>> curl -u solr:SolrRocks -H 'Content-type:application/json' -d '{
>> "set-user-role" : {"user": ["search-user"]}}'
>> http://localhost:8983/solr/admin/authorization
>>
>> After executing the above, access to /mysearch is protected until I restart
>> the Solr and Zookeeper instances. However, the admin UI is never protected
>> like the Wiki page says it should be once activated.
>>
>> https://cwiki.apache.org/confluence/display/solr/Rule-Based+Authorization+Plugin
>>
>> <https://cwiki.apache.org/confluence/display/solr/Rule-Based+Authorization+Plugin>
>>
>> Why does the authentication and authorization plugin not stay activated
>> after restart and why is the Admin UI never protected? Am I missing any
>> steps?
>>
>> Thanks,
>> Kevin
--
-
Noble Paul
ing lists
(http://lucene.apache.org/solr/discussion.html)
--
-----
Noble Paul
www.lucidworks.com
sorry , screwed up the title
On Tue, Aug 25, 2015 at 8:30 AM, Noble Paul wrote:
> Solr is the popular, blazing fast, open source NoSQL search platform
> from the Apache Lucene project. Its major features include powerful
> full-text search, hit highlighting, faceted search, dynamic
>
ing lists
(http://lucene.apache.org/solr/discussion.html)
--
-----
Noble Paul
www.lucidworks.com
no.
Most of it is in Solr 5.3
On Tue, Aug 25, 2015 at 12:48 AM, Steven White wrote:
> Hi Noble,
>
> Is everything in the link you provided applicable to Solr 5.2.1?
>
> Thanks
>
> Steve
>
> On Mon, Aug 24, 2015 at 2:20 PM, Noble Paul wrote:
>
>> did you m
>
>
>
> --
> Arcadius Ahouansou
> Menelic Ltd | Information is Power
> M: 07908761999
> W: www.menelic.com
> ---
--
-
Noble Paul
. I’ve found some examples on user authentication on the Jetty side.
> But they have failed.
>
> Does any one have a step by step example on authentication for the admin
> screen? And a core?
>
>
> Thanks
>
> Tom LeZotte
> Health I.T. - Senior Product Developer
> (p) 615-875-8830
>
>
>
>
>
>
>
--
-
Noble Paul
out of
> other things since I see many mails usually in consensus of not embedding and
> rather want people to consider Solr as a stand-alone service, not sure why!
> I'm probably getting out of context here.
>
> Regards
>
>> On 27 Jul 2015, at 13:17, Noble Paul
own security.json + class/implementation to verify user/pass
> should work today with 5.2, right?
>
> Thanks
> Fadi
>
>> On 22 Jul 2015, at 14:33, Noble Paul wrote:
>>
>> Solr 5.3 is coming with proper basic auth support
>>
>>
>> https://issue
>>
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/Basic-auth-tp4218053p4218519.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
--
-
Noble Paul
rain hurt. You probably
> know a lot more about the code for those areas than I do.
>
> Thanks,
> Shawn
>
>
--
-
Noble Paul
... 56 common frames omitted
>
> Look like the exception occurs in the ConfigOverlay static block, line 213:
> editable_prop_map = (Map)new ObjectBuilder(new JSONParser(new
> StringReader(
> MAPPING))).getObject();
>
> What is happening?
>
--
-
Noble Paul
> searching.
> >>
> >> What is the proper way to perform this backup-restore task?
> >>
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> http://lucene.472066.n3.nabble.com/Backuping-SolrCloud-tp4170624.html
> >> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
-
Noble Paul
thanks.
>
> Msj
>
--
-----
Noble Paul
check https://issues.apache.org/jira/browse/SOLR-6633
On Fri, Oct 17, 2014 at 5:35 PM, Alexandre Rafalovitch
wrote:
> I wonder how hard it would be to write an URP to just copy JSON from the
> request into a store-only field?
>
> Regards,
> Alex
> On 17/10/2014 1:21 am, &
t; Thanks again,
> Scott
>
> On Thu, Oct 16, 2014 at 2:10 PM, Noble Paul wrote:
>
> > The end point /update/json/docs is enabled implicitly in Solr
> irrespective
> > of the solrconfig.xml
> > In schemaless the fields are created automatically by solr.
> &
st way to get this feature up and
> running quickly and is this documented somewhere? I'm trying to do a quick
> proof-of-concept to verify that we can move from our current flat JSON
> ingestion to a more natural use of structured JSON.
>
> Thanks,
> Scott Dawson
>
--
-
Noble Paul
have modified the JsonLoader to accept complicated json documents with
>>> arrays/objects as values.
>>>
>>> It stores the object/array and then flatten it and indexes the fields.
>>>
>>> e.g basic example document
>>>
>>> {
>>> "titles_json":{"FR":"This is the FR title" , "EN":"This is the EN
>>> title"} ,
>>> "id": 103,
>>> "guid": "3b2f2998-85ac-4a4e-8867-beb551c0b3c6"
>>> }
>>>
>>> It will store titles_json:{"FR":"This is the FR title" , "EN":"This is
>>> the
>>> EN title"}
>>> and then index fields
>>>
>>> titles.FR:"This is the FR title"
>>> titles.EN:"This is the EN title"
>>>
>>>
>>> Do you see any problems with this approach?
>>>
>>>
>>>
>>> Regards,
>>> Michael Pitsounis
>>>
>>
>>
--
-
Noble Paul
is creating cores per client. So I have 400
> > cores
> > > already.
> > >
> > > Is this a good idea to do ?
> > >
> > > What is the general practice for creating cores
> > >
> >
> >
> I have a single machine 16GB Ram with 16 cpu cores
>
> What is the h/w you are using
>
--
-
Noble Paul
ion records every 2 months.
>
> What I am currently doing is creating cores per client. So I have 400 cores
> already.
>
> Is this a good idea to do ?
>
> What is the general practice for creating cores
>
--
-----
Noble Paul
http://lucene.472066.n3.nabble.com/Hash-range-to-shard-assignment-tp4091204p4091591.html
> Sent from the Solr - User mailing list archive at Nabble.com.
--
-----
Noble Paul
s be supported ?
>
> Regards,
> Lochri
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Hash-range-to-shard-assignment-tp4091204p4091503.html
> Sent from the Solr - User mailing list archive at Nabble.com.
--
-
Noble Paul
091204.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
-
Noble Paul
07-01 16:45:57.317;
> org.apache.solr.handler.dataimport.DataImporter; Starting Full Import
> WARN - 2013-07-01 16:45:57.333;
> org.apache.solr.handler.dataimport.SimplePropertiesWriter; Unable to read:
> dataimport.properties
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/dataconfig-to-index-ZIP-Files-tp4073965p4074399.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
-
Noble Paul
ty.
>
> It would be great if you could just sketch the setup with the entities I
> provided. Because currently I have no idea on how to do it.
>
> Regards
>
> Constantin
>
>
> -Ursprüngliche Nachricht-
> Von: Noble Paul നോബിള് नोब्ळ् [mailto:noble.p...@gmail.com
gt;
> The following solutions would be possible in my opinion:
>
> 1. Is there any way to tell the config to ignore the Cache when running a
> delta import? That would help already because we are talking about the
> maximum of 500 documents changed in 15 minutes compared to over 5 million
> documents in total.
> 2. Get solr to not refresh the cash for every document.
>
> Best Regards
>
> Constantin Wolber
>
>
--
-
Noble Paul
06-1:)
> Closing out SolrRequest: {command=indexversion}
>
> -Ursprüngliche Nachricht-
> Von: Noble Paul നോബിള് नोब्ळ् [mailto:noble.p...@gmail.com]
> Gesendet: Dienstag, 11. Juni 2013 13:41
> An: solr-user@lucene.apache.org
> Betreff: Re: Replication not working
>
> Y
> On Slave:
>
>0
>0
>0
>1
>
>
> > pollInterval is set to 2 minutes. It is usually long
>
> I know ;-)
>
>
> -Ursprüngliche Nachricht-
> Von: Noble Paul നോബിള് नोब्ळ् [mailto:noble.p...@gmail.com]
> Gesen
"_1r_Lucene41_0.doc",
> "_1r_Lucene41_0.pos",
> "_1r_Lucene41_0.tim",
> "_1r_Lucene41_0.tip",
> "segments_1h"]]],
> "isMaster":"true",
> "isSlave":"false",
> "indexVersion":1370612995391,
> "generation":53,
> "master":{
> "confFiles":"stopwords.txt, solrconfig.xml",
> "replicateAfter":["commit",
> "startup"],
> "replicationEnabled":"true",
> "replicableVersion":1370612995391,
> "replicableGeneration":53}},
> "WARNING":"This response format is experimental. It is likely to
> change in the future."}
>
>
>
>
>
> Any idea how we could go on?
>
>
>
> Regards
>
> Thomas
>
>
>
>
--
-
Noble Paul
I did a couple of quick searches and found mostly older wikis that say
> solr replication will change in the future. Would you be able to point
> me to the right one?
>
>
> -
>
> On Fri, Jun 7, 2013 at 8:34 PM, Noble Paul നോബിള് नोब्ळ्
> wrote:
> > We set it up like
We set it up like this
+ individual solr instances are setup
+ external mapping/routing to allocate users to instances. This information
can be stored in an external data store
+ all cores are created as transient and loadonstart as false
+ cores come online on demand
+ as and when users data get b
way to get output in proper format.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SOLR-CSV-output-in-custom-order-tp4068527.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
---
overall status of the
> effort?
>
> Thank you in advance,
>
> Aleksey
>
--
-
Noble Paul
Actually , It's pretty high end for most of the users. Rishi, u can post
the real h/w details and our typical deployment .
No :of cpus per node
No :of disks per host
Vms per host
Gc params
No :of cores per instance
Noble Paul
Sent from phone
On 21 May 2013 01:47, "Rishi Easwaran"
binary format
> > SolrJ is
> > using. Can you point me to an URL if any?
>
> may be this?
> https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/response/BinaryResponseWriter.java
>
--
-----
Noble Paul
1 - 100 of 1149 matches
Mail list logo
