Re: empty strings outputting to numeric field types

: fields storing dollar values as tdouble. they don't always exist in the : outputted rows, however, at which point they throw an error and fail at : indexing because the field is seen as an empty string (the log message: str : = ''). : : for now i've gotten around this by skipping out of any out

Re: _version_ as LongPointField returns error

just replying to some comments/discussion in general rather then individual msgs/sentences.. * uninversion/FieldCache of *singlevalued* Points fields was fixed in SOLR-10472 * currently a bad idea to use indexed="true" Points for _version_ due to SOLR-10832 * AFAICT it's a good idea (in gener

Re: Swapping indexes on disk

Are you physically swapping the disks to introduce the new index? Or having both disks mounted at the same time? If the disks are simultaneously available, can you just swap the cores and then delete the core on the old disk? https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API#CoreAdmin

Re: Solr 6: how to get SortedSetDocValues from index by field name

https://people.apache.org/~hossman/#xyproblem XY Problem Your question appears to be an "XY Problem" ... that is: you are dealing with "X", you are assuming "Y" will help you, and you are asking about "Y" without giving more details about the "X" so that we can understand the full issue. Perhaps

Re: Live update the zookeeper for SOLR

of the rest. It went down, and that resulted in the solr instance being inaccessible since it can't find the rest of the zk ensemble. Best, Chris On Fri, Jun 16, 2017 at 11:05 AM Xie, Sean wrote: > Is there a way to keep SOLR alive when zookeeper instances (3 instance > ensembl

Re: IndexSchema uniqueKey is not stored

Markus: I'm 95% certain that as long as the uniqueKey (effectively) has useDocValuesAsStored everything should still work and it's just the error checking/warning that's broken -- if you want to test that out and file a jira that would be helpful. the one concern i have is that a deliberate ch

Re: Problem in documentation -- authentication JSON fails validation

I haven't actually tested it, but I believe the JSON should probably be this: { "set-permission": {"name": "update", "role":"dev"}, "set-permission": {"name": "read", "role":"guest"} } It's missing closing double quotes for 'update' and 'read' and had an extra comma after the 'guest' entry.

Re: Same score for different length matches

: we have multiple documents that are matches for the query in question : ("name:hubwagen"). Thing is, some of the documents only contain the : query, while others match 100% in the "name" field: ... : 5.9861565 = (MATCH) weight(name:hubwag in 8093) [DefaultSimilarity], : result of: : 5.9

Re: custom search component process method not called

: : I believe the init bit is called on startup, so that leaves the second : part of your puzzle. I find this a bit suspicious though: : :${solr.core.name} : : Are you sure this is different for all three cores? My thought is that : the component is being called for all three cores but it's

RE: [EXTERNAL] - Re: custom search component process method not called

the type of purpose you are using it for. : : : -S : : -Original Message- : From: Chris Hostetter [mailto:hossman_luc...@fucit.org] : Sent: Friday, June 30, 2017 1:34 PM : To: solr-user : Subject: [EXTERNAL] - Re: custom search component process method not called : : : : : : I believ

Inconsistency in results between replicas using CloudSolrClient

nate the scenario in question from occurring? Thanks, Chris

Re: Inconsistency in results between replicas using CloudSolrClient

automated tests so I anticipate this likely causing issues. I'll give it some more thought and see if I can come up with any other workarounds. -Chris On Tue, Aug 1, 2017 at 5:38 PM, Erick Erickson wrote: > You're understanding is correct. > > As for how people cope? Mostly

Get handler failure

ave been a temporary connectivity issue that we're unaware of and the request couldn't find the document and returned null. So is that a possibility, and are there any other circumstances where the /get handler would not be able to return a document that exists in a collection? Thanks, Chris

Re: Get handler failure

would be useful. We're running Solr 6.3.0 on Ubuntu 16.04 virtual machines. On Thu, Aug 3, 2017 at 9:18 AM Shawn Heisey wrote: > On 8/3/2017 6:30 AM, Chris Ulicny wrote: > > I've run into an issue in a test environment where a document exists, but > > fails to be retrieved co

SolrDispatchFilter Request Consumption

