Hi - adding carrot.title field should resolve this issue
On Thu, Dec 19, 2019 at 2:22 AM Nehemia Litterat
wrote:
> Hi,
> I am using stand alone solr 8.2 server.
> Used this guide to define Clustering
> https://carrot2.github.io/solr-integration-strategies/carrot2-3.6.3/index.html
>
>
> (Attached
Hi,
Is there a way to select text fields in a query with a join clause in
Streaming Expressions or Parallel SQL? The following query:
SELECT field_s, field_t FROM t1 INNER JOIN t2 ON t1.a = t2.a LIMIT 10
requires that field_t, which is of type text, have docValues enabled, which
is not supported
This could be because Zookeeper ensemble is not properly configured. Using
a very similar setup which consists of ZK cluster of three hosts and one
Solr Cloud node (all are containers), the system got running. Each ZK host
has ZOO_MY_ID and ZOO_SERVERS environment variables set before running ZK.
I
randal.maff...@enron.com
Randal Maffett
...
which can be used as a subsequent request to the first in order to retrieve
additional fields but it would be more efficient if there's a way to
retrieve the required fields in one request.
Best,
A. Adel
On Mon, Jul 22, 2019
Hi,
Similar to this question (
https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201907.mbox/browser),
how can additional fields be returned when using /graph request handler?
For example, from the documentation, for the request:
nodes(enron_emails,
nodes(enron_emails,
walk="kayne.coul.
tch expression. When we look at
> that log we'll be able to see what the query is, and if results are
> returned. It could be a bug in the code or it could be something related to
> the data that's being fetched.
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
e /select handler on your
> install?
>
> Anyway fetch needs to be reverted back to it's previous implementation
> before the above commit basically broke it.
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
> On Fri, Jul 19, 2019 at 2:20 PM Ahmed Ad
sed on the
> fetch. If that doesn't work, I'll investigate further.
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
> On Fri, Jul 19, 2019 at 5:51 AM Ahmed Adel wrote:
>
> > Hi Joel,
> >
> > Thank you for your thoughts. I tried the
onal thoughts are appreciated.
Best,
A.
On Thu, Jul 18, 2019 at 6:12 PM Joel Bernstein wrote:
> Hi Ahmed,
>
> Take a look at the fetch
>
> https://lucene.apache.org/solr/guide/8_0/stream-decorator-reference.html#fetch
>
> It probably makes sense to allow more field to be r
gt; You have to perform a „join“ to get more fields.
>
> > Am 16.07.2019 um 13:52 schrieb Ahmed Adel :
> >
> > Hi,
> >
> > How can multiple fields be returned in graph traversal streaming
> expression
> > response documents? For example, the following query
Hi,
How can multiple fields be returned in graph traversal streaming expression
response documents? For example, the following query:
nodes(emails,
walk="john...@apache.org->from",
gather="to")
returns these documents in the response:
{
"result-set": {
"docs": [
{
rts with stats=true and mis-typed the q clause.
>
> Best,
> Erick
> > On Jul 3, 2019, at 5:08 AM, Ahmed Adel wrote:
> >
> > Hi,
> >
> > As per the documentation recommendation of using pivot with stats
> component
> > instead (
> >
> ht
ppreciated.
Thanks,
A. Adel
On Tue, Jul 2, 2019 at 4:38 PM Ahmed Adel wrote:
> Hi,
>
> How can stats field value be calculated for top facet values? In other
> words, the following request parameters should return the stats.field
> measures for facets sorted by count:
>
>
ppreciated.
Thanks,
A. Adel
On Tue, Jul 2, 2019 at 4:38 PM Ahmed Adel wrote:
> Hi,
>
> How can stats field value be calculated for top facet values? In other
> words, the following request parameters should return the stats.field
> measures for facets sorted by count:
>
>
Hi,
How can stats field value be calculated for top facet values? In other
words, the following request parameters should return the stats.field
measures for facets sorted by count:
q: *
wt: json
stats: true
stats.facet: authors_s
stats.field: average_rating_f
facet.missing: true
f.authors_s.face
you saying that you intend to use the ZK REST API
> to fetch live_nodes and then send the 'clusterstatus' API call to one of
> the live nodes?
>
> On Thu, Apr 9, 2015 at 7:13 PM, Ahmed Adel wrote:
>
> > In fact, the advantage I see of using ZK is that we don't h
gt;
> https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api18
>
>
> On Thu, Apr 9, 2015 at 5:52 PM, Ahmed Adel wrote:
>
> > Hi Shalin,
> >
> > Thanks for your response. I'm actually looking inside ZooKeeper in order
> to
>
.json directly because 1) things like
> live-ness is not stored in clusterstate.json and 2) collections created
> with Solr 5.0 have their own individual state.json inside
> /collections/collection_name/state.json
>
> On Thu, Apr 9, 2015 at 3:37 PM, Ahmed Adel wrote:
>
> > H
Hi All,
On Solr 5.0 and ZK 3.4.6 sometimes clusterstate.json does not reflect the
aggregation of states of collections, the latter is always correct. I could
verify this from the admin panel (under Tree view) and from ZKCli. Is there
something I'm missing that could generate this issue?
--
A. A
Hi, I believe a better approach than Solarium is to create a custom search
component that extends SearchComponent class and override process() method
to store query, QTime, and numFound to a database for further analysis.
This approach would cut steps 2 through 6 into one step. Analysis can be
done
t; If 'q' is absent, then you always match nothing (there may be
> exceptions?);
> > so it's sort of required, in effect. I wish it defaulted to *:*.
> >
> > ~ David Smiley
> > Freelance Apache Lucene/Solr Search Consultant/Developer
> > http://www
urn all the documents in the index" because you did nothing
> to filter them out. Your query is *:* (everything) and there are no filter
> queries.
>
> ~ David Smiley
> Freelance Apache Lucene/Solr Search Consultant/Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
Hello,
I'm trying to get Facet By Distance working on an index with LatLonType
fields. The schema is as follows:
...
...
And the query I'm running is:
q=*:*&sfield=start_station&pt=40.71754834,-74.01322069&facet.query={!frange
l=0.0 u=0.1}geodist()&facet.query={!frange l=0.10001 u=0.2}g
Hi All,
Is there a way to convert unix time field that is already indexed to
ISO-8601 format in query response? If this is not possible on the query
level, what is the best way to copy this field to a new Solr standard date
field.
Thanks,
--
*Ahmed Adel*
<http://s.wisestamp.com/links?url=h
.
>
>
>
>
>
>
>
>
> Joel Bernstein
> Search Engineer at Heliosearch
>
> On Thu, Oct 2, 2014 at 4:10 PM, Joel Bernstein wrote:
>
> > Yep getting the same error. Investigating...
> >
> > Joel Bernstein
> > Search Engineer at Heliosearch
Hi All,
I'm trying to use Solr 4.10 export feature, but I'm getting an error. Maybe
I missed something.
Here's the scenario:
1. Download Solr 4.10.0
2. Use collection1 schema out of the box
3. Add docValues="true" to price and pages fields in schema.xml
4. Index books.json using com
26 matches
Mail list logo