Hello,
while investigating, I understood why I do have a lot of locks on Lucene
Documents in java mission control. That is because as soon as there is
String in the index, this is handled by Lucene even if you do not want full
text search (The string being a identifier).
--- From
Hi Oru,
If you need just key/value operations then simple get() will be much faster
than SQL queries. Because indexing, parsing and processing query consumes
resources.
But if you need quite often search for cache entities by their fields, using
of SQL + indexes is preferable, because no need to
Thanks for the reply.
I decided to use Strings with ASCII encoding.
Regards,
Oru
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/byte-as-a-key-in-Ignite-cache-tp9728p9736.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
That happens because key and value fields mapped to the same DB columns. You
should use at least one unique column for value mapping.
Ignite throws away all fields from value that intersect with key fields.
--
View this message in context:
Hi There!
I am currently writing my java program to access ignite cache primarily by
using IgniteCache's .get method.
Is it advisable to use indexed SQL based queries (for performance reason
only) ? or the search speed of both is the same?
Thanks
Oru
--
View this message in context:
Hi Val,
I have created a complex query and looks good in terms of query plan. But
query execution time is very high.
query -
SELECT
P.serialnumber,
iP.count,
cnt.itemnumber,
cnt.status,
cnt.enddate
FROM Product P
left JOIN ( SELECT serialnumber, COUNT(*) AS count
Amount of partitions depends on configured affinity function.
RendezvousAffinityFunction with 1024 partitions is default for
replicated or partitioned cache (for single node too). So for example
you can perform scan query by partitions in concurrent threads.
Another example of parallel processing
Hi Val,
Having two independently running clusters is fine with running ignite cache
in each cluster.
But I see cache is stopped because of network segmentation.
*Following the response to one of the query [1] -*
*Call chain:*
Hi,
Your question does not almost clear for me.
>> I realize that strings do take double the space as compared to bytes in
java.
It is not always correct. How about none latin characters?
If you are able to pack string, of course it is good idea for reduce
consume memory.
About byte[] as key,
