On Fri, Jan 13, 2017 at 12:26 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote:
> Dima, > > >> But, as you have justly noted, we have to keep nodes joining the > >> cluster up-to-date about what schemas and tables need to be created in > >> order for those nodes to participate in distributed queries. And, > >> correct me if I'm wrong, but this is relevant even outside of context > >> of 2.0 and page memory and persistent stores, amirite? > >> > > > > This should already be supported in Ignite. Otherwise, how are we able to > > run queries today? > > > > Currently SQL structures identity is maintained between nodes via > configuration identity. Nodes participating in distributed queries > must be started w/identical configs, there's no mechanism to propagate > SQL related configuration between peer nodes. This works as long as > SQL structures are created currently just once, at node startup. > However, if we wish to create those structures dynamically, we have to > maintain some sort of that metadata delivery to new nodes. > How about dynamic caches? Isn't the metadata already maintained across all nodes every time a new cache is created? What am I missing here?
