DML Documentation Readiness
Locked
 
|
Alexander,
How close are you to the finalization of the DML doc? https://apacheignite.readme.io/docs/distributed-dml <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 |
|
|
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 <https://apacheignite.readme.io/docs/dml> [2] https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe <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 <[hidden email]> 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 <[hidden email]>: >> 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 >> >> |
|
|
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 <[hidden email]>: > 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 > <[hidden email]> 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 <[hidden email]>: > > 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 > > > |
|
|
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 <http://apacheignite.gridgain.org/docs/dml> [2] http://apacheignite.gridgain.org/docs/sql-grid <http://apacheignite.gridgain.org/docs/sql-grid> [3] http://apacheignite.gridgain.org/docs/binary-marshaller#handling-hash-code-generation-and-equals-execution <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 <[hidden email]> 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 <[hidden email] <mailto:[hidden email]>>: >> 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 <https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe> >> [3] https://apacheignite.readme.io/docs/dml#section-insert <https://apacheignite.readme.io/docs/dml#section-insert> >> >> — >> Denis >> >> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko >> <[hidden email]> 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 <[hidden email]>: >> >> 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 |
|
|
Sure, will look into it.
-P On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < > [hidden email]> 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 <[hidden email]>: > > 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 > <[hidden email]> 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 <[hidden email]>: > > 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 > > > |
|
|
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 <[hidden email]>: > Sure, will look into it. > > -P > > On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < >> [hidden email]> 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 <[hidden email]>: >> >> 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 >> <[hidden email]> 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 <[hidden email]>: >> >> 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 >> >> >> |
|
|
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 <[hidden email]>: > 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 <[hidden email]>: >> Sure, will look into it. >> >> -P >> >> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < >>> [hidden email]> 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 <[hidden email]>: >>> >>> 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 >>> <[hidden email]> 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 <[hidden email]>: >>> >>> 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 >>> >>> >>> |
|
In reply to this post by dmagda
Denis, I cannot access the links. Are you sure they are correct?
On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < > http://apacheignite.gridgain.org/docs/dml> > [2] http://apacheignite.gridgain.org/docs/sql-grid < > http://apacheignite.gridgain.org/docs/sql-grid> > [3] http://apacheignite.gridgain.org/docs/binary-marshaller# > handling-hash-code-generation-and-equals-execution < > 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 < > [hidden email]> 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 <[hidden email] <mailto: > [hidden email]>>: > >> 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 < > https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe> > >> [3] https://apacheignite.readme.io/docs/dml#section-insert < > https://apacheignite.readme.io/docs/dml#section-insert> > >> > >> — > >> Denis > >> > >> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko > >> <[hidden email]> 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 <[hidden email]>: > >> > >> 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 > > |
|
|
Readme.io team broke something in the legacy version of the doc engine that we used. As a result navigation was broken completely. I had to migrate all our docs to the latest version of their product which is 2.0 in order to fix this. Presently I’m reaching them our in order to apply the appearance we had before.
The valid links are the following: [1] https://apacheignite.readme.io/docs/dml [2] https://apacheignite.readme.io/docs/sql-grid [3] https://apacheignite.readme.io/docs/binary-marshaller#handling-hash-code-generation-and-equals-execution — Denis > On Dec 23, 2016, at 9:23 AM, Dmitriy Setrakyan <[hidden email]> wrote: > > Denis, I cannot access the links. Are you sure they are correct? > > On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < >> http://apacheignite.gridgain.org/docs/dml> >> [2] http://apacheignite.gridgain.org/docs/sql-grid < >> http://apacheignite.gridgain.org/docs/sql-grid> >> [3] http://apacheignite.gridgain.org/docs/binary-marshaller# >> handling-hash-code-generation-and-equals-execution < >> 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 < >> [hidden email]> 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 <[hidden email] <mailto: >> [hidden email]>>: >>>> 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 < >> https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe> >>>> [3] https://apacheignite.readme.io/docs/dml#section-insert < >> https://apacheignite.readme.io/docs/dml#section-insert> >>>> >>>> — >>>> Denis >>>> >>>> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko >>>> <[hidden email]> 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 <[hidden email]>: >>>> >>>> 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 >> >> |
|
|
In reply to this post by al.psc
Alex, great! Thanks for sharing more details about DML feature.
I’ll put this new content on this page after the review is finished https://apacheignite.readme.io/docs/performance-and-debugging <https://apacheignite.readme.io/docs/performance-and-debugging> — Denis > On Dec 23, 2016, at 6:13 AM, Alexander Paschenko <[hidden email]> wrote: > > 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 > <[hidden email]>: >> 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 <[hidden email]>: >>> Sure, will look into it. >>> >>> -P >>> >>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < >>>> [hidden email]> 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 <[hidden email]>: >>>> >>>> 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 >>>> <[hidden email]> 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 <[hidden email]>: >>>> >>>> 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 >>>> >>>> >>>> |
|
|
Shouldn't the URL be "sql-performance-and-debugging"?
On Fri, Dec 23, 2016 at 10:30 AM, Denis Magda <[hidden email]> wrote: > Alex, great! Thanks for sharing more details about DML feature. > > I’ll put this new content on this page after the review is finished > https://apacheignite.readme.io/docs/performance-and-debugging < > https://apacheignite.readme.io/docs/performance-and-debugging> > > — > Denis > > > On Dec 23, 2016, at 6:13 AM, Alexander Paschenko < > [hidden email]> wrote: > > > > 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 > > <[hidden email]>: > >> 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 <[hidden email]>: > >>> Sure, will look into it. > >>> > >>> -P > >>> > >>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> > 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 < > >>>> [hidden email]> 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 <[hidden email]>: > >>>> > >>>> 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 > >>>> <[hidden email]> 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 <[hidden email]>: > >>>> > >>>> 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 > >>>> > >>>> > >>>> > > |
|
|
The URL will be the same as the name of the page which is “Performance and Debugging”. I wouldn’t not rename the page because it’s already located under “SQL Grid” section. However, even if we rename the page the URL will be left the same. This is how readme.io works.
— Denis > On Dec 23, 2016, at 10:33 AM, Dmitriy Setrakyan <[hidden email]> wrote: > > Shouldn't the URL be "sql-performance-and-debugging"? > > On Fri, Dec 23, 2016 at 10:30 AM, Denis Magda <[hidden email]> wrote: > >> Alex, great! Thanks for sharing more details about DML feature. >> >> I’ll put this new content on this page after the review is finished >> https://apacheignite.readme.io/docs/performance-and-debugging < >> https://apacheignite.readme.io/docs/performance-and-debugging> >> >> — >> Denis >> >>> On Dec 23, 2016, at 6:13 AM, Alexander Paschenko < >> [hidden email]> wrote: >>> >>> 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 >>> <[hidden email]>: >>>> 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 <[hidden email]>: >>>>> Sure, will look into it. >>>>> >>>>> -P >>>>> >>>>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> >> 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 < >>>>>> [hidden email]> 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 <[hidden email]>: >>>>>> >>>>>> 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 >>>>>> <[hidden email]> 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 <[hidden email]>: >>>>>> >>>>>> 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 >>>>>> >>>>>> >>>>>> >> >> |
|
|
On Fri, Dec 23, 2016 at 10:40 AM, Denis Magda <[hidden email]> wrote:
> The URL will be the same as the name of the page which is “Performance and > Debugging”. I wouldn’t not rename the page because it’s already located > under “SQL Grid” section. However, even if we rename the page the URL will > be left the same. This is how readme.io works. > I would actually rename the page to SQL Performance and Debugging for better clarity. I also believe I have changed the URL before in readme. If there is no way, we can always create another page. My main concern here is that the page name is too generic and will conflict with other similar pages in other sections. > > On Dec 23, 2016, at 10:33 AM, Dmitriy Setrakyan <[hidden email]> > wrote: > > > > Shouldn't the URL be "sql-performance-and-debugging"? > > > > On Fri, Dec 23, 2016 at 10:30 AM, Denis Magda <[hidden email]> wrote: > > > >> Alex, great! Thanks for sharing more details about DML feature. > >> > >> I’ll put this new content on this page after the review is finished > >> https://apacheignite.readme.io/docs/performance-and-debugging < > >> https://apacheignite.readme.io/docs/performance-and-debugging> > >> > >> — > >> Denis > >> > >>> On Dec 23, 2016, at 6:13 AM, Alexander Paschenko < > >> [hidden email]> wrote: > >>> > >>> 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 > >>> <[hidden email]>: > >>>> 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 <[hidden email]>: > >>>>> Sure, will look into it. > >>>>> > >>>>> -P > >>>>> > >>>>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> > >> 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 < > >>>>>> [hidden email]> 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 <[hidden email]>: > >>>>>> > >>>>>> 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 > >>>>>> <[hidden email]> 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 <[hidden email]>: > >>>>>> > >>>>>> 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 > >>>>>> > >>>>>> > >>>>>> > >> > >> > > |
|
|
Denis,
The page slug can be changed in readme.io. I have renamed the url - http://apacheignite.gridgain.org/v1.8/docs/sql-performance-and-debugging On Mon, Dec 26, 2016 at 9:55 PM, Dmitriy Setrakyan <[hidden email]> wrote: > On Fri, Dec 23, 2016 at 10:40 AM, Denis Magda <[hidden email]> wrote: > > > The URL will be the same as the name of the page which is “Performance > and > > Debugging”. I wouldn’t not rename the page because it’s already located > > under “SQL Grid” section. However, even if we rename the page the URL > will > > be left the same. This is how readme.io works. > > > > I would actually rename the page to SQL Performance and Debugging for > better clarity. I also believe I have changed the URL before in readme. If > there is no way, we can always create another page. My main concern here is > that the page name is too generic and will conflict with other similar > pages in other sections. > > > > > On Dec 23, 2016, at 10:33 AM, Dmitriy Setrakyan <[hidden email] > > > > wrote: > > > > > > Shouldn't the URL be "sql-performance-and-debugging"? > > > > > > On Fri, Dec 23, 2016 at 10:30 AM, Denis Magda <[hidden email]> > wrote: > > > > > >> Alex, great! Thanks for sharing more details about DML feature. > > >> > > >> I’ll put this new content on this page after the review is finished > > >> https://apacheignite.readme.io/docs/performance-and-debugging < > > >> https://apacheignite.readme.io/docs/performance-and-debugging> > > >> > > >> — > > >> Denis > > >> > > >>> On Dec 23, 2016, at 6:13 AM, Alexander Paschenko < > > >> [hidden email]> wrote: > > >>> > > >>> 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 > > >>> <[hidden email]>: > > >>>> 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 <[hidden email]>: > > >>>>> Sure, will look into it. > > >>>>> > > >>>>> -P > > >>>>> > > >>>>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> > > >> 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 < > > >>>>>> [hidden email]> 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 <[hidden email]>: > > >>>>>> > > >>>>>> 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 > > >>>>>> <[hidden email]> 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 <[hidden email]>: > > >>>>>> > > >>>>>> 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 > > >>>>>> > > >>>>>> > > >>>>>> > > >> > > >> > > > > > |
|
|
In reply to this post by al.psc
Alexander, thanks for such a useful section. I’ve reviewed it and added to the page existed before
http://apacheignite.gridgain.org/v1.8/docs/sql-performance-and-debugging#section-advanced-dml-optimizations <http://apacheignite.gridgain.org/v1.8/docs/sql-performance-and-debugging#section-advanced-dml-optimizations> The page you created before for `Fast Updates` was removed. — Denis > On Dec 23, 2016, at 6:13 AM, Alexander Paschenko <[hidden email]> wrote: > > 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 > <[hidden email]>: >> 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 <[hidden email]>: >>> Sure, will look into it. >>> >>> -P >>> >>> On Thu, Dec 22, 2016 at 4:00 PM, Denis Magda <[hidden email]> 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 < >>>> [hidden email]> 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 <[hidden email]>: >>>> >>>> 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 >>>> <[hidden email]> 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 <[hidden email]>: >>>> >>>> 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 >>>> >>>> >>>> |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |