Guest User

Untitled

a guest
Jun 21st, 2018
74
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.82 KB | None | 0 0
  1. <jmayfield> hey.. looking at riak for a project, vfx/film asset mgmt.
  2. i've implemented such system using traditional rdbms backends,
  3. and it always feels like a fight with complexity
  4.  
  5. 13:41 <jmayfield> i am new to this world of nosql etc, but at a glance,
  6. riak seems like a very good potential fit for this stuff
  7.  
  8. 13:43 <benblack> what sort of trouble did you have with rdbms backends?
  9.  
  10. 13:49 <jmayfield> complex schemas, for starters
  11.  
  12. 13:49 <benblack> what made them complex?
  13.  
  14. 13:49 <seldo> jmayfield: the design of the schema is not really
  15. intrinsic to the data store
  16.  
  17. 13:49 <benblack> hrm
  18.  
  19. 13:50 <benblack> seldo: kind of disagree with you there
  20.  
  21. 13:50 <jmayfield> uses contant need to new data structures, mods to existing ones, etc
  22.  
  23. 13:50 <jmayfield> for example
  24.  
  25. 13:50 <benblack> are the assets going into the db, or just metadata?
  26.  
  27. 13:51 <jmayfield> depends, usually metadata
  28.  
  29. 13:53 <benblack> without something more specific i can't really offer much advice
  30.  
  31. 13:54 <jmayfield> yeah, i know
  32.  
  33. 13:54 <jmayfield> hehe
  34.  
  35. 13:59 <jmayfield> well, heres a typical problem.. nested assets, where
  36. some of the nested assets have data mods per context (how/where they are nested)
  37.  
  38. 14:04 <benblack> often best handled in riak with links
  39.  
  40. 14:05 <benblack> rather than trying to directly nest in a single document
  41.  
  42. 14:05 <jmayfield> right
  43.  
  44. 14:07 <jmayfield> i like the link stuff for sure
  45.  
  46. 14:07 <jmayfield> feels similar to playing with symlinks in an fs..or maybe i am totally wrong
  47.  
  48. 14:07 <jmayfield> hehe
  49.  
  50. 14:10 <jmayfield> maybe the fs analogy works foro what i am getting at. you have
  51. assets (real files) that need to be plopped into collections (folders full of symlinks)..
  52. with the added requirement of being able to mod/extend the sylinked file when in folder
  53. A vs folder B
  54.  
  55. 14:11 <benblack> sounds fine
  56.  
  57. 14:27 <pete_lacey> Hope you guys don't mind if I do a hit and run, but I have a
  58. question about the ruby library for Riak. Does it support named functions? If
  59. o, what's the syntax for calling them. Googled around and came up dry.
  60.  
  61.  
  62. 14:30 <jmayfield> benblack, how might one think about something like that with riak..
  63. when asset b is linked to asset a, asset b has some different value for x? (assuming yuo
  64. have the time/interest in helping me and my vagueness)
  65.  
  66. 14:40 <benblack> jmayfield: don't understand the question. links are links.
  67.  
  68. 14:44 <jmayfield> benblack, if asset b has attr1 and attr2, i want attr1 to be somethng else
  69. when it comes from a link on asset a, yet if somebody mods attr2 on asset a, i get that change.. hehe
  70.  
  71. 14:45 <benblack> then i recommend you implement that in your app
  72.  
  73. 14:45 <jmayfield> i am just trying to get a grip on how theses sorts of things might be
  74. accomplish
  75.  
  76. 14:45 <jmayfield> sure
  77.  
  78. 14:47 <jmayfield> i have just had my head in postgres/mysql for years.. trying to rethink
  79. this data stuff.. heh
Add Comment
Please, Sign In to add comment