g unexpected in what data makes it into solr, so it doesn't seem problematic right now. Thanks, Chris

Re: SolrDispatchFilter Request Consumption

ixed after the 9.3.8 version (and not backported) that was packaged with 6.3.0. No idea if it is actually related though. Thanks, Chris o.a.s.s.SolrDispatchFilter Could not consume full client request java.io.IOException: Committed before 100 Continues

SplitShard Replica Placement

d on. How does solr determine where to put the new follower replicas, and is there a way to prevent it from colocating the leader and the follower of the new shards? Thanks, Chris

Re: Facet on a Payload field type?

: The payload idea was from my boss, it's similar to how they did this in : Endeca. ... : My alternate idea is to have sets of facet fields for different languages, : then let our service layer determine the correct one for the user's : language, but I'm curious as to how others have solve

Re: Facet on a Payload field type?

the : translations would be stored in the payloads : : On Wed, Aug 23, 2017 at 7:47 PM, Chris Hostetter : wrote: : : > : > : The payload idea was from my boss, it's similar to how they did this in : > : Endeca. : > ... : > : My alternate idea is to have sets of

Re: Facet on a Payload field type?

g : Subject: Re: Facet on a Payload field type? : : You are describing the idea pretty accurately. Apparently Endeca has : something that sort of supports this, which we used for the problem. : : On Thu, Aug 31, 2017 at 1:59 PM, Chris Hostetter : wrote: : : > : > ok, so lemme attempt to res

Re: ERR_SSL_VERSION_OR_CIPHER_MISMATCH

all of the low level SSL code used by Solr comes from the JVM. double check which version of java you are using and make sure it's consistent on all of your servers -- if you disable SSL on the affected server you can use the Solr Admin UI to be 100% certain of exactly which version of java is

RE: How to remove control characters in stored value at Solr side

: You can not do this in Solr, you cannot even send non-character code : points in the first place. For Apache Nutch we solved the problem by Strictly speak: this is false. You *can* send control characters to solr as field values -- assuming your transport format allows it. Example: using j

RE: How to remove control characters in stored value at Solr side

: But, can you then explain why Apache Nutch with SolrJ had this problem? : It seems that by default SolrJ does use XML as transport format. We have : always used SolrJ which i assumed would default to javabin, but we had : this exact problem anyway, and solved it by stripping non-character cod

Re: Moving to Point, trouble with IntPoint.newRangeQuery()

: I have a QParser impl. that transforms text input to one or more : integers, it makes a BooleanQuery one a field with all integers in : OR-more. It used to work by transforming the integer using : LegacyNumericUtils.intToPrefixCoded, getting a BytesRef. : : I have now moved it to use IntPoin

Unauthorized Requests on Empty Solr Node

if the security.json shouldn't be the problem. Thanks, Chris { "authentication":{ "blockUnknown":true, "class":"solr.BasicAuthPlugin", "credentials":{ "solradmin":"hashedpassword",

RE: Moving to Point, trouble with IntPoint.newRangeQuery()

