Agree. The gradual approach is the way to go for us. — Denis
> On May 31, 2017, at 1:20 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > I think a fully functional ALTER TABLE command may be hard to implement, as > it includes changes of columns, types, constraints, etc... We should take a > gradual approach here and implement this command by phases. > > I would propose that in the first phase we simply add the capability to add > and remove columns to a table. This way, given that we already support > CREATE INDEX command, the new column can be immediately indexed within the > cluster and used for query execution. > > Does this sound like a plan? > > D. > > On Wed, May 31, 2017 at 11:52 AM, Denis Magda <dma...@apache.org> wrote: > >> Sergi, Vovan, Alexander P., >> >> It’s great that we added CREATE/DROP index commands support to Ignite. As >> the next step, I think we need to move forward and plan to add ALTER TABLE >> command to the list. >> >> The reason we should have this command is simple. If a user adds a new >> field to Person class (while the cluster is up and running) then there >> should be a way to access the field from SQL and index it later if needed. >> Presently, this is not supported. >> >> What will be our efforts to support this? >> >> — >> Denis
