Re: [GSoC 2018] Ignite backend - Status

2018-08-21 Thread Kevin Ratnasekera
Hi Carlos, I have reviewed your PR [1] added some suggestions, please address them and let s get your work merged to master. This is excellent work Carlos. Thank you for all the hard work you have put into in this summer. [1] https://github.com/apache/gora/pull/134 Regards Kevin On Mon, Jul

Re: [GSoC 2018] Ignite backend - Status

2018-07-22 Thread carlos muñoz
Hi all. I am working on the changes that you guys suggested and other small improvements. I hope I will be pushing my commits by Thursday. In the meantime, I would like to update Gora's Wiki with details of the project within the GSoC section [1], so I would highly appreciate you grant me write

Re: [GSoC 2018] Ignite backend - Status

2018-07-17 Thread Alfonso Nishikawa
@Lewis, @Nishadi, wow you did a very thorough review, congrats =) I was liking your comments, but I guess is better just to say I subscribe all your coments (except one, but already commented :) Loooking forward those changes. Carlos, cheer up! :) Thanks! Regards, Alfonso 2018-07-15 7:05

Re: [GSoC 2018] Ignite backend - Status

2018-07-15 Thread Nishadi Kirielle
Hi Carlos, This is great work..!!! I have gone through your code and added some comments. Please have a look at them and let me know if you need further clarifications. Regards, Nishadi On Sun, Jul 8, 2018 at 1:04 AM Lewis John Mcgibbney < lewis.mcgibb...@gmail.com> wrote: > Hi Carlos, I’ll

Re: [GSoC 2018] Ignite backend - Status

2018-07-07 Thread Lewis John Mcgibbney
Hi Carlos, I’ll reciew by end of weekend this is an excellent effort thank you. Lewis On Sat, Jul 7, 2018 at 07:30 carlos muñoz wrote: > Hi. > > Just a quick update of the project. > > I just have sent a PR [1] with the initial Ignite Backend implementation. > All the tests are passing, but I

Re: [GSoC 2018] Ignite Backend - Status

2018-06-26 Thread Alfonso Nishikawa
Hi, Carlos. Nice analysis. It looks a good to me to start with the serialized approach. Personally, I tend to be too much ambitious, so I encourage to keep it simple :) Reading your analysis brings me lots of ideas (always time consuming ideas), like creating two Stores for each case with

Re: [GSoC 2018] Ignite Backend - Status

2018-06-25 Thread carlos muñoz
Hi all As Alfonso mentioned the Ignite backend could implement the 3-union fields either by using joined tables or storing serialized objects as binary. Here some comments on those approaches. Using joined tables would definitely has an impact in performance due the fact distributed joins [1]

Re: [GSoC 2018] Ignite Backend - Status

2018-06-06 Thread Alfonso Nishikawa
Hi, Carlos. About the mapping files and the fields 'boss' and 'webpage', yes, they reference two other Persistent entities. You can see the schema of Employee [1], were it has a boss (referencing itself) and a webpage (with the WebPage schema defined there). How to handle this depends on the