He Rajesh,
Method CacheConfiguration.setIndexedTypes() should only be used for classes
with SQL annotations. Since you operate on binary objects, you should use
CacheConfiguration.setQueryEntity(), and define QueryEntity with all
necessary fields. Also there is a property QueryEntity.tableName whi
Thanks Stan for looking into it.
Unfortunately, it still takes 23 sec on 240gb RAM system, the corresponding
EXPLAIN PLAN
[[SELECT
ST.ENTRYID,
ST.ATTRNAME,
ST.ATTRVALUE,
ST.ATTRSTYPE
FROM "objectclass".IGNITE_OBJECTCLASS T
/* "objectclass".OBJECTCLASSNDEXED_ATTRVAL_IDX: ATTRVAL
Great. Many thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi all,
I am trying to build a prototype of some workflow application, where task
in a workflow is a spark application. For the same i am using Data and
Service grid. (Can't use Compute grid due to limitations from Customer)
What i am trying to do is, encapsulate spark execution inside an Ignite
Hi Raymond,
>I understand when I add an element to a cache that element is serialized,
>placed into the local memory for the cache on that server and then placed
>into the WAL pending checkpointing (merging into the persistence store).
First, the update will be written into WAL and only then in
Igniters, Valentin Kulichenko is hosting a free webinar today at 11 a.m..
Pacific time that will give you the tools and blueprint to build your very own
distributed database using Apache Ignite. This webinar will be recorded. You
can register to addend the event live or catch the recording from
Hi Igniters,
I will try to keep it short as much as I can. We have 8 caches total size is
around 6GB to 8GB in redis and the cluster is made up of 1200 nodes. All the
operations are read-only. It is a very low latency system where each request
doesn't need to be more than 2ms, in very rare cases 3
Hi Val,
Thanks for the response.
We will destroy the cache this time around. We will look to upgrade our
environments to 2.3 (currently on 2.1) so we can dynamically update the cache
configuration next time.
Thanks again!
-Original Message-
From: vkulichenko [mailto:valentin.kuliche..
What changes do I need to do to make ZeroDeploy work with QuerySqlFunction
definitions? I'm following the example and adding the class as follows, but
even with peer class loading enabled, I get a gnarly error. Can clients marshal
to servers? Any advice?
import org.apache.ignite.cache.query.a
Hi,
AFAIK, PeerClassLoading works only with Ignite compute subsystem.
For SQL functions you need to deploy them in cluster before use.
On Thu, Feb 15, 2018 at 4:29 AM, Williams, Michael <
michael.willi...@transamerica.com> wrote:
> What changes do I need to do to make ZeroDeploy work with Que
That's correct. Custom SQL functions must be explicitly deployed on all nodes
and can't be deployed dynamically.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Luqman,
I don't see why not. It will probably require pretty big cluster, but looks
like your Redis cluster is not very small either :) Ignite is a highly
scalable system, so you can test with smaller clusters of different sizes,
check what maximum throughput they provide and then extrapolate t
Thanks for the clarification Mike 😊
-Original Message-
From: Mikhail [mailto:michael.cherka...@gmail.com]
Sent: Thursday, February 15, 2018 5:15 AM
To: user@ignite.apache.org
Subject: Re: Write ahead log and early eviction of new elements
Hi Raymond,
>I understand when I add an element t
Hi luqmanahmed,
Could you please tell me why do need 1200 nodes to get 8 gb in memory?
Is it replicated cache? Do you need 1200 nodes to serve high number of
requests/sec?
If yes then does each node act as a primary for whole data? If yes, do you
use load balancer to reroute the requests?
Thanks,
Hi,
As per the doc ignite is a s strong or 100% consistent system.
e.g. I have partitioned cache, backup count is 1, and there are two nodes
in cluster.
If I update an entry in cache on one node and before updating the value in
backup cache(update to back is sync or async) the node crashes.
In t
15 matches
Mail list logo