LSCS Query Issue on [:>=] and [:<=] regular expressions

Hi,

We are facing an issue with LSCS query which contains regular expressions like [: > =] and [: < =] to fire greater/less than values using metadata, with this scenario the lscs document is returning inconsistent result while querying through debug panel.

Example: we are querying across (TeamSite/Metadata/property-listing/price: > =10000) and which is returning attached set of documents from LSCS repository using debug panel.

I have tried below set of scenarios :

Updated lscs-authoring.xml mapping the attribute type as integer along with the metadata name inside <attributeinfo> node.

After changing the lscs-authoring.xml file, I am trying to get metadata information using http://<Servername>:1876/lscs/v1/metadata-info and metadata info not been updated with the new metadata TeamSite/Metadata/property-listing/price as a type integer which returns string type after changing the lscs-authoring.xml.(<field name="TeamSite/Metadata/property-listing/price" type="string" multivalued="true" facet="false" mvfDelimiter=";" internal="false"/>)

This particular issue is not related to property-listing /price metadata, this is common across TeamSite 8.1 and TeamSite 7.3 versions.

Any pointers would be of great help.

Thanks

Sathya

Find more posts tagged with

Comments

nipper

We use > < all the time for Start_Date/End_Date and have very complex queries.

End_Date Smiley Embarassed =2016-06-03

Start_Date:<=2016-06-03

When you changed the Idol settings, did you redeploy the content ? I do not think it will reindex those changes without deploying it. Dropping the project and running a deploy all script may be the best.

Sathya

Thanks Andy,

I Got a solution,

By default, fields are indexed as Strings so that can lead to inconsistent results when doing greater/less than some value,The fix is the metadata type needs to be “numeric” not “Integer” (needs to change inlscs-authoring.xml). However, if there are published records with this attribute as a String, it will never allow you to change that type of field.

Your options are basically,
Purge any LSCS projects containing that field, then republish your content with the new data format; or
Rename your EA to something new
The same would apply to date fields, although if you’ve used YYYY-MM-DD format then they sort just fine as strings.