Re: Documents issue

[KRIS MUSSHORN]

Allesandro et al. 

I tried this with no change in the results. 
"Other" is still missing when doctype is empty.. 
No dynamicFields are involved. 

 
 

 

- Original Message -

From: "alessandro.benedetti" <abenede...@apache.org> 
To: solr-user@lucene.apache.org 
Sent: Friday, January 27, 2017 4:07:19 AM 
Subject: Re: Documents issue 

I may be wrong and don't have time to check the code in details now, but I 
would say you need to define the default in the destination field as well. 

The copy field should take in input the plain content of the field ( which 
is null) and then pass that content to the destination field. 

Properties and attributes of the source field should not be considered at 
copy field time. 
So what it happens is simply you pass a null content to the destination 
field. 

If you define the default in the destination field, it should work as 
expected. 

N.B. it's a shot in the dark, not sure if you experienced a different 
behavior previously. 

Cheers 



-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317514.html
 
Sent from the Solr - User mailing list archive at Nabble.com. 

Re: Documents issue

[Comcast]

Only change was rename to remove periods from the fieldnames

Sent from my iPhone

> On Jan 27, 2017, at 11:53 AM, alessandro.benedetti  
> wrote:
> 
> Hi Khris,
> can you paste here the diff between the OK status and the KO status ?
> Has only the name of the destination field changed ? ( a replace of '.' with
> '_' ?)
> Do you have any dynamic field defined ?
> Cheers
> 
> 
> 
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317566.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Re: Documents issue

[alessandro.benedetti]

Hi Khris,
can you paste here the diff between the OK status and the KO status ?
Has only the name of the destination field changed ? ( a replace of '.' with
'_' ?)
Do you have any dynamic field defined ?
Cheers



--
View this message in context: 
http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317566.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Documents issue

[Comcast]

Why would this behavior changed from one day to the next? I ran crawl and index 
several times with no issues, changed the schematic xml definition of a couple 
of fields, ran crawl and index and produced the dataset with missing copyfields.

Sent from my iPhone

> On Jan 27, 2017, at 4:07 AM, alessandro.benedetti  
> wrote:
> 
> I may be wrong and don't have time to check the code in details now, but I
> would say you need to define the default in the destination field as well.
> 
> The copy field should take in input the plain content of the field ( which
> is null) and then pass that content to the destination field.
> 
> Properties and attributes of the source field should not be considered at
> copy field time.
> So what it happens is simply you pass a null content to the destination
> field.
> 
> If you define the default in the destination field, it should work as
> expected.
> 
> N.B. it's a shot in the dark, not sure if you experienced a different
> behavior previously.
> 
> Cheers
> 
> 
> 
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317514.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Re: Documents issue

[alessandro.benedetti]

I may be wrong and don't have time to check the code in details now, but I
would say you need to define the default in the destination field as well.

The copy field should take in input the plain content of the field ( which
is null) and then pass that content to the destination field.

Properties and attributes of the source field should not be considered at
copy field time.
So what it happens is simply you pass a null content to the destination
field.

If you define the default in the destination field, it should work as
expected.

N.B. it's a shot in the dark, not sure if you experienced a different
behavior previously.

Cheers



--
View this message in context: 
http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317514.html
Sent from the Solr - User mailing list archive at Nabble.com.

Documents issue

[KRIS MUSSHORN]

Running the latest crawl from Nutch to SOLR 5.4.1 it seems that my copy fields 
do not work as expected anymore. 

 
 
 


Why would copyField ignore the default all of a sudden? 

I've not made any significant changes to SOLR and none at all to nutch. 
{
  "response":{"numFound":699,"start":0,"docs":[
  {
"metatag.doctype":"Articles",
"facet_metatag_doctype":"Articles"}, 
_snipped a bunch of articles _ 
{
"metatag.doctype":"Dispatches",
"facet_metatag_doctype":"Dispatches"}, 

_snipped a bunch of Dispatches_
  
  {
"metatag.doctype":"Other"},
  {
"metatag.doctype":"Other"},
  {
"metatag.doctype":"Other"},
  {
"metatag.doctype":"Other"},
  {
"metatag.doctype":"Other"} 

_snipped a bunch of Other_
  ]
  },
  "facet_counts":{
"facet_queries":{},
"facet_fields":{
  "facet_metatag_doctype":[
"Dispatches",38,
"Articles",33]},
"facet_dates":{},
"facet_ranges":{},
"facet_intervals":{},
"facet_heatmaps":{}}}