Re: Solr with encrypted HDFS

[Hendrik Haddorp]

Hi,

we have some setups that use an encryption zone in HDFS. Once you have
the hdfs config setup the rest is transparent to the client and thus
Solr works just fine like that. Said that, we have some general issues
with Solr and HDFS. The main problem seems to be around the transaction
log files. We have a quite high commit rate and these short lived files
don't seem to play well with HDFS and triple replication of the blocks
in HDFS. But encryption did not add anything issues for us.

regards,
Hendrik

On 11.09.19 22:53, John Thorhauer wrote:

Hi,

I am interested in encrypting/protecting my solr indices.  I am wondering
if Solr can work the an encrypted HDFS.  I see that these instructions (
https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/configuring-hdfs-encryption/content/configuring_and_using_hdfs_data_at_rest_encryption.html)
explain that:

"After permissions are set, Java API clients and HDFS applications with
sufficient HDFS and Ranger KMS access privileges can write and read to/from
files in the encryption zone"


So I am wondering if the solr/java api that uses HDFS would work with this
as well and also, has anyone had experience running this?  Either good
or bad?

Thanks,
John

Re: Is it possible to skip scoring completely?

[Shawn Heisey]

On 9/11/2019 5:27 PM, Ashwin Ramesh wrote:

I was wondering if there is a way we can tell solr (7.3+) to run none of
it's scoring logic. We would like to simply add a set of filter queries and
order on a specific docValue field.

e.g. "Give me all fq=color:red documents ORDER on popularityScore DESC"


I don't know whether doing so actually tells Solr to completely skip the 
scoring calculations, but you can easily make those calculations 
irrelevant simply by including a sort parameter with your query that 
references something other than score.


I would not expect skipping scoring to provide much in the way of a 
performance enhancement even if specifying a sort does disable those 
calculations.  Java can do math calculations VERY quickly, and as I 
understand it, scoring is just math.


Thanks,
Shawn

Is it possible to skip scoring completely?

[Ashwin Ramesh]

Hi everybody,

I was wondering if there is a way we can tell solr (7.3+) to run none of
it's scoring logic. We would like to simply add a set of filter queries and
order on a specific docValue field.

e.g. "Give me all fq=color:red documents ORDER on popularityScore DESC"

Thanks in advance,

Ash

-- 
*P.S. We've launched a new blog to share the latest ideas and case studies 
from our team. Check it out here: product.canva.com 
. ***
** Empowering the 
world to design
Also, we're hiring. Apply here! 

  
  
    
  

Solr with encrypted HDFS

[John Thorhauer]

Hi,

I am interested in encrypting/protecting my solr indices.  I am wondering
if Solr can work the an encrypted HDFS.  I see that these instructions (
https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/configuring-hdfs-encryption/content/configuring_and_using_hdfs_data_at_rest_encryption.html)
explain that:

"After permissions are set, Java API clients and HDFS applications with
sufficient HDFS and Ranger KMS access privileges can write and read to/from
files in the encryption zone"


So I am wondering if the solr/java api that uses HDFS would work with this
as well and also, has anyone had experience running this?  Either good
or bad?

Thanks,
John

RE: CDCR tlog corruption leads to infinite loop

[Webster Homer]

We also see an accumulation of tlog files on the target solrs. One of our 
production clouds crashed due to too many open files
2019-09-11 15:59:39.570 ERROR (qtp1355531311-81540) 
[c:bioreliance-catalog-testarticle-20190713 s:shard2 r:core_node8 
x:bioreliance-catalog-testarticle-20190713_shard2_replica_n6] 
o.a.s.s.HttpSolrCall null:org.apache.solr.common.SolrException: 
java.io.FileNotFoundException: 
/var/solr/data/bioreliance-catalog-testarticle-20190713_shard2_replica_n6/data/tlog/tlog.0005307.1642472809370222592
 (Too many open files)

We found 9106 open files. 

This is our update request handler


 


  ${solr.ulog.dir:}



  
   ${solr.autoCommit.maxTime:6} 
   false 
 

  
   ${solr.autoSoftCommit.maxTime:3000} 
 

  

solr.autoSoftCommit.maxTime is set to 3000
solr.autoCommit.maxTime is set to 6

-Original Message-
From: Webster Homer  
Sent: Monday, September 09, 2019 4:17 PM
To: solr-user@lucene.apache.org
Subject: CDCR tlog corruption leads to infinite loop

We are running Solr 7.2.0

Our configuration has several collections that are loaded into a solr cloud 
which is set to replicate using CDCR to 3 different solrclouds. All of our 
target collections have 2 shards with two replicas per shard. Our source 
collection has 2 shards, and 1 replica per shard.

Frequently we start to see errors where the target collections are out of date, 
and the cdcr action=errors endpoint shows large numbers of errors For example:
{"responseHeader": {
"status": 0,
"QTime": 0},
"errors": [
"uc1f-ecom-mzk01:2181,uc1f-ecom-mzk02:2181,uc1f-ecom-mzk03:2181/solr",
["sial-catalog-product-20190824",
[
"consecutiveErrors",
700357,
"bad_request",
0,
"internal",
700357,
"last",
[
"2019-09-09T19:17:57.453Z",
"internal",
"2019-09-09T19:17:56.949Z",
"internal",
"2019-09-09T19:17:56.448Z"
,"internal",...

We have found that one or more tlogs have become corrupt. It appears that the 
CDCR keeps trying to send data, but cannot read the data from the tlog and then 
it retrys, forever.
How does this happen?  It seems to be very frequent, on a weekly basis and 
difficult to trouble shoot Today we had it happen with one of our collections. 
Here is the listing for the tlog files:

$ ls -alht
total 604M
drwxr-xr-x 2 apache apache  44K Sep  9 14:27 .
-rw-r--r-- 1 apache apache 6.7M Sep  6 19:44 
tlog.766.1643975309914013696
-rw-r--r-- 1 apache apache  35M Sep  6 19:43 
tlog.765.1643975245907886080
-rw-r--r-- 1 apache apache  30M Sep  6 19:42 
tlog.764.1643975182924120064
-rw-r--r-- 1 apache apache  37M Sep  6 19:41 
tlog.763.1643975118316109824
-rw-r--r-- 1 apache apache  19M Sep  6 19:40 
tlog.762.1643975053918863360
-rw-r--r-- 1 apache apache  21M Sep  6 19:39 
tlog.761.1643974989726089216
-rw-r--r-- 1 apache apache  21M Sep  6 19:38 
tlog.760.1643974926010417152
-rw-r--r-- 1 apache apache  29M Sep  6 19:37 
tlog.759.1643974862567374848
-rw-r--r-- 1 apache apache 6.2M Sep  6 19:10 
tlog.758.1643973174027616256
-rw-r--r-- 1 apache apache 228K Sep  5 19:48 
tlog.757.1643885009483857920
-rw-r--r-- 1 apache apache  27M Sep  5 19:48 
tlog.756.1643884946565103616
-rw-r--r-- 1 apache apache  35M Sep  5 19:47 
tlog.755.1643884877912735744
-rw-r--r-- 1 apache apache  30M Sep  5 19:46 
tlog.754.1643884812724862976
-rw-r--r-- 1 apache apache  25M Sep  5 19:45 
tlog.753.1643884748976685056
-rw-r--r-- 1 apache apache  18M Sep  5 19:44 
tlog.752.1643884685794738176
-rw-r--r-- 1 apache apache  21M Sep  5 19:43 
tlog.751.1643884621330382848
-rw-r--r-- 1 apache apache  16M Sep  5 19:42 
tlog.750.1643884558054064128
-rw-r--r-- 1 apache apache  26M Sep  5 19:41 
tlog.749.1643884494725316608
-rw-r--r-- 1 apache apache 5.8M Sep  5 19:12 
tlog.748.1643882681969147904
-rw-r--r-- 1 apache apache  31M Sep  4 19:56 
tlog.747.1643794877229563904
-rw-r--r-- 1 apache apache  31M Sep  4 19:55 
tlog.746.1643794813706829824
-rw-r--r-- 1 apache apache  30M Sep  4 19:54 
tlog.745.1643794749615767552
-rw-r--r-- 1 apache apache  22M Sep  4 19:53 
tlog.744.1643794686253465600
-rw-r--r-- 1 apache apache  18M Sep  4 19:52 
tlog.743.1643794622319689728
-rw-r--r-- 1 apache apache  21M Sep  4 19:51 
tlog.742.1643794558055612416
-rw-r--r-- 1 apache apache  15M Sep  4 19:50 
tlog.741.1643794493330161664
-rw-r--r-- 1 apache apache  26M Sep  4 19:49 
tlog.740.1643794428790308864
-rw-r--r-- 1 apache apache  11M Sep  4 14:58 
tlog.737.1643701398824550400
drwxr-xr-x 5 apache apache   53 Aug 21 06:30 ..
[apache@dfw-pauth-msc01 tlog]$ ls -alht 

RE: Replication Iteration

[Akreeti Agarwal]

Hi,

It fails many times, sharing the iteration:

Passed:
Wed Sep 11 16:49:18 UTC 2019
Wed Sep 11 16:48:56 UTC 2019
Wed Sep 11 16:48:36 UTC 2019
Wed Sep 11 16:48:18 UTC 2019
Wed Sep 11 16:47:55 UTC 2019
Wed Sep 11 16:47:35 UTC 2019
Wed Sep 11 16:47:16 UTC 2019
Wed Sep 11 16:46:55 UTC 2019
Wed Sep 11 16:46:33 UTC 2019

Failed:
Wed Sep 11 16:42:47 UTC 2019
Wed Sep 11 16:36:07 UTC 2019
Wed Sep 11 16:32:47 UTC 2019
Wed Sep 11 16:29:27 UTC 2019
Wed Sep 11 16:24:27 UTC 2019
Wed Sep 11 16:11:07 UTC 2019
Wed Sep 11 16:09:47 UTC 2019
Wed Sep 11 16:05:47 UTC 2019
Wed Sep 11 15:53:27 UTC 2019
Wed Sep 11 15:51:47 UTC 2019

Memory details:

 total   used   free sharedbuffers cached
Mem: 15947  15549398 62198   5650
-/+ buffers/cache:   9700   6246
Swap:0  0  0


Thanks & Regards,
Akreeti Agarwal


-Original Message-
From: Jon Kjær Amundsen  
Sent: Wednesday, September 11, 2019 7:28 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication Iteration

Is it every time it fails, or just sometimes?
What is the timestamps on the failed and passed iterations?
And how much disk space do you have available on the slave?

Venlig hilsen/Best regards

*Jon Kjær Amundsen*
Developer


Phone: +45 7023 9080
E-mail: j...@udbudsvagten.dk
Web: 
https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.dkdata=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=DSWnCimBzOilM8DoS4efsbgE%2BP%2BG2RDP0IUjolch7Z4%3Dreserved=0
Parken - Tårn D - 5. Sal
Øster Allé 48 | DK - 2100 København



Intelligent Offentlig Samhandel
*Før, under og efter udbud*

*Følg UdbudsVagten og markedet her Linkedin 

 *


Den ons. 11. sep. 2019 kl. 15.23 skrev Akreeti Agarwal :

> My index size is 2.62 GB, and :
> 00:00:10
>
> Thanks & Regards,
> Akreeti Agarwal
>
>
> -Original Message-
> From: Paras Lehana 
> Sent: Wednesday, September 11, 2019 5:39 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> What is the size of your index? Is it too big? How fast is your link 
> between master and slave?
>
> I'm asking these because, for larger indexes, you may want to raise 
> commitReserveDuration defined in ReplicationHandler in solrconfig.xml.
>
> 00:00:10
>
>
> From SolrReplication
> <
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik
> i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplicationdata=
> 02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189d
> e737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=4p
> rY6X8%2FXVTbFj9OAlgQ1t6Vq7GFytRPHNzPsQkFktc%3Dreserved=0
> >
> documentation for Master
> <
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik
> i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplication%23Master&
> amp;data=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019
> bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996
> ;sdata=vPlsIvqTrwzq0wSkBkMiJc3C7IOaXpQWdwG06xRlG9k%3Dreserved=0
> >:
>
> If your commits are very frequent and network is particularly slow, 
> you can
> > tweak an extra attribute  name="commitReserveDuration">00:00:10.
> > This is roughly the time taken to download 5MB from master to slave.
> > Default is 10 secs.
>
>
>  Do check the hyperlinks.
>
> On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal  wrote:
>
> > I am seeing the logs on both UI and file, but I only see this error:
> >
> > ReplicationHandler
> > Index fetch failed :org.apache.solr.common.SolrException: Unable to 
> > download segments_znow completely. Downloaded 0!=2217
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > -Original Message-
> > From: Paras Lehana 
> > Sent: Wednesday, September 11, 2019 5:17 PM
> > To: solr-user@lucene.apache.org
> > Subject: Re: Replication Iteration
> >
> > Hi Akreeti,
> >
> > Have you tried using the old UI to see errors? I had always 
> > experienced not seeing status updates about replication in the newer 
> > UI. Check for the option on top right of Solr UI.
> >
> > And where are you seeing logs - on solr UI or from a file?
> >
> > On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:
> >
> > > In the logs I don't see any errors, mostly after every  1-2 min 
> > > 

Re: Replication Iteration

[Jon Kjær Amundsen]

Is it every time it fails, or just sometimes?
What is the timestamps on the failed and passed iterations?
And how much disk space do you have available on the slave?

Venlig hilsen/Best regards

*Jon Kjær Amundsen*
Developer


Phone: +45 7023 9080
E-mail: j...@udbudsvagten.dk
Web: www.udbudsvagten.dk
Parken - Tårn D - 5. Sal
Øster Allé 48 | DK - 2100 København



Intelligent Offentlig Samhandel
*Før, under og efter udbud*

*Følg UdbudsVagten og markedet her Linkedin
 *


Den ons. 11. sep. 2019 kl. 15.23 skrev Akreeti Agarwal :

> My index size is 2.62 GB, and :
> 00:00:10
>
> Thanks & Regards,
> Akreeti Agarwal
>
>
> -Original Message-
> From: Paras Lehana 
> Sent: Wednesday, September 11, 2019 5:39 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> What is the size of your index? Is it too big? How fast is your link
> between master and slave?
>
> I'm asking these because, for larger indexes, you may want to raise
> commitReserveDuration defined in ReplicationHandler in solrconfig.xml.
>
> 00:00:10
>
>
> From SolrReplication
> <
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplicationdata=02%7C01%7CAkreetiA%40hcl.com%7C23769a9cc4094154170008d736b0f190%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038005907686643sdata=NEwvmMCXOFB7v56IuNJ8cJglInSJZjLTSUQTT6d07f0%3Dreserved=0
> >
> documentation for Master
> <
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplication%23Masterdata=02%7C01%7CAkreetiA%40hcl.com%7C23769a9cc4094154170008d736b0f190%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038005907686643sdata=5gX%2FbeaPUQWxMkJ8bD4Jt%2BB7feB509VHD25d66iLCnU%3Dreserved=0
> >:
>
> If your commits are very frequent and network is particularly slow, you can
> > tweak an extra attribute  name="commitReserveDuration">00:00:10.
> > This is roughly the time taken to download 5MB from master to slave.
> > Default is 10 secs.
>
>
>  Do check the hyperlinks.
>
> On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal  wrote:
>
> > I am seeing the logs on both UI and file, but I only see this error:
> >
> > ReplicationHandler
> > Index fetch failed :org.apache.solr.common.SolrException: Unable to
> > download segments_znow completely. Downloaded 0!=2217
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > -Original Message-
> > From: Paras Lehana 
> > Sent: Wednesday, September 11, 2019 5:17 PM
> > To: solr-user@lucene.apache.org
> > Subject: Re: Replication Iteration
> >
> > Hi Akreeti,
> >
> > Have you tried using the old UI to see errors? I had always
> > experienced not seeing status updates about replication in the newer
> > UI. Check for the option on top right of Solr UI.
> >
> > And where are you seeing logs - on solr UI or from a file?
> >
> > On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:
> >
> > > In the logs I don't see any errors, mostly after every  1-2 min
> > > replication fails and I am not able to identify the root cause for it.
> > >
> > > Thanks & Regards,
> > > Akreeti Agarwal
> > >
> > > -Original Message-
> > > From: Jon Kjær Amundsen 
> > > Sent: Wednesday, September 11, 2019 12:15 PM
> > > To: solr-user@lucene.apache.org
> > > Subject: Re: Replication Iteration
> > >
> > > It depends on the timestamps.
> > > The red iterations are failed replications and the green are passed
> > > replications.
> > > If the newest timestamp is green the latest replication went well,
> > > if it is red, it failed.
> > >
> > > You should check the solr log on the slave if a recent replication
> > > have failed to see the cause.
> > >
> > > Venlig hilsen/Best regards
> > >
> > > *Jon Kjær Amundsen*
> > > Developer
> > >
> > >
> > > Phone: +45 7023 9080
> > > E-mail: j...@udbudsvagten.dk
> > > Web:
> > > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten
> > > .d
> > > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736
> > > ad
> > > ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416
> > > 
> > > mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved
> > > =0
> > > Parken - Tårn D - 5. Sal
> > > Øster Allé 48 | DK - 2100 København
> > >
> > > <
> > > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.
> > > li
> > > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40
> > > hc
> > > l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca
> > > 99
> > > 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nx
> > > nx
> > > ooisjC15hPV5y9NSCgKg%3Dreserved=0
> > > >
> > >
> > > Intelligent Offentlig Samhandel
> > > *Før, under og efter udbud*
> > >
> > > *Følg UdbudsVagten og markedet her Linkedin <
> > > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww
> > > .l
> > > 

Documents with same unique id indexed multiple times

[JTytler]

I am seeing multiple entries for the exact same URLs and each time I re-index
the contents the crawler adds the same entry one more time. 

I have id defined in the schema.xml file.  It seems
Solr is not reading the schema file - I cannot think of any other
explanation how the unique key constraint could be violated.

Please see the examples below:

"_language":"en",
"_description":"",
"_last_modified":"2018-11-22T00:00:00Z",
"_platform":"infosite",
"_keywords":"",
"id":"http://infosite.gc.ca/org/org/psa-af_e.aspx;,
"_title":"Office of Public Service Accessibility",
"_type":"Administrative page",
"Date":["Tue, 30 Jul 2019 19:56:28 GMT"],
"url":"http://infosite.gc.ca/org/org/psa-af_e.aspx;,
"content":["Engage expert internal and external stakeholders to provide
advice, support and motivation to facilitate progress. Date Modified:
2018-11-22"],
"version":1640514868282916864,
"root":["http://infosite.gc.ca/org/org/psa-af_e.aspx;],
"timestamp":"2019-07-30T20:01:35.564Z"},
{
"_language":"en",
"_description":"",
"_last_modified":"2018-11-22T00:00:00Z",
"_platform":"infosite",
"_keywords":"",
"id":"http://infosite.gc.ca/org/org/psa-af_e.aspx;,
"_title":"Office of Public Service Accessibility",
"_type":"Administrative page",
"Date":["Tue, 30 Jul 2019 22:12:19 GMT"],
"url":"http://infosite.gc.ca/org/org/psa-af_e.aspx;,
"content":[Engage expert internal and external stakeholders to provide
advice, support and motivation to facilitate progress. Date Modified:
2018-11-22"],
"version":1640523480504991744,
"root":["http://infosite.gc.ca/org/org/psa-af_e.aspx;],
"timestamp":"2019-07-30T22:18:28.819Z"}]
}}



I am also occassionally seeing the write.lock error message and while trying
to index sometimes Norconex Committer is unable to write to the /data/index
folder, giving error about not able to write to the files in the folder.
This all started happenning since past few weeks and I wonder if all these
issues are related and 
whether the permissions of the Solr Service account got changed that may
have caused these issues to all of sudden start to appear.

Has anyone seen this bizzare behaviour?



--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: termfreq and IntPointField

[ahubold]

Okay, after a bit of debugging and reading JIRA issues (SOLR-12074,
SOLR-12632), I think this does not work because there's no terms index for
point fields.

So it probably cannot work, and one would need to have a separate string
field with the same values (copyField) to use the termfreq function with?

Maybe this could be explained more clearly in the documentation. The
reference guide just recommends using point fields instead of the deprecated
trie fields, if one can accept the performance for field:value queries. It
should also mention the functional differences of the field types. Maybe
other features are affected as well?

Oh, I just read that TermsComponent supports point fields (SOLR-11173), so
maybe termfreq could be changed to support them as well?




--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

RE: Replication Iteration

[Akreeti Agarwal]

My index size is 2.62 GB, and :
00:00:10

Thanks & Regards,
Akreeti Agarwal


-Original Message-
From: Paras Lehana  
Sent: Wednesday, September 11, 2019 5:39 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication Iteration

What is the size of your index? Is it too big? How fast is your link between 
master and slave?

I'm asking these because, for larger indexes, you may want to raise 
commitReserveDuration defined in ReplicationHandler in solrconfig.xml.

00:00:10


From SolrReplication

documentation for Master
:

If your commits are very frequent and network is particularly slow, you can
> tweak an extra attribute 00:00:10.
> This is roughly the time taken to download 5MB from master to slave.
> Default is 10 secs.


 Do check the hyperlinks.

On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal  wrote:

> I am seeing the logs on both UI and file, but I only see this error:
>
> ReplicationHandler
> Index fetch failed :org.apache.solr.common.SolrException: Unable to 
> download segments_znow completely. Downloaded 0!=2217
>
> Thanks & Regards,
> Akreeti Agarwal
>
> -Original Message-
> From: Paras Lehana 
> Sent: Wednesday, September 11, 2019 5:17 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> Hi Akreeti,
>
> Have you tried using the old UI to see errors? I had always 
> experienced not seeing status updates about replication in the newer 
> UI. Check for the option on top right of Solr UI.
>
> And where are you seeing logs - on solr UI or from a file?
>
> On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:
>
> > In the logs I don't see any errors, mostly after every  1-2 min 
> > replication fails and I am not able to identify the root cause for it.
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > -Original Message-
> > From: Jon Kjær Amundsen 
> > Sent: Wednesday, September 11, 2019 12:15 PM
> > To: solr-user@lucene.apache.org
> > Subject: Re: Replication Iteration
> >
> > It depends on the timestamps.
> > The red iterations are failed replications and the green are passed 
> > replications.
> > If the newest timestamp is green the latest replication went well, 
> > if it is red, it failed.
> >
> > You should check the solr log on the slave if a recent replication 
> > have failed to see the cause.
> >
> > Venlig hilsen/Best regards
> >
> > *Jon Kjær Amundsen*
> > Developer
> >
> >
> > Phone: +45 7023 9080
> > E-mail: j...@udbudsvagten.dk
> > Web:
> > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten
> > .d 
> > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736
> > ad 
> > ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416
> > 
> > mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved
> > =0
> > Parken - Tårn D - 5. Sal
> > Øster Allé 48 | DK - 2100 København
> >
> > <
> > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.
> > li 
> > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40
> > hc
> > l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca
> > 99 
> > 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nx
> > nx
> > ooisjC15hPV5y9NSCgKg%3Dreserved=0
> > >
> >
> > Intelligent Offentlig Samhandel
> > *Før, under og efter udbud*
> >
> > *Følg UdbudsVagten og markedet her Linkedin < 
> > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww
> > .l
> > inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02
> > %7
> > C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de7
> > 37
> > c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416sdata=zQVT
> > %2 FJjMY6GlU4IVHZEMc6P4EWh9MrMcWEybBonKn7w%3Dreserved=0>
> > *
> >
> >
> > Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal 
> > >:
> >
> > > Hi All,
> > >
> > > I am using solr-5.5.5, in which I have one master and two slaves. 
> > > I see some red and some green replication iteration on my slave side.
> > > What does these red and green iteration means?
> > > Will this cause problem?
> > >
> > > Thanks & Regards,
> > > Akreeti Agarwal
> > >
> > > ::DISCLAIMER::
> > > 
> > > The contents of this e-mail and any attachment(s) are confidential 
> > > and intended for the named recipient(s) only. E-mail transmission 
> > > is not guaranteed to be secure 

Re: Replication Iteration

[Paras Lehana]

What is the size of your index? Is it too big? How fast is your link
between master and slave?

I'm asking these because, for larger indexes, you may want to raise
commitReserveDuration defined in ReplicationHandler in solrconfig.xml.

00:00:10


>From SolrReplication

documentation for Master
:

If your commits are very frequent and network is particularly slow, you can
> tweak an extra attribute 00:00:10.
> This is roughly the time taken to download 5MB from master to slave.
> Default is 10 secs.


 Do check the hyperlinks.

On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal  wrote:

> I am seeing the logs on both UI and file, but I only see this error:
>
> ReplicationHandler
> Index fetch failed :org.apache.solr.common.SolrException: Unable to
> download segments_znow completely. Downloaded 0!=2217
>
> Thanks & Regards,
> Akreeti Agarwal
>
> -Original Message-
> From: Paras Lehana 
> Sent: Wednesday, September 11, 2019 5:17 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> Hi Akreeti,
>
> Have you tried using the old UI to see errors? I had always experienced
> not seeing status updates about replication in the newer UI. Check for the
> option on top right of Solr UI.
>
> And where are you seeing logs - on solr UI or from a file?
>
> On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:
>
> > In the logs I don't see any errors, mostly after every  1-2 min
> > replication fails and I am not able to identify the root cause for it.
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > -Original Message-
> > From: Jon Kjær Amundsen 
> > Sent: Wednesday, September 11, 2019 12:15 PM
> > To: solr-user@lucene.apache.org
> > Subject: Re: Replication Iteration
> >
> > It depends on the timestamps.
> > The red iterations are failed replications and the green are passed
> > replications.
> > If the newest timestamp is green the latest replication went well, if
> > it is red, it failed.
> >
> > You should check the solr log on the slave if a recent replication
> > have failed to see the cause.
> >
> > Venlig hilsen/Best regards
> >
> > *Jon Kjær Amundsen*
> > Developer
> >
> >
> > Phone: +45 7023 9080
> > E-mail: j...@udbudsvagten.dk
> > Web:
> > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.d
> > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736ad
> > ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416
> > mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved=0
> > Parken - Tårn D - 5. Sal
> > Øster Allé 48 | DK - 2100 København
> >
> > <
> > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.li
> > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hc
> > l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca99
> > 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nxnx
> > ooisjC15hPV5y9NSCgKg%3Dreserved=0
> > >
> >
> > Intelligent Offentlig Samhandel
> > *Før, under og efter udbud*
> >
> > *Følg UdbudsVagten og markedet her Linkedin <
> > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l
> > inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7
> > C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737
> > c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416sdata=zQVT%2
> > FJjMY6GlU4IVHZEMc6P4EWh9MrMcWEybBonKn7w%3Dreserved=0>
> > *
> >
> >
> > Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal  >:
> >
> > > Hi All,
> > >
> > > I am using solr-5.5.5, in which I have one master and two slaves. I
> > > see some red and some green replication iteration on my slave side.
> > > What does these red and green iteration means?
> > > Will this cause problem?
> > >
> > > Thanks & Regards,
> > > Akreeti Agarwal
> > >
> > > ::DISCLAIMER::
> > > 
> > > The contents of this e-mail and any attachment(s) are confidential
> > > and intended for the named recipient(s) only. E-mail transmission is
> > > not guaranteed to be secure or error-free as information could be
> > > intercepted, corrupted, lost, destroyed, arrive late or incomplete,
> > > or may contain viruses in transmission. The e mail and its contents
> > > (with or without referred errors) shall therefore not attach any
> > > liability on the originator or HCL or its affiliates. Views or
> > > opinions, if any, presented in this email are solely those of the
> > > author and may not necessarily reflect the views or opinions of HCL or
> its affiliates.
> > > Any form of reproduction, dissemination, copying, disclosure,
> > > modification, distribution and / or publication of this message
> > > without the prior written consent of authorized representative of
> > > HCL is strictly prohibited. If you have received this email in error
> > > please delete it and notify the sender immediately. 

RE: Replication Iteration

[Akreeti Agarwal]

I am seeing the logs on both UI and file, but I only see this error:

ReplicationHandler
Index fetch failed :org.apache.solr.common.SolrException: Unable to download 
segments_znow completely. Downloaded 0!=2217

Thanks & Regards,
Akreeti Agarwal

-Original Message-
From: Paras Lehana  
Sent: Wednesday, September 11, 2019 5:17 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication Iteration

Hi Akreeti,

Have you tried using the old UI to see errors? I had always experienced not 
seeing status updates about replication in the newer UI. Check for the option 
on top right of Solr UI.

And where are you seeing logs - on solr UI or from a file?

On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:

> In the logs I don't see any errors, mostly after every  1-2 min 
> replication fails and I am not able to identify the root cause for it.
>
> Thanks & Regards,
> Akreeti Agarwal
>
> -Original Message-
> From: Jon Kjær Amundsen 
> Sent: Wednesday, September 11, 2019 12:15 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> It depends on the timestamps.
> The red iterations are failed replications and the green are passed 
> replications.
> If the newest timestamp is green the latest replication went well, if 
> it is red, it failed.
>
> You should check the solr log on the slave if a recent replication 
> have failed to see the cause.
>
> Venlig hilsen/Best regards
>
> *Jon Kjær Amundsen*
> Developer
>
>
> Phone: +45 7023 9080
> E-mail: j...@udbudsvagten.dk
> Web:
> https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.d
> kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736ad
> ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416
> mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved=0
> Parken - Tårn D - 5. Sal
> Øster Allé 48 | DK - 2100 København
>
> <
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.li
> nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hc
> l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca99
> 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nxnx
> ooisjC15hPV5y9NSCgKg%3Dreserved=0
> >
>
> Intelligent Offentlig Samhandel
> *Før, under og efter udbud*
>
> *Følg UdbudsVagten og markedet her Linkedin < 
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l
> inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7
> C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737
> c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416sdata=zQVT%2
> FJjMY6GlU4IVHZEMc6P4EWh9MrMcWEybBonKn7w%3Dreserved=0>
> *
>
>
> Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal :
>
> > Hi All,
> >
> > I am using solr-5.5.5, in which I have one master and two slaves. I 
> > see some red and some green replication iteration on my slave side.
> > What does these red and green iteration means?
> > Will this cause problem?
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > ::DISCLAIMER::
> > 
> > The contents of this e-mail and any attachment(s) are confidential 
> > and intended for the named recipient(s) only. E-mail transmission is 
> > not guaranteed to be secure or error-free as information could be 
> > intercepted, corrupted, lost, destroyed, arrive late or incomplete, 
> > or may contain viruses in transmission. The e mail and its contents 
> > (with or without referred errors) shall therefore not attach any 
> > liability on the originator or HCL or its affiliates. Views or 
> > opinions, if any, presented in this email are solely those of the 
> > author and may not necessarily reflect the views or opinions of HCL or its 
> > affiliates.
> > Any form of reproduction, dissemination, copying, disclosure, 
> > modification, distribution and / or publication of this message 
> > without the prior written consent of authorized representative of 
> > HCL is strictly prohibited. If you have received this email in error 
> > please delete it and notify the sender immediately. Before opening 
> > any email and/or attachments, please check them for viruses and 
> > other
> defects.
> > 
> >
>


--
--
Regards,

*Paras Lehana* [65871]
Software Programmer, Auto-Suggest,
IndiaMART Intermesh Ltd.

8th Floor, Tower A, Advant-Navis Business Park, Sector 142, Noida, UP, IN - 
201303

Mob.: +91-9560911996
Work: 01203916600 | Extn:  *8173*

--
IMPORTANT:
NEVER share your IndiaMART OTP/ Password with anyone.

Re: Replication Iteration

[Paras Lehana]

Hi Akreeti,

Have you tried using the old UI to see errors? I had always experienced not
seeing status updates about replication in the newer UI. Check for the
option on top right of Solr UI.

And where are you seeing logs - on solr UI or from a file?

On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal  wrote:

> In the logs I don't see any errors, mostly after every  1-2 min
> replication fails and I am not able to identify the root cause for it.
>
> Thanks & Regards,
> Akreeti Agarwal
>
> -Original Message-
> From: Jon Kjær Amundsen 
> Sent: Wednesday, September 11, 2019 12:15 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Replication Iteration
>
> It depends on the timestamps.
> The red iterations are failed replications and the green are passed
> replications.
> If the newest timestamp is green the latest replication went well, if it
> is red, it failed.
>
> You should check the solr log on the slave if a recent replication have
> failed to see the cause.
>
> Venlig hilsen/Best regards
>
> *Jon Kjær Amundsen*
> Developer
>
>
> Phone: +45 7023 9080
> E-mail: j...@udbudsvagten.dk
> Web:
> https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.dkdata=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=4GyE5bBQdOoIZW3GH5uB%2FmA1jqzsQqBmJmvg3U6PDsg%3Dreserved=0
> Parken - Tårn D - 5. Sal
> Øster Allé 48 | DK - 2100 København
>
> <
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.linkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=YsXMQqLqxXvwoF3d1Juq9LB60gNT9%2FQSVD3L8y08a%2B4%3Dreserved=0
> >
>
> Intelligent Offentlig Samhandel
> *Før, under og efter udbud*
>
> *Følg UdbudsVagten og markedet her Linkedin <
> https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=Eibo4cubbi%2BTkukH6D9SClTafKzB5Xud2EnJBX9xD0Q%3Dreserved=0>
> *
>
>
> Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal :
>
> > Hi All,
> >
> > I am using solr-5.5.5, in which I have one master and two slaves. I
> > see some red and some green replication iteration on my slave side.
> > What does these red and green iteration means?
> > Will this cause problem?
> >
> > Thanks & Regards,
> > Akreeti Agarwal
> >
> > ::DISCLAIMER::
> > 
> > The contents of this e-mail and any attachment(s) are confidential and
> > intended for the named recipient(s) only. E-mail transmission is not
> > guaranteed to be secure or error-free as information could be
> > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> > may contain viruses in transmission. The e mail and its contents (with
> > or without referred errors) shall therefore not attach any liability
> > on the originator or HCL or its affiliates. Views or opinions, if any,
> > presented in this email are solely those of the author and may not
> > necessarily reflect the views or opinions of HCL or its affiliates.
> > Any form of reproduction, dissemination, copying, disclosure,
> > modification, distribution and / or publication of this message
> > without the prior written consent of authorized representative of HCL
> > is strictly prohibited. If you have received this email in error
> > please delete it and notify the sender immediately. Before opening any
> > email and/or attachments, please check them for viruses and other
> defects.
> > 
> >
>


-- 
-- 
Regards,

*Paras Lehana* [65871]
Software Programmer, Auto-Suggest,
IndiaMART Intermesh Ltd.

8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
Noida, UP, IN - 201303

Mob.: +91-9560911996
Work: 01203916600 | Extn:  *8173*

-- 
IMPORTANT: 
NEVER share your IndiaMART OTP/ Password with anyone.

RE: Replication Iteration

[Akreeti Agarwal]

In the logs I don't see any errors, mostly after every  1-2 min replication 
fails and I am not able to identify the root cause for it.

Thanks & Regards,
Akreeti Agarwal

-Original Message-
From: Jon Kjær Amundsen  
Sent: Wednesday, September 11, 2019 12:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication Iteration

It depends on the timestamps.
The red iterations are failed replications and the green are passed 
replications.
If the newest timestamp is green the latest replication went well, if it is 
red, it failed.

You should check the solr log on the slave if a recent replication have failed 
to see the cause.

Venlig hilsen/Best regards

*Jon Kjær Amundsen*
Developer


Phone: +45 7023 9080
E-mail: j...@udbudsvagten.dk
Web: 
https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.dkdata=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=4GyE5bBQdOoIZW3GH5uB%2FmA1jqzsQqBmJmvg3U6PDsg%3Dreserved=0
Parken - Tårn D - 5. Sal
Øster Allé 48 | DK - 2100 København



Intelligent Offentlig Samhandel
*Før, under og efter udbud*

*Følg UdbudsVagten og markedet her Linkedin 

 *


Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal :

> Hi All,
>
> I am using solr-5.5.5, in which I have one master and two slaves. I 
> see some red and some green replication iteration on my slave side.
> What does these red and green iteration means?
> Will this cause problem?
>
> Thanks & Regards,
> Akreeti Agarwal
>
> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be 
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> may contain viruses in transmission. The e mail and its contents (with 
> or without referred errors) shall therefore not attach any liability 
> on the originator or HCL or its affiliates. Views or opinions, if any, 
> presented in this email are solely those of the author and may not 
> necessarily reflect the views or opinions of HCL or its affiliates. 
> Any form of reproduction, dissemination, copying, disclosure, 
> modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL 
> is strictly prohibited. If you have received this email in error 
> please delete it and notify the sender immediately. Before opening any 
> email and/or attachments, please check them for viruses and other defects.
> 
>

Re: Can you help with this JOIN and OR query?

[Mikhail Khludnev]

Hello, James.
Right. Syntax is cumbersome

q=articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z] {!join to=id
from=url v=$param}=articledate:[2018-09-04T12:00:00Z TO
2019-09-10T11:59:59Z])

On Wed, Sep 11, 2019 at 9:39 AM Smith2, James
 wrote:

> Hi there,
>
> I was hoping that you may be able to assist us with a search issue we're
> facing.
>
> Each one of these queries work on their own:
> articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z]
>
> {!join to=id from=url}articledate:[2018-09-04T12:00:00Z TO
> 2019-09-10T11:59:59Z])
>
> But if we try and combine them in to an or statement:
>
> (articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z] OR {!join
> to=id from=url}articledate:[2018-09-04T12:00:00Z TO 2019-09-10T11:59:59Z])
>
> Then we get a parser error.  The odd thing is that in the second clause,
> if we search for single date then it works, so we were thinking that we had
> the scope of the parser correct.
>
> If you could provide some guidance it'd be most appreciated.,
>
> Kind regards,
>
> James Smith
>
>
>
> IMPORTANT NOTICE:  This email and any attachments may contain information
> that is confidential and privileged. It is intended to be received only by
> persons entitled to receive the information. If you are not the intended
> recipient, please delete it from your system and notify the sender. You
> should not copy it or use it for any purpose nor disclose or distribute its
> contents to any other person.
>
>

