Try to print putted object with new field from java code. Column in
QueryEntity is just link to binary object field. So you may be have
different names for binary field and column.
PS. I use ignite 2.6 and don't have problems with new fields/columns.
On 11/22/18 05:26, kcheng.mvp wrote:
> Thank y
Thank you very much!
how to handle this case in production?
it's too common to add new attribute to a new cache/pojo attribute.!!!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Actually you can't, because the schema stored in cache configuration is the
old one before adding column.
I've asked a similar question on dev list.
http://apache-ignite-developers.2346864.n4.nabble.com/Schema-in-CacheConfig-is-not-updated-after-DDL-commands-Add-drop-column-Create-drop-index-td38
Thank you reply very much!
May be I don't address the issue clearly.
here is my steps:
1: keep the server running
2: alter the schema via sql
3: I can query the new add column
4: add the corresponding attribute in pojo and with tag it with
@QuerySqlField.
5: call IgniteCache.put with new version
Hi,
If you want to change sql schema after start, you have to use ALTER TABLE
command: https://apacheignite-sql.readme.io/docs/alter-table
Best Regards,
Evgenii
вт, 20 нояб. 2018 г. в 06:37, kcheng.mvp :
> i noticed there is a comment from @slava.koptilin
>
> > I think the problem is to support
i noticed there is a comment from @slava.koptilin
> I think the problem is to support dynamic update of fields in QueryEntity.
I am afraid that there is no plan to support that. At least, I didn't find a
ticket in JIRA.
is there any plan to add this feature?
it's obviously with the system go
My case is very similar with this one
http://apache-ignite-users.70518.x6.nabble.com/SQL-cannot-find-data-of-new-class-definition-td22081.html
I add the new column(property) via sql as addressed in the
http://apache-ignite-users.70518.x6.nabble.com/SQL-cannot-find-data-of-new-class-definition-
