Hello Val,
you're right I was too quick to jump to a conclusion. Actually, the problem
comes from my code but it was not obvious to me.
I create the indexes with the following code:
---------------------------------
Collection<QueryIndex> idxs = new ArrayList<>();
QueryIndex idx1 = new QueryIndex();
LinkedHashMap<String, Boolean> idxFlds1 = new LinkedHashMap<>();
idxFlds1.put("lotTypeFk", true);
idxFlds1.put("validOn", true);
idxFlds1.put("ideCounterpartyRef", true);
idx1.setFields(idxFlds1);
idxs.add(idx1);
QueryIndex idx2 = new QueryIndex("rowId");
idxs.add(idx2);
qryEntity.setIndexes(idxs);
---------------------------------
Because I did not specify the type, I thought the index type was SORTED.
Actually, when nothing has been specified the type == null.
The thing is that null is considered to be FULLTEXT.
>From GridQueryProcessor.java
if (idx.getIndexType() == QueryIndexType.SORTED || idx.getIndexType() ==
QueryIndexType.GEOSPATIAL) {
....
} else {
assert idx.getIndexType() == QueryIndexType.FULLTEXT;
for (String field : idx.getFields().keySet()) {
String alias = aliases.get(field);
if (alias != null)
field = alias;
d.addFieldToTextIndex(field);
}
}
I solved that problem simply by setting the type explicitly
idx1.setIndexType(QueryIndexType.SORTED);
I will do a full load using this initialization code. If the problem
persists, I'll do a reproducer. The problem is that it might be a little bit
difficult.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/LoadCache-Performance-decreases-with-the-size-of-the-cache-tp9645p9765.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
