Denis, I have also added a doc titled 'Fast Updates' - it's a separate document and it's hidden for now, please find the link to it in dash at the bottom of 'SQL Grid' section on the left. It describes an optimization technique that allows to run particular queries with performance of bare cache operations reducing SQL related overhead to nearly none at all. Hence I thought it was important to describe this feature. Please review it and include into main doc as your heart desires.
- Alex 2016-12-23 14:42 GMT+03:00 Alexander Paschenko <alexander.a.pasche...@gmail.com>: > Denis, Prachi, > > All links from ToC to subsections are broken on this page: > http://apacheignite.gridgain.org/docs/dml > > - Alex > > 2016-12-23 3:54 GMT+03:00 Prachi Garg <pg...@gridgain.com>: >> Sure, will look into it. >> >> -P >> >> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <dma...@apache.org> wrote: >> >>> I’ve finished the review and released all the parts of DML documentation >>> [1]. >>> >>> Prachi, could you review whole SQL Grid documentation [2] including [1]? >>> Also it will be great if you check this newly added section [3]. >>> >>> [1] http://apacheignite.gridgain.org/docs/dml >>> [2] http://apacheignite.gridgain.org/docs/sql-grid >>> [3] http://apacheignite.gridgain.org/docs/binary- >>> marshaller#handling-hash-code-generation-and-equals-execution >>> >>> — >>> Denis >>> >>> On Dec 9, 2016, at 12:34 AM, Alexander Paschenko < >>> alexander.a.pasche...@gmail.com> wrote: >>> >>> Denis, >>> >>> About your question: 'putIfAbsent' is used only when we have single >>> key-value pair to process as long as we don't have method like 'put >>> all if absent'. When there's a bunch of pairs, an entry processor is >>> created for each pair to make its processing atomic (effectively CAS >>> style processing), and all those processors are then executed via >>> 'invokeAll'. >>> >>> - Alex >>> >>> 2016-12-09 8:17 GMT+03:00 Denis Magda <dma...@apache.org>: >>> >>> Alexander, thanks for all the material you’ve prepared so far. >>> >>> Actually, I’ve reviewed, restructured and released only a part of it [1]. >>> >>> The rest, that is missing, requires more time from my side and I’ll be >>> releasing additional blocks throughout the next week. The full >>> documentation >>> with the unreviewed parts is invisible and located here [2]. >>> >>> Please don’t modify neither of the docs ([1] and [2]) until I’ve finished >>> with the overall review. Send all your suggestions over the email. >>> >>> At the moment I have the following question. What cache method(s) do we >>> convert INSERT statements to [3]? Is it ‘putIfAbsent’? >>> >>> [1] https://apacheignite.readme.io/docs/dml >>> [2] https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe >>> [3] https://apacheignite.readme.io/docs/dml#section-insert >>> >>> — >>> Denis >>> >>> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko >>> <alexander.a.pasche...@gmail.com> wrote: >>> >>> Denis, >>> >>> it's all ready, JDBC driver page is also updated (I've created a >>> hidden clone page, please find it on the left) as well as one on >>> binary marshaller. Also I've renamed 'distributed DML' page to just >>> 'DML' as long as there's much less to distribution of DML operations >>> themselves than to queries and there's clearly no need to make another >>> doc page to distinguish. Removed batches mention from limitations. >>> >>> - Alex >>> >>> 2016-12-08 5:26 GMT+03:00 Denis Magda <dma...@apache.org>: >>> >>> Alexander, >>> >>> How close are you to the finalization of the DML doc? >>> https://apacheignite.readme.io/docs/distributed-dml >>> >>> Since we’re approaching 1.8 release I would like to do a final review of it >>> polishing whatever is needed tomorrow. >>> >>> As I see that only the limitations section is left. The first note is that >>> I >>> wouldn’t mention “JDBC Batching mode” for now because this is something >>> that >>> doesn’t affect the usability and SQL API's scope of support. >>> >>> — >>> Denis >>> >>> >>>
