Taras Ledkov created IGNITE-13403:
-
Summary: Update JDBC metadata to match actual capabilities
Key: IGNITE-13403
URL: https://issues.apache.org/jira/browse/IGNITE-13403
Project: Ignite
Issue
Stephen Darlington created IGNITE-13404:
---
Summary: ignite.sh fails to set default JVM parameters
Key: IGNITE-13404
URL: https://issues.apache.org/jira/browse/IGNITE-13404
Project: Ignite
Ivan Smirnov created IGNITE-13405:
-
Summary: [Pyignite] Invalid cache configuration parameters
Key: IGNITE-13405
URL: https://issues.apache.org/jira/browse/IGNITE-13405
Project: Ignite
Issue
Hi Igniters,
It seems that it's not possible to implement effective leader-board with the
current Ignite indexes.
Leader-board stores a score and an id of a player of some game. Score is
indexed. One of the possible requests to that data structure is to get some
range of scores based on their rank
Hi Vladimir,
Usually, LSM-storage engines serve the range searches the best (Cassandra
is one of the examples). The SortedSet of Redis is one of the typical
components you can find in LSM-engines.
Presently, Ignite neither supports an LSM store nor a SortedSet data
structure. However, the range s
Hi Vladimir,
As far as I know, Redis' SortedSet is not shared. Is this correct? Is it
even possible to support similar functionality for a partitioned dataset?
-Val
On Fri, Sep 4, 2020 at 8:58 AM Denis Magda wrote:
> Hi Vladimir,
>
> Usually, LSM-storage engines serve the range searches the be
Folks, please disregard my previous email. I confused the range search task
when (the search boundaries are defined in a query) with the K largest
elements problem described by Vladimir.
Personally, I don't think there is a practical need for partitioned sorted
sets. Even if you store thousands of
