Addshore added a comment.

  In T301471#7714044 <https://phabricator.wikimedia.org/T301471#7714044>, @Joe 
wrote:
  
  > You also say the service will need to read an index file. How is that 
generated?
  
  This is currently generated using this go code 
https://github.com/martaannaj/SchemaTreeBuilder
  
  > Where do you plan to store / retreive it? For an A/B test baking the file 
into the application images might be ok, but long-term we might need to move 
the data to a datastore instead.
  
  I would also propose including it in the image for now and thinking about 
loading it from some other data store in the future.
  This index will likley only get updated once a month or so, as with the 
current property suggester data (but that lands in an SQL table).
  
  In terms of loading it into the image, I'm not quite sure how it may be best 
to do that? 
  I guess we don't want to load it into the git repo along side the service 
itself.
  Does anyone have a good idea?
  
  In T301471#7714171 <https://phabricator.wikimedia.org/T301471#7714171>, 
@Michaelcochez wrote:
  
  > @Addshore can you elaborate on how we could create the index file? Since 
this is not something we have to recreate often it might even be worth 
recreating the application image each time we recreate the index.
  
  +1 I think the the initial version and A/B test we should aim to just include 
it in the image as long as @Joe is okay with this

TASK DETAIL
  https://phabricator.wikimedia.org/T301471

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Addshore
Cc: ItamarWMDE, Joe, Aklapper, Addshore, karapayneWMDE, Martaannaj, 
Michaelcochez, Arnoldokoth, Invadibot, maantietaja, wkandek, JMeybohm, 
Akuckartz, Nandana, jijiki, Lahi, Gq86, GoranSMilovanovic, QZanden, 
LawExplorer, _jensen, rosalieper, Scott_WUaS, Eevans, Hardikj, Wikidata-bugs, 
aude, Sjoerddebruin, Jdforrester-WMF, Mbch331, Jay8g, Dzahn
_______________________________________________
Wikidata-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to