First of all, it would be a good idea to collocate data in your caches, i.e.
make items be stored on the same nodes with corresponding products. Take a
look at the documentation:
https://apacheignite.readme.io/docs/affinity-collocation#collocate-data-with-data
Hi,
It isn't a good idea to update millions of items every time product details
are changed.
I guess the main purpose of this schema is to store product details close to
items.
I suggest you add an additional cache for product details and make it
replicated. It seems that products count is much
Prasad,
First, I'm not sure why you think write-though would be slower than using
JTA. I'm probably missing something, but I believe you should at least test
this before making decision.
In any case, if you use JTA, Ignite would automatically enlist any cache
operations into ongoing JTA
Hi Community members,
I am looking for how to design fanout related problem in Ignite
We have two cache - product and items.
Items has product name and details along with item details.
Every time when there is product related update, item cache should be
updated for all the items with
Hello, Luca.
Please, try to use *withKeepBinary()* method to use BinaryMarshaller while
query SQL rows from cache.
Please, write me if it doesn't help.
@Test
public void testIgniteCaches() {
Ignite ignite =
Hell, ray.
> Please advise is this behavior expected?
I think this behavior is expected.
Because it's more efficient to query specific affinity key value.
Anyway, I'm not an expert in SQL engine, so I send your question to the
dev-list.
Igniters,
I think this user question is related to the
As you already know, you cannot have the config file in the discovery
bucket, because discovery enumerates the contents of the discovery bucket.
But the credentials in the config bucket are not yet visible, so they
cannot be used. You can make the config bucket public, but not with the
key
Cool thanks for the confirmation
Just curious does the continuous query implementation handle the duplicates?
i.e. is the client code shielded from having to deal with duplicates?
vkulichenko wrote
> This makes sense, and actually that's exactly how initialQuery works. It's
> executed after
Hello,
> Can you please provide an example to configure jta with ignite?
You can check the following tests that illustrate the JTA configuration[1]
from Apache Ignite point of view.
Hi Val,
1M per day in memory sales data, 100 parallel financial aggregations in each
batch plus additional PUB/SUB requests for both instant query and server
push. It has been confirmed to play group count distinct is way too slow, so
we decided to play some of TOP N query in separate domain, for
I am trying to deploy an Apache Ignite cluster in our AWS VPC. I have done
the following:
• Created an S3 Bucket to store the ignite-config.xml file
o Uploaded the config file to the bucket.
Config file contents (just based on example in github):
Hi Alexey.
Thanks for the feedback. It will take me a little bit to set up the test
again. My original test had a bunch of machines in cluster mode, I guess
to test this I can just use one with a small data region instead.
On Wed, Mar 21, 2018 at 3:59 AM, Alexey Goncharuk <
Thanks Slava,
I'll have it in mind.
Best regards.
2018-03-26 15:17 GMT+02:00 Вячеслав Коптилин :
> Hello,
>
> If I am not mistaken, Apache Ignite is certified with
> spring-data:1.13.1.RELEASE version.
> I am not sure there is an activity related to the latest code
Hi Fvyaba,
I investigated your example. In your code you are going to create new cache
every time when you are going to create new table. Every new cache will have
some memory overhead. Next code can help you to get the average allocated
memory:
try (IgniteCache cache =
Hi,
Looks like it make sense for such simple query.
However, this optimization should be omitted for other aggregates: e.g. SUM
with DISTINCT and for AVG with DISTINCT.
I've created a ticket for this [1].
[1] https://issues.apache.org/jira/browse/IGNITE-8047
On Sat, Mar 24, 2018 at 7:35 PM,
Hello,
If I am not mistaken, Apache Ignite is certified with
spring-data:1.13.1.RELEASE version.
I am not sure there is an activity related to the latest code changes in
spring boot library.
Anyway, you can start a discussion on dev-list about that, and feel free to
contribute to the project!
Hi Fvyaba,
I investigated your example. In your code you are going to create new cache
every time when you are going to create new table. Every new cache will have
some memory overhead. Next code can help you to get the average allocated
memory:
try (IgniteCache cache =
Hello,
If I am not mistaken, Apache Ignite is certified with
spring-data:1.13.1.RELEASE version.
I am not sure there is an activity related to the latest code changes in
spring boot library.
Anyway, you can start a discussion on dev-list about that, and feel free to
contribute to the project!
Hello,
It looks like a bug. I've created the following JIRA ticket for that
https://issues.apache.org/jira/browse/IGNITE-8044
Best regards,
Slava.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Please provide all logs and thread dumps from all nodes.
Evgenii
2018-03-26 9:45 GMT+03:00 Priyanka Shinde :
> Hi Igniters,
>
> We have 1 server node and my application starts in client mode. We have
> created 3 caches in client application namely Queuecache,
Hi,
I checked the project from github. Using the proposed steps I wasn't able to
reproduce the issue.
It looks like the IDE somehow uses old class files. You can try to rebuild
module from IDE (after moving "CompanyCachestorefactory") or execute "mvn
clean install".
Best Regards,
Roman
--
Hi,
I checked the project from github. Using the proposed steps I wasn't able to
reproduce the issue.
It looks like the IDE somehow uses old class files. You can try to rebuild
module from IDE (after moving "CompanyCachestorefactory") or execute "mvn
clean install".
I am quite sure that the
Hi,
When declaring Spring Boot 2 in my POM.xml I get this error:
Error:(14, 8) java: name clash: deleteAll(java.lang.Iterable) in
org.springframework.data.repository.CrudRepository
and deleteAll(java.lang.Iterable) in
org.apache.ignite.springdata.repository.IgniteRepository
have the same erasure,
Hi,
There is a bug when you declare a function in a IgniteRepository without
parameters:
The IgniteQueryGenerator.getOptions function is not validating that the
parameter list can be null. The error is thrown when the application starts
up.
@Query("SELECT sum(vlSale) FROM SalFDetLin")
double
Hi Igniters,
We have 1 server node and my application starts in client mode. We have
created 3 caches in client application namely Queuecache, Queuegroupcache
and agentcache.
During Initialization we put all the values in cache by cache.put operation
and referred the values from the cache using
Hi
Can you show your solution? I am very upset about this.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
26 matches
Mail list logo