Thank you for your quick response! I'm actually using Ignite as an embedded shared-memory fabric for a multi-instance HTTP service. The vast majority of the business logic for this app is done through puts, gets and per-partition scan queries, for which we heavily leverage the POJOs. Still, the SQL layer is super useful for our users to quickly create dashboards for tracking purposes. Our deployment is already heavily automated, and I was hoping to figure out a way of keeping the SQL schema in sync with the POJO schema in a similarly automated fashion. Is ALTER TABLE ADD COLUMN even supported in v2.1?
Thanks, Cody On Fri, Dec 29, 2017 at 2:34 PM, vkulichenko <valentin.kuliche...@gmail.com> wrote: > Cody, > > If you want to dynamically change object schema, then you should avoid > deploying classes on server nodes. Ignite binary format [1] will make sure > that the change happens transparently, so you don't even need to perform > rolling upgrade. > > However, this will not affect SQL schema, i.e. will not make a new field > queryable or indexed. To achieve that you can use ALTER TABLE command [2]. > Actually, if you have a SQL use case, I would recommend to create schema > via > DDL in the first place, and not use POJOs at all. That can significantly > simplify the usage. > > [1] https://apacheignite.readme.io/docs/binary-marshaller > [2] https://apacheignite-sql.readme.io/docs/ddl > > -Val > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
