You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "machristie (via GitHub)" <gi...@apache.org> on 2023/02/01 20:43:49 UTC

[GitHub] [airavata-data-catalog] machristie opened a new issue, #3: Evaluate the overhead (absolute and relative) of loading JSONB documents with and without a GIN index

machristie opened a new issue, #3:
URL: https://github.com/apache/airavata-data-catalog/issues/3

   This came up in the design review. From Amila:
   
   > 1. The performance -- each time we insert/update documents the inverted index needs to be re-build. If we are are re-building the inverted index synchronously, the api call might need to wait more time. Asyncrhounous updates might be more suitable.
   
   Perhaps we can do asynchronous updates, but first I think it would be good to quantify what overhead there is with updating the GIN index each time a JSONB document (i.e., the `metadata` column) is inserted into the data_product table.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@airavata.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org