Issue with an oak index using snonym filter | Community
Skip to main content
lksfjhadfas
lksfjhadfas
Level 2
Oct 12, 2018 2:05 PM UTC
Solved

Issue with an oak index using snonym filter

Hey guys,

I have a custom index which is working totally fine if i do not add any analyzers to it. I added an analyzer for adding a synonym to return similar results for "fact sheets" and factsheets. Index stopped working after that.

Any help with it is appreciated.

Thank you!

Here is the index

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:oak="http://jackrabbit.apache.org/oak/ns/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"

          jcr:primaryType="oak:Unstructured"

          async="async"

          compatVersion="{Long}2"

          evaluatePathRestrictions="{Boolean}true"

          reindex="{Boolean}true"

          type="lucene">

    <indexRules jcr:primaryType="nt:unstructured">

        <nt:base

            jcr:primaryType="nt:unstructured"

            includePropertyTypes="all">

            <properties jcr:primaryType="nt:unstructured">

                <literatureTitle name="literatureTitle"

                    analyzed="{Boolean}true"

                    ordered="{Boolean}true"

                    jcr:primaryType="nt:unstructured"/>

                <displayContentTypename name="displayContentTypename"

                    analyzed="{Boolean}true"

                    jcr:primaryType="nt:unstructured"/>

            </properties>

        </nt:base>

    </indexRules>

    <analyzers jcr:primaryType="nt:unstructured">

        <default jcr:primaryType="nt:unstructured">

            <filters jcr:primaryType="nt:unstructured">

                <LowerCase jcr:primaryType="nt:unstructured"/>

                <Synonym jcr:primaryType="nt:unstructured"

                synonyms="synonym.txt">

                    <synonym.txt/>

                </Synonym>

            </filters>

        </default>

    </analyzers>

</jcr:root>

and in synonym.txt i have

fact sheets, factsheets

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Employee
Oct 15, 2018 8:16 PM UTC

As I read the docs [1], you should have the synonyms.txt as nt:file in the "Synonym" node; and is there a "classicTokenizerFactory"? I would try with "name" :"Classic" (uppercase).

Jörg

[1] Jackrabbit Oak – Lucene Index

View reply

14 replies

lksfjhadfas
lksfjhadfasAuthor
Level 2
Oct 16, 2018 1:41 PM UTC

I am able to get the results back. I also had to add lowercase filter for it to work. Thank you so much Jörg Hoh​.

Translate
joerghoh
joerghohAccepted solution
Employee
Oct 15, 2018 8:16 PM UTC

As I read the docs [1], you should have the synonyms.txt as nt:file in the "Synonym" node; and is there a "classicTokenizerFactory"? I would try with "name" :"Classic" (uppercase).

Jörg

[1] Jackrabbit Oak – Lucene Index

Translate
    lksfjhadfas
    lksfjhadfasAuthor
    Level 2
    Oct 15, 2018 6:43 PM UTC

    Here is the JSON of the index

    "faiLiteratureIndex":{

       "jcr:primaryType":"oak:QueryIndexDefinition",

       "compatVersion":2,

       "type":"lucene",

       "async":"async",

       "evaluatePathRestrictions":true,

       "reindex":true,

       "indexRules":{

          "jcr:primaryType":"nt:unstructured",

          "nt:base":{

             "jcr:primaryType":"nt:unstructured",

             "includePropertyTypes":"all",

             "properties":{

                "jcr:primaryType":"nt:unstructured",

                "literatureTitle":{

                   "jcr:primaryType":"nt:unstructured",

                   "ordered":true,

                   "analyzed":true,

                   "name":"literatureTitle"

                },

                "displayContentTypename":{

                   "jcr:primaryType":"nt:unstructured",

                   "analyzed":true,

                   "name":"displayContentTypename"

                }

             }

          }

       },

       "analyzers":{

          "jcr:primaryType":"nt:unstructured",

          "default":{

             "jcr:primaryType":"nt:unstructured",

             "filters":{

                "jcr:primaryType":"nt:unstructured",

                "Synonym":{

                   "jcr:primaryType":"nt:unstructured",

                   "synonyms":"synonym.txt"

                }

             },

             "tokenizer":{

                "jcr:primaryType":"nt:unstructured",

                "name":"classic"

             }

          }

       }

    }

    Translate
    joerghoh
    joerghoh
    Employee
    Oct 15, 2018 6:35 PM UTC

    Can you please provide your complete index definition (e.g. as JSON dump)? It's hard to guess just from this snippet what could be wrong.

    Translate
    lksfjhadfas
    lksfjhadfasAuthor
    Level 2
    Oct 15, 2018 6:29 PM UTC

    After i changed the node type, i had to add a tokenizer for the index to be reindexes.

    <analyzers jcr:primaryType="nt:unstructured">

            <default

                jcr:primaryType="nt:unstructured">

                <filters jcr:primaryType="nt:unstructured">

                    <Synonym jcr:primaryType="nt:unstructured"

                        synonyms="synonym.txt">

                        <synonym.txt/>

                    </Synonym>

                </filters>

                <tokenizer jcr:primaryType="nt:unstructured"

                           name="classic"/>

            </default>

        </analyzers>

    now i can re index but i am not getting any results back using this index.

    Translate
    lksfjhadfas
    lksfjhadfasAuthor
    Level 2
    Oct 15, 2018 5:28 PM UTC

    Nvm i had to delete the existing index for it to take the new node type. I will try adding the synonym now and see if it works and let you know.

    Thanks!

    Translate
    lksfjhadfas
    lksfjhadfasAuthor
    Level 2
    Oct 15, 2018 3:42 PM UTC

    If i use the oak:queryIndexDefinition, it gives me a "javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: The primary type null does not exist (500)" error. I am not sure what the issue is.

    Translate
    joerghoh
    joerghoh
    Employee
    Oct 13, 2018 11:33 AM UTC

    Ok, so if you add these additional settings and you try to reindex, the reindexing is not starting? Just from looking at the index definition I would assume that the nodetype of the index definition itself (/oak:index/customIndex) is wrong; it should not be "nt:unstructured" but rather "oak:queryIndexDefinition".

    Jörg

    Translate
      lksfjhadfas
      lksfjhadfasAuthor
      Level 2
      Oct 12, 2018 7:30 PM UTC

      when i try to reindex it, it just stays true and doesnt change to false and i dont see anything in the logs either.

      Translate
      joerghoh
      joerghoh
      Employee
      Oct 12, 2018 7:03 PM UTC

      What do you mean with "it stopped working"? Any exceptions? What change in behaviour did you find when you changed the index definition?

      Translate
      Show more replies
      Terms & ConditionsAccessibility statement

      Loading footer...