Hi Igniters
I think queries (SQL) is a killer feature of Ignite. But we still have the example CacheQueryExample where query features provided. What's about to introduce a new package e.g. called org.apache.ignite.examples.query and split org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples like CacheQueryExample CacheQueryJoinExample CacheQueryCrossCacheExample CacheQueryExplainExample etc From my standpoint it will be easier to maintain and extend in future. For ignite user it's more clear where to find the a query functional example. -- Sergey Kozlov |
I completely agree. We should make our SQL capabilities more prominent and
visible. Sergey, can you file a ticket for this outlining what changes need to take place? D. On Mon, Dec 7, 2015 at 6:45 AM, Sergey Kozlov <[hidden email]> wrote: > Hi Igniters > > I think queries (SQL) is a killer feature of Ignite. But we still have the > example CacheQueryExample where query features provided. What's about to > introduce a new package e.g. called org.apache.ignite.examples.query and > split org.apache.ignite.examples.datagrid.CacheQueryExample into separate > examples like > > CacheQueryExample > CacheQueryJoinExample > CacheQueryCrossCacheExample > CacheQueryExplainExample > etc > > From my standpoint it will be easier to maintain and extend in future. For > ignite user it's more clear where to find the a query functional example. > -- > Sergey Kozlov > |
I filed https://issues.apache.org/jira/browse/IGNITE-2097
On Tue, Dec 8, 2015 at 12:02 AM, Dmitriy Setrakyan <[hidden email]> wrote: > I completely agree. We should make our SQL capabilities more prominent and > visible. Sergey, can you file a ticket for this outlining what changes need > to take place? > > D. > > On Mon, Dec 7, 2015 at 6:45 AM, Sergey Kozlov <[hidden email]> > wrote: > > > Hi Igniters > > > > I think queries (SQL) is a killer feature of Ignite. But we still have > the > > example CacheQueryExample where query features provided. What's about to > > introduce a new package e.g. called org.apache.ignite.examples.query and > > split org.apache.ignite.examples.datagrid.CacheQueryExample into separate > > examples like > > > > CacheQueryExample > > CacheQueryJoinExample > > CacheQueryCrossCacheExample > > CacheQueryExplainExample > > etc > > > > From my standpoint it will be easier to maintain and extend in future. > For > > ignite user it's more clear where to find the a query functional example. > > -- > > Sergey Kozlov > > > -- Sergey Kozlov |
I think the same is valid for TXs -
https://issues.apache.org/jira/browse/IGNITE-2107 Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2015-12-08 9:07 GMT+03:00 Sergey Kozlov <[hidden email]>: > I filed https://issues.apache.org/jira/browse/IGNITE-2097 > > On Tue, Dec 8, 2015 at 12:02 AM, Dmitriy Setrakyan <[hidden email]> > wrote: > > > I completely agree. We should make our SQL capabilities more prominent > and > > visible. Sergey, can you file a ticket for this outlining what changes > need > > to take place? > > > > D. > > > > On Mon, Dec 7, 2015 at 6:45 AM, Sergey Kozlov <[hidden email]> > > wrote: > > > > > Hi Igniters > > > > > > I think queries (SQL) is a killer feature of Ignite. But we still have > > the > > > example CacheQueryExample where query features provided. What's about > to > > > introduce a new package e.g. called org.apache.ignite.examples.query > and > > > split org.apache.ignite.examples.datagrid.CacheQueryExample into > separate > > > examples like > > > > > > CacheQueryExample > > > CacheQueryJoinExample > > > CacheQueryCrossCacheExample > > > CacheQueryExplainExample > > > etc > > > > > > From my standpoint it will be easier to maintain and extend in future. > > For > > > ignite user it's more clear where to find the a query functional > example. > > > -- > > > Sergey Kozlov > > > > > > > > > -- > Sergey Kozlov > |
Free forum by Nabble | Edit this page |