-- 
Sincerely yours
Mikhail Khludnev

Re: Replication Iteration

[Jon Kjær Amundsen]

It depends on the timestamps.
The red iterations are failed replications and the green are passed
replications.
If the newest timestamp is green the latest replication went well, if it is
red, it failed.

You should check the solr log on the slave if a recent replication have
failed to see the cause.

Venlig hilsen/Best regards

*Jon Kjær Amundsen*
Developer


Phone: +45 7023 9080
E-mail: j...@udbudsvagten.dk
Web: www.udbudsvagten.dk
Parken - Tårn D - 5. Sal
Øster Allé 48 | DK - 2100 København



Intelligent Offentlig Samhandel
*Før, under og efter udbud*

*Følg UdbudsVagten og markedet her Linkedin
 *


Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal :

> Hi All,
>
> I am using solr-5.5.5, in which I have one master and two slaves. I see
> some red and some green replication iteration on my slave side.
> What does these red and green iteration means?
> Will this cause problem?
>
> Thanks & Regards,
> Akreeti Agarwal
>
> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or may contain
> viruses in transmission. The e mail and its contents (with or without
> referred errors) shall therefore not attach any liability on the originator
> or HCL or its affiliates. Views or opinions, if any, presented in this
> email are solely those of the author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification, distribution and / or
> publication of this message without the prior written consent of authorized
> representative of HCL is strictly prohibited. If you have received this
> email in error please delete it and notify the sender immediately. Before
> opening any email and/or attachments, please check them for viruses and
> other defects.
> 
>

Can you help with this JOIN and OR query?

[Smith2, James]

Hi there,

I was hoping that you may be able to assist us with a search issue we're facing.

Each one of these queries work on their own:
articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z]

{!join to=id from=url}articledate:[2018-09-04T12:00:00Z TO 
2019-09-10T11:59:59Z])

But if we try and combine them in to an or statement:

(articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z] OR {!join to=id 
from=url}articledate:[2018-09-04T12:00:00Z TO 2019-09-10T11:59:59Z])

Then we get a parser error.  The odd thing is that in the second clause, if we 
search for single date then it works, so we were thinking that we had the scope 
of the parser correct.

If you could provide some guidance it'd be most appreciated.,

Kind regards,

James Smith



IMPORTANT NOTICE:  This email and any attachments may contain information that 
is confidential and privileged. It is intended to be received only by persons 
entitled to receive the information. If you are not the intended recipient, 
please delete it from your system and notify the sender. You should not copy it 
or use it for any purpose nor disclose or distribute its contents to any other 
person.