: Ok, it has been resolved. I was lucky to have spotted i was looking at : the wrong schema fike! The one the test actually used was not yet : updated from Trie to Point! And boom goes the dynamite. This is a prime example of where having assumptions in your code (that the field type will by

Re: Jenkins setup for continuous build

: I have some custom code in solr (which is not of good quality for : contributing back) so I need to setup my own continuous build solution. I : tried jenkins and was hoping that ant build (ant clean compile) in Execute : Shell textbox will work, but I am stuck at this ivy-fail error: : : To wor

Re: Solr test runs: test skipping logic

: I am seeing that in different test runs (e.g., by executing 'ant test' on : the root folder in 'lucene-solr') a different subset of tests are skipped. : Where can I find more about it? I am trying to create parity between test : successes before and after my changes and this is causing confusio

Re: Solr not preserving milliseconds precision for zero milliseconds

: > "startTime":"2013-02-10T18:36:07.000Z" ... : handler. It gets added successfully but when I retrieve this document back : using "id" I get following. ... : > "startTime":"2013-02-10T18:36:07Z", ... : As you can see, the milliseconds precision in date fiel

Re: mm is not working if you have same term multiple times in query

: I'm using Solr 6.6.0 i have set mm as 100% but when i have the repeated : search term then mm param is not honoured : I have 2 docs in index : Doc1- : name=lock : Doc 2- : name=lock lock : : Now when i'm quering the solr with query : *http://localhost:8983/solr/test2/select?defType=dismax&qf=

Re: Slow when query with cursorMark

: I would guess that your first query is hitting the queryResultCache. yeah, that's almost certainly why you're seeing the "page#0" query be so fast -- but IIRC the cursorMark pages can't be cached in the same way? where you'll start to see significant speed ups is in in the subsequent "page

Re: Doubt about facet with dates

: https://lucene.apache.org/solr/guide/6_6/working-with-dates.html#Workin : gwithDates-DateMath : : Your query would be something like : mydate:[* TO NOW/DAY] AND mydate:[NOW+1DAY/DAY TO *] specifically you could use those with "facet.query" ... instead of trying to do them with "facet.range"

Re: Newbie question about why represent timestamps as "float" values

: Here is my question. In schema.xml, there is this field: : : : : Question: why is this declared as a float datatype? I'm just looking : for an explanation of what is there – any changes come later, after I : understand things better. You would hvae to ask the creator of that sch

Querying a specific replica in SolrCloud

ca is handling a request via debug or some other parameter, or to specify which replica to route the request to? Thanks, Chris

Re: Querying a specific replica in SolrCloud

> You can also try adding "&shards.info=true" to the standart request like: > solr_node:port/solr/collection/query?shards.info=true&blah blah blah > > Best, > Erick > > On Wed, Oct 11, 2017 at 7:58 AM, Chris Ulicny wrote: > > Hi, > > > &g

Inconsistent results for facet queries

o troubleshoot this are appreciated. Thanks, Chris

Re: Inconsistent results for facet queries

n't end up fixing the problem. Out of curiosity, are there any good write-ups or documentation on how two (or more) lucene segments are merged, or is it just worth looking at the source code to figure that out? Thanks, Chris On Wed, Oct 11, 2017 at 6:55 PM Erick Erickson wrote: > bq: ...

Re: Inconsistent results for facet queries

. 2) Is it expected that any large tainted segments will eventually merge with clean segments resulting in more tainted segments as enough docs are deleted on the large segments? Also, we aren't disk constrained as much as previously. Reindexing a subset of docs is possible, but a full clean colle

Re: Inconsistent results for facet queries

an setup a small test in QA for this, and test it out. This facet issue is the only one we've noticed and is able to be worked around, so we might end up just waiting until we reindex for version 7.X to permanently fix it. Thanks Chris On Thu, Oct 12, 2017 at 1:41 PM Erick Erickson wrote: &

Re: Edismax - bq taking precedence over pf

: ok. Shouldn't pf be applied on top of bq=? that way among the object_types : boosted, if one has "Manufacturing" then it should be listed first? No. bq is an *additive* boost ... documents must match your "main query" to be included, but if document X scores very high against the bq query, an

Long blocking during indexing + deleteByQuery

sing some big problems. Thanks, Chris

Re: Java 9

: Anyone else been noticing this this msg when starting up solr with java 9? (This is just an FYI and not a real question) : Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. : Java HotSpot(TM) 64-

Re: Java 9

: Anyone else been noticing this this msg when starting up solr with java 9? (This is just an FYI and not a real question) : Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. : Java HotSpot(TM) 64-

Re: recent utf8 problems

: We recently discovered issues with solr with converting utf8 code in the search. One or two month ago everything was still working. : : - What might have caused it is a Java update (Java 8 Update 151). : - We are using firefox as well as chrome for displaying results. : - We tested it with So

Re: Long blocking during indexing + deleteByQuery

plica. Has anyone else experienced this/have any thoughts on what to try? On Sun, Nov 5, 2017 at 2:20 PM, Chris Troullis wrote: > Hi, > > I am experiencing an issue where threads are blocking for an extremely > long time when I am indexing while deleteByQuery is also running. > > Se

Re: Long blocking during indexing + deleteByQuery

