Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-5997

Index update after schema change

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • RHDG 8.4.2 GA
    • RHDG 8.4.1 GA
    • Indexing
    • False
    • None
    • False
    • CR1
    • Hide

      Client to add an entry and run a query with "order by x.mySortField"
      one schema with sortable true and one with false for the mySortable field.

       

      Show
      Client to add an entry and run a query with "order by x.mySortField" one schema with sortable true and one with false for the mySortable field. Run the server and add the schema without sortable=true run the client to see the ISPN014827 message change the schema (sortable trur)    curl -X PUT --data-binary @message.proto http://127.0.0.1:11222/rest/v2/schemas/message run the mass indexer and see the server log messages   curl -X POST http://127.0.0.1:11222/rest/v2/caches/IckleMessageCache/search/indexes?action=mass-index run the client again to see the message ISPN014827 is still show  

      If a schema is change for a query with order by, to be sortable the running server will show the message

      "ISPN014827: Distributed sort not supported for non-indexed query 'FROM playground.Message ORDER BY reader'. Consider using an index for optimal performance."

      even if the schema has changed to @BASIC(sortable=true) and the index is rebuild with the mass indexer

       

        1. Screenshot from 2023-04-03 11-48-01.png
          Screenshot from 2023-04-03 11-48-01.png
          27 kB

              fercoli@redhat.com Fabio Massimo Ercoli
              rhn-support-wfink Wolf Fink
              Fabrizio Asta Fabrizio Asta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: