keon94 opened a new issue, #5360:
URL: https://github.com/apache/incubator-devlake/issues/5360

   ## What and why to refactor
   Blueprints are currently stored in a monolithic fashion in the database, 
with the plan and settings stored as encrypted as json blobs within them. The 
blob structure makes searching for blueprints by some blob attribute impossible 
except by querying for all blueprints and brute-force searching through them to 
filter for the one(s) we're looking for. This is bad for performance obviously.
   
   ## Describe the solution you'd like
   Break the plan and settings up into other tables and link them to the BP 
table via IDs. We'll have to decide which columns of these tables should be 
encrypted. At the moment, the main use case will be having at least a 
blueprint_scopes table, which will be referenced by blueprint_connections, 
referenced by blueprint_settings. Having these tables will be the minimum 
requirement of this ticket.  
   
   ## Related issues
   #5153 - introduced brute-force searching for blueprints by scopes. This 
ticket should optimize that.
   
   ## Additional context
   n/a
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to