t's worse when it comes to distributed indexes. If the updates > > were sent out in parallel you could end up in situations where one > > replica contained 132 and another didn't depending on the vagaries of > > thread execution. > > > > Now I didn't write

Re: recent utf8 problems

: 1) When looking for Tübingen in the title, I am expecting the 3092484 Just to be clear -- I'm reading that as an 8 character word, where the 2nd character is U+00FC and the other characters are plain ascii: T_bingen Also to be clear: I'm attempting to reproduce the steps you describe using

Re: Long blocking during indexing + deleteByQuery

@Erick, I see, thanks for the clarification. @Shawn, Good idea for the workaround! I will try that and see if it resolves the issue. Thanks, Chris On Tue, Nov 7, 2017 at 1:09 PM, Erick Erickson wrote: > bq: you think it is caused by the DBQ deleting a document while a > document wit

Re: A problem of tracking the commits of Lucene using SHA num

: In the first few weeks of 2016, the Lucene/Solr project migrated from : svn to git.  Prior to this, there was a github mirror of the subversion : repository, but when the official repository was converted, that github : mirror was completely deleted, and replaced with an exact mirror of the : off

Re: Long blocking during indexing + deleteByQuery

rovements in using multiple > threads to resolve deletions: > http://blog.mikemccandless.com/2017/07/lucene-gets- > concurrent-deletes-and.html > > Mike McCandless > > http://blog.mikemccandless.com > > On Tue, Nov 7, 2017 at 2:26 PM, Chris Troullis > wrote: > >

Re: Long blocking during indexing + deleteByQuery

rying manually it seems to work fine, but something is going on in some of our test environments. Thanks, Chris On Thu, Nov 9, 2017 at 2:52 PM, Chris Troullis wrote: > Thanks Mike, I will experiment with that and see if it does anything for > this particular issue. > > I implemented S

Re: TimeZone issue

: : As I said before, I do not think that Solr will use timezones for date display : -- ever.  Solr does support timezones in certain circumstances, but I'm pretty One possibility that has been discussed in the pst is the idea of a "Date Formatting DocTransformer" that would always return a Stri

Re: External file field

: Do I need to define a field with when I use an external file : field? I see the to define it, but the docs don’t say how : to define the field. you define the field (or dynamicField) just like any other field -- the fieldType is where you specify things like the 'keyField' & the 'defVal',

SOLR-10272

ot; one was intended or not when the change was made. If it was, the documentation for CREATE in the Collections API could do with an update, because it currently seems to me at least like the behavior hasn't actually changed from the 6.X behavior. Thanks, Chris

Re: SOLR-10272

Thanks Shawn, That's great to hear. I'm glad the overwriting behavior is being reverted. On Wed, Dec 6, 2017 at 10:33 AM Shawn Heisey wrote: > On 12/6/2017 6:43 AM, Chris Ulicny wrote: > > I am curious as to whether overwriting an _existing_ config with the > > "

Re: JSON-B deserialization of Solr-response with highlightning

: We're started to migrate our integration-framework to move over to : JavaEE JSON-B as default json-serialization /deserialization framework : and now the highlighning component is giving us some troubles. Here's a : constructed example of the JSON response from Solr. Wait .. what? that make

Re: solr.TrieDoubleField deprecated with 7.1.0 but wildcard "*" search behaviour is different with solr.DoublePointField

AFAICT The behavior you're describing with Trie fields was never intentionally supported/documented? It appears that it only worked as a fluke side effect of how the default implementation of FieldType.getprefixQuery() was inherited by Trie fields *and* because "indexed=true" TrieFields use T

Authentication Plugin

pe: [ADMIN], collections: [], Path: [/admin/cores] path : /admin/cores params :core=Feeds_shard11_replica2&action=REQUESTRECOVERY&wt=javabin&version=2 How does solr determine what user/authentication to use for inter-node requests? Are there any of the predefined permissions that we shouldn't have assigned to a user that are causing this? Thanks, Chris

Negative Core Node Numbers

ot;}}} This keeps happening even when the collection is successfully deleted (no directories or files left on disk), the entire cluster is shutdown, and the zookeeper chroot path cleared out of all content. The only thing that happened prior to this cycle was a single failed collection creation which seemed to clean itself up properly, after which everything was shutdown and cleaned from zookeeper as well. Is there something else that is keeping track of those values that wasn't cleared out? Or is this now the expected behavior for the numerical assignments to replicas? Thanks, Chris

Re: Negative Core Node Numbers

lica_n-2046950790 <(204)%20695-0790>", "base_url":"http://host2:8080/solr";, "node_name":"host2:8080_solr","state":"active", "type":"NRT", "leader":"true"}, "core_node766423250"

Using DIH FileListEntityProcessor with SolrCloud

: This same script worked as expected on a single solr node (i.e. not in SolrCloud mode). Thanks, Chris -- Chris Rogers Digital Projects Manager Bodleian Digital Library Systems and Services chris.rog...@bodleian.ox.ac.uk

Re: Using DIH FileListEntityProcessor with SolrCloud

Hi all, Just bumping my question again, as doesn’t seem to have been picked up by anyone. Any help would be much appreciated. Chris On 02/12/2016, 16:36, "Chris Rogers" wrote: Hi all, A question regarding using the DIH FileListEntityProcessor with SolrCloud (

Re: Reserved characters in password used by Jetty (Solr)

: I fixed the issue by URL encoding. Here is a slim down version of my code : (with the fix): ... : // Gives back: http://username:password@server:port/solr/... : String solrUrl = "http://"; + username + ":" + password + "@" + : getSolrServerName() + ":" getSolrServerPort(

RE: Solr seems to reserve facet.limit results

I think what you're seeing might be a result of the overrequesting done in phase #1 of a distriuted facet query. The purpose of overrequesting is to mitigate the possibility of a constraint which should be in the topN for the collection as a whole, but just outside the topN on every shard -- s

Re: Difference between currency fieldType and float fieldType

: Thanks for your reply. : : That means the best fieldType to use for money is currencyField, and not : any other fieldType? The primary use case for CurrencyField is when you want to do dynamic currency fluctuations between multiple currency types at query time -- but to do that you either nee

Re: The state of Solr 5. Is it in maintenance mode only?

: On the 5.x front I wasn't expecting 5.6 release now that we have 6.x but : was simply surprised to see fix for 4.x and not for 5.x. As Shawn mentioned: jira issues might have inccorrect fixVersion info if people don't pay enough attention when resolving (especially with dups/invalid) but what

Re: Adding DocExpirationUpdateProcessorFactory causes "Overlapping onDeckSearchers" warnings

: bq: ...is it triggering a commit every 30 seconds, because that's what : I have the autoDeletePeriodSeconds set to yes a commit is triggered each time a delete is fired. : There's a note in the code about making the commits optional, it seems : fair to raise a JIRA about implementing this. Pat

Re: Adding DocExpirationUpdateProcessorFactory causes "Overlapping onDeckSearchers" warnings

: > If you are seeing an increase in "Overlapping onDeckSearchers" when using : > DocExpirationUpdateProcessorFactory, it's becuase you actaully have docs : > expiring quite frequently relative to the autoDeletePeriodSeconds and : > the amount of time needed to warm each of the new searchers. :

Re: CREATEALIAS to non-existing collections

: > We currently support requests to CREATEALIAS to collections that don’t : > exist. Requests to this alias later result in 404s. If the target : > collection is later created, requests to the alias will begin to work. I’m : > wondering if someone is relying on this behavior, or

Re: Traverse over response docs in SearchComponent impl.

FWIW: Perhaps an XY problem? can you explain more in depth what it is you plan on doing in this search component? : I can see that Solr calls the component's process() method, but from : within that method, rb.getResponseDocs(); is always null. No matter what : i try, i do not seem to be able

Re: Solr 6 Default Core URL

No, Solr stoped supporting the concept of a default core back in Solr5. The only tangible benefit to having a default was being able to change the default to point at a diff core w/o impacting existing users. You can easily do the same thing by creating a core/collection alias that you use in

Re: "on deck" searcher vs warming searcher

(disclaimer: i'm writing this all from memory, maybe there was some code change at some point that i'm not aware of and i'm completley wrong) : I've always understood the "on deck" searcher(s) being the same as the : warming searcher(s). So you have the "active" searcher and them the warming :

Re: "on deck" searcher vs warming searcher

: In a situation where searchers A-E are queued in the states : A: Current : B: Warming : C: Ondeck : D: Ondeck : E: Being created with newSearcher : : wouldn't it make sense to discard C before it gets promoted to Warming, : as the immediate action after warming C would be to start warming D? :

Re: DocTransformer not always working

Fairly certain you aren't overridding getExtraRequestFields, so when your DocTransformer is evaluated it can'd find the field you want it to transform. By default, the ResponseWriters don't provide any fields that aren't explicitly requested by the user, or specified as "extra" by the DocTran

RE: DocTransformer not always working

: Well, i can work with this really fine knowing this, but does it make : sense? I did assume (or be wrong in doing so) that fl=minhash:[binstr] : should mean get that field and pass it through the transformer. At least : i just now fell for it, maybe other shouldn't :) that's what it *can* me

Re: ttl on merge-time possible somehow ?

: Yep, that's what came in my search. See how TTL work in hbase/cassandra/ : rocksdb . There : isn't a "delete old docs"query, but old docs are deleted by the storage : when merging. Looks like this needs to be a lucene-module which can then b

Re: ttl on merge-time possible somehow ?

: > lucene, something has to "mark" the segements as deleted in order for them ... : Note, it doesn't mark the "segment", it marks the "document". correct, typo on my part -- sorry. : > The disatisfaction you expressed with this approach confuses me... : > : Really ? : If you have many e

Re: Confusing debug=timing parameter

SG: IIRC, when doing a distributed/cloud search, the timing info returned for each stage is the *cummulative* time spent on that stage in all shards -- so if you have 4 shards, the "process" time reported could be 4x as much as the actual process time spent. The QTime reported back (in a dist

Re: ttl on merge-time possible somehow ?

: So, the other way this can be made better in my opinion is (if the : optimization is not already there) : Is to make the 'delete-query' on ttl-documents operation on translog to not : be forced to fsync to disk (so still written to translog, but no fsync). : The another index/delete happens,

SolrCloud and LVM

dware becomes available. Thanks, Chris

Re: SolrCloud and LVM

to cache entirely in memory, and we haven't had any performance problems so far. So I'm not expecting that to change too much when moving the cloud architecture. Thanks again. On Thu, Jan 5, 2017 at 7:55 PM Shawn Heisey wrote: > On 1/5/2017 3:12 PM, Chris Ulicny wrote: > > Is

Re: Referencing a !key and !stat in facet.pivot

If i'm understanding your question correctly, what you're looking for is simply... stats.field={!tag=pivot_stats}lastPrice facet.pivot={!key=pivot stats=pivot_stats}buyer,vendor ...there should only ever be one set of "{}" in the facet.pivot, defining the set of local params, and there are 2 p

Re: Error Loading Custom Codec class with Solr Codec Factory. Class cast exception

: But when I try to load this codec directly via Solrconfig.xml CodecFactory : as below. : : : ...there is a difference between a (lucene layer) Codec. And a (solr layer) CodecFactory. Having the codec code in place (with the necessary SPI metadata files) let's Solr/Lucene *read* indexes

no dataimport-handler defined!

SOLR admin UI. My config files are listed below. Can anyone spot any mistakes here? Many thanks, Chris # solrconfig.xml ## … DIH-data-config.xml # DIH-data-config.xml (in the same dir as solrconfig.xml

Re: no dataimport-handler defined!

replacing the relative path to the .jar with an absolute path to the dist directory. Still didn’t work. Thanks, Chris On 24/01/2017, 13:20, "Alexandre Rafalovitch" wrote: Which solrconfig.xml are you editing and what kind of Solr install are you running (cloud?). And did you

Re: no dataimport-handler defined!

A quick update. I rolled back to solr 6.2, and the data import handler is recognized there. So there has either been a change in the config required between 6.2 and 6.4, or there’s a bug in 6.4 Any thoughts? On 24/01/2017, 13:32, "Chris Rogers" wrote: Hi Alex, I

Get Handler Returning Null

itial configurations) that would possibly cause the get handler to not return documents that exist in the collection? Thanks, Chris

Re: no dataimport-handler defined!

Hi Alex, Just tested the DIH example in 6.4 (bin/solr -e dih) Getting the same “No dataimport-handler defined!” for every one of the cores installed as part of the example. Cheers, Chris On 24/01/2017, 15:07, "Alexandre Rafalovitch" wrote: Strange. If you run a pre

Re: After migrating to SolrCloud

That error means that some client talking to your server is attempting to use an antiquated HTTP protocol version, which was (evidently) supported by the jetty used in 3.6, but is no longer supported by the jetty used in 6.2. (some details: https://stackoverflow.com/a/32302263/689372 ) If it'

Re: project related configsets need to be deployed in both data and solr install folders ?

Based on your description of the problem, and the fact that explicitly setting configSetBaseDir in your solr.xml works, I suspect there is some sort of weird bug in how the "default" configSetBaseDir is determined in some diff code paths in Solr. We should definitely file a jira issue tracking

Re: project related configsets need to be deployed in both data and solr install folders ?

: Re: project related configsets need to be deployed in both data and : solr install folders ? : : Hi Chris, : since I have been playing with this install, and I am not certain if I have : unknowingly messed some other settings. I want to avoid put in a false Jira : wasting your time. : : I

Facets and docValues

I've been trying to figure out how exactly docValues help with facet queries, and I only seem to find mention that they are beneficial to facet performance without many specifics. What I'd like to know is whether it applies to all fields used in the facet or just fields that are faceted on. For ex

RE: Atomic updates to increase single field bulk updates?

: partial update or a complete document. Under the hood a partial update : is a complete object anyway. Using partial updates you gain a little : bandwidth at the expense of additional stored fields. FWIW: once SOLR-5944 lands in a released version, that won't always be true -- atomic updates

Re: Division in JSON Facet

I'm sorry I didn't see your original question last month, but as you've since realized you can't use functions like "div" in this way. The syntax for getting "stats" in the JSON Faceting API doesn't really make this clear, but the outermost function call you make must be somethign that can "ag

Re: Facet query - exlude main query

: Solr3.1 Starting with Solr 3.1, the : primary relevance query (i.e. the one normally specified by the *q* parameter) : may also be excluded. : : But doesnt show me how to exlude it ?? same tag + ex local params, as you had in your example... : 2. q=

Re: Facet query - exlude main query

: facet.field: [ : "{!ex=tag_make,tag_model,tag_mq}feature_s_1_make", : "{!ex=tag_model}feature_s_2_model" ... : q: "{!tag=mq}nissan", You are attempting to exclude tags named "tag_make", "tag_model", and "tag_mq" -- but the name of the tag you are using in the query is "mq" if you incl

Re: Facet query - exlude main query

: Maybe I'm doing something wrong ? : /select?q.op=OR&mm=2&q={!tag=mq}nissan&qf=name%20name_raw&wt=json&start=0&rows=20&facet.field={!ex=tag_mq}feature_s_1_make that url still contains "ex=tag_mq" .. which is looking for a query with a tag named "tag_mq" .. in your q param you are using a t

Problem managing Solr configsets on Zookeeper

old collection! It’s as if the old config has been cached somewhere or something… Am I missing a stage or command here? Many thanks, Chris -- Chris Rogers Digital Projects Manager Bodleian Digital Library Systems and Services chris.rog...@bodleian.ox.ac.uk

Re: Problem managing Solr configsets on Zookeeper

Hi Gus, Thanks for the reply, but unfortunately this is not the problem. I am using the basic schema factory, with a directly edited schema file. Best, Chris On 22/02/2017, 12:00, "Gus Heck" wrote: Hi Chris, Are you perhaps using (by default) ManagedIndexSch

Re: Problem managing Solr configsets on Zookeeper

as pushed the config to zookeeper, but the config reload isn’t associating this new config. Should the upconfig be pushing the new config directly into that /solr/configs znode? Best, Chris On 22/02/2017, 15:06, "Erick Erickson" wrote: Chris: I'd check a couple of

<    1   2   3   4   5   6   7   8   9   10   >