Hi Ilya,
Then I think this property should be ready in the production planning stage.
So the problem is, if there are many tables in the system and many
tables have combined primary keys, should this attribute be configured
with a relatively large value at the beginning, such as 40 and 50?
What's the negative impact? Instead of waiting for notifications from
the log.
在 2020/5/18 下午9:45, Ilya Kasnacheev 写道:
Hello!
I think this is correct. Moreover, setting this property on a part of
cluster may lead to problems of its own. It is recommended to set ot
before deploying a cluster.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:40, 18624049226 <18624049...@163.com
<mailto:18624049...@163.com>>:
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?
