Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@manifoldcf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKoYS6K-_z7ai4xR=2dOE7MByJM=+_cJQX0Ok+zAsEdAgUzZDw@mail.gmail.com>
References: 
 <CAKoYS6KYqJSJbXUZeDWjfDjiXo-rLfX7nK2ohjLsNc+xU9EJiw@mail.gmail.com>
	<CALUFAGAsV3-Wn-+wmFPt68XkGiACS1Y+XrGZeizQmP+o=aAuSQ@mail.gmail.com>
	<CALUFAGC0qC6jvPqFZhkCm7kph_kwpSvr9DSAzEcnXkj=4Cwh+g@mail.gmail.com>
	<CAKoYS6JbttnhD9Tea3Ar2FQwpv4hRLZwE2tN7Wpge-CVG2ie=A@mail.gmail.com>
	<CALUFAGAVSzkLdNmpn7+PYJ3jjzNgOXhTccT5G11W8iwLx5zD=w@mail.gmail.com>
	<CALUFAGB8TPQtdf-+0JG_hck9bBs-XHtTHPuM9yC92tc+nLqPhQ@mail.gmail.com>
	<CAKoYS6+VGHBc1wc314bqBXf3_ut-NSh=xqSTfiu3seqOY8X1Vw@mail.gmail.com>
	<CALUFAGCjKNV_+pyp5=gFA5t0JrS8dhrkXa4cZWjJ2xhpM+x07Q@mail.gmail.com>
	<CALUFAGCQf=E6Z_V5vi9xWM5QbLP32MghdEqGvH5S0e9-T=iGHw@mail.gmail.com>
	<CAKoYS6KqKRUPS15TK7wMDHebMaqLmoGeqWyhRKDYDnPVLoLcxw@mail.gmail.com>
	<CALUFAGDjZRWc4OdJVykHVtUvmGjUF-QfN2UpTxLY2-rWyx+a8A@mail.gmail.com>
	<CALUFAGAXiH48ePf7PA_kV1PCqbHPoxrwvKhbXw2cuo7wDtFaOg@mail.gmail.com>
	<CAKoYS6+Ak_w5Zosc7wMqwZ-Fre9zpS3UNaTn=TvWao8L2F+sBg@mail.gmail.com>
	<CALUFAGA9_xzbvuu8y27ZzwsSD9Dq4D+aBw0-OTGM8bMA5OPRsw@mail.gmail.com>
	<CAKoYS6K-_z7ai4xR=2dOE7MByJM=+_cJQX0Ok+zAsEdAgUzZDw@mail.gmail.com>
Date: Tue, 4 Nov 2014 18:15:20 +0000
Message-ID: 
 <CAKoYS6Jzfsh6ArYHaPRgoGREDULZDHcFX8Y3ARV-ODrmr_Kz=w@mail.gmail.com>
Subject: Re: (Continuous) crawl performance
From: Aeham Abushwashi <aeham.abushwashi@exonar.com>
To: dev@manifoldcf.apache.org
Content-Type: multipart/alternative; boundary=bcaec548586e2f4f7505070c723a

--bcaec548586e2f4f7505070c723a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Karl,

After applying the 1.7.2 revisions for CONNECTORS-1090, -1091, -1092 and
-1093 to my 1.6.1 branch, if I create a new crawl, then its documents get
picked up by the next scan; however, that doesn't happen for an existing
crawl. The docpriority for documents in the existing craw is still at
1000000001.

I believe the priority should be set by
ManifoldCF#resetAllDocumentPriorities but it's not, because
JobManager#getNextNotYetProcessedReprioritizationDocuments returns no rows
to update, which I think is due to the legacy job's docs having a
priorityset of NULL. Replacing the current priorityset condition in
JobManager#getNextNotYetProcessedReprioritizationDocuments with
(priorityset IS NULL OR priorityset<?) addresses this specific issue.
Is this a valid fix or do you see it introducing undesirable behaviour or
masking an issue elsewhere?

Cheers,
Aeham
=E2=80=8B

--bcaec548586e2f4f7505070c723a--