Hi Ilya,
Thank you very much for your reply!
I wonder if the existing primary key index will not be rebuilt after
this property is configured? Will only affect newly created tables in
the future?
在 2020/5/18 下午9:25, Ilya Kasnacheev 写道:
Hello!
Yes, it will have global impact on all indexes on primary keys, and
all indexes created without INLINE SIZE clause.
Regards,
--
Ilya Kasnacheev
чт, 14 мая 2020 г. в 16:53, 38797715 <38797...@qq.com
<mailto:38797...@qq.com>>:
Hi,
I see this property.
If this property is configured, it has a global impact? What is
the influence range of this parameter?
在 2020/5/14 下午9:41, Stephen Darlington 写道:
Exactly as the warning says, with
the IGNITE_MAX_INDEX_PAYLOAD_SIZE property:
./ignite.sh -J-DIGNITE_MAX_INDEX_PAYLOAD_SIZE=33
Regards,
Stephen
On 14 May 2020, at 14:23, 38797715 <38797...@qq.com
<mailto:38797...@qq.com>> wrote:
Hi,
Today, I see the following information in the log:
[2020-05-14T16:42:04,346][WARN][query-#7759][IgniteH2Indexing]
Indexed columns of a row cannot be fully inlined into index what
may lead to slowdown due to additional data page reads, increase
index inline size if needed (set system property
IGNITE_MAX_INDEX_PAYLOAD_SIZE with recommended size (be aware it
will be used by default for all indexes without explicit inline
size)) [cacheName=NEW, tableName=NEW, idxName=_key_PK,
idxCols=(CO_NUM, CUST_ID), idxType=PRIMARY KEY, curSize=10,
recommendedInlineSize=33]
I know that the create index statement has an inline_ size
clause, but I want to ask, how to adjust theinline size of
primary key?
