Thanks *Pavel *for the reply
our application is multi company application ,so each company instance have
more than 100 tables.so that we are creating single cache for each company
instance containing lot entity classes as well as it thirdparty enable with
native persistence.
*You can
Hi siva, modifying QueryEntity configuration of existing cache is not
possible.
Also, having multiple model classes per cache is not recommended.
The recommended way is to create a new cache for every new model/entity,
and have one QueryEntity per cache.
Note that you can achieve all the same
Hello!
Can you throw together a reproducer project that demonstrates incorrect
behavior? We would look into it, raise ticket if needed.
Thanks?
--
Ilya Kasnacheev
вт, 10 сент. 2019 г. в 13:01, Pascoe Scholle :
> Thanks for the prompt response. I have looked the
>
Hi,
we have implemented .net core server with 3rd party and native persistence
enabled & .net core thick client to create caches and thinclient to perform
crud/sql operations to the grid from multiple applications
we are creating single cache for multiple models classes and working
fine.But
Hello!
You can use CREATE TABLE with TEMPLATE= option to take advantage of a
template from XML file while creating a cache.
Not sure if you can use starred* template by name.
Regards,
--
Ilya Kasnacheev
пн, 16 сент. 2019 г. в 15:56, Igor Sapego :
> Denis,
>
> No ideas here. I think, it is
thank you very much!
Thanks,
Ken Cheng
On Mon, Sep 23, 2019 at 8:29 PM Igor Belyakov
wrote:
> Hi,
>
> Increasing index inline size can improve performance in cases when you're
> using variable-size columns, as described here:
>
Hi,
According to the logs, I see a lot of "Possible too long JVM pause"
messages, seems like you have a problem with GC activity. You should check
GC logs and try to tune GC following this manual:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
Also, it's suggested to disable WAL
Hi,
Increasing index inline size can improve performance in cases when you're
using variable-size columns, as described here:
https://apacheignite-sql.readme.io/docs/create-index#section-index-inlining
Also modifying inline size will require entire index rebuild, which is
equals to index
Hi,
By default Ignite uses "ATOMIC" atomicity mode which doesn't support
transactions:
https://apacheignite.readme.io/docs/transactions#section-atomicity-mode
In case you want to use transactions in SQL you should set
"TRANSACTIONAL_SNAPSHOT" atomicity level, as described here:
Hi Igniters it is me again :)
We are having a wierd behivor on some of cluster nodes. Cluster uses native
persistance with MMAP disabled. Some clusters have too many wal files even
if they are already deleted, but for some reason they are stll persisted on
the disk. I do not have any logs on
We have had some issues with the native persistance, in fact I reported this
issue :) https://issues.apache.org/jira/browse/IGNITE-12127
We are hoping to have the upgrade before this week ends.
cheers
-
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from:
Hi,
To make work this query, you can add one where clause or join condition in
the query, for example: where c.id = city_id;. I don't really understand
why do you want to run a fully distributed cross join on these tables - it
doesn't make sense, moreover, it will lead to the a lot of data
please send an email to user-unsubscr...@ignite.apache.org
在 2019/9/23 下午1:47, Roberto Lavalle de Juan 写道:
Unscribe
Hi All,
I want to test transaction with Apache Ignite SQL table. For this I created
a small program. What the program does is
1. Start a ignite server node from the code itself.
2. Create a JDBC url to local ignite server
3. Get a JDBC connection, create the table
4. Get a JDBC connection, set
Hi,
Ignite 2.7.5 requires the spark of 2.3.X version.
You should start the separate Spark and Ignite cluster:
https://apacheignite.readme.io/docs/getting-started
https://spark.apache.org/docs/2.3.0/spark-standalone.html
After that you should provide all required Ignite libraries to you
Hi,
I have created the following JIRA for this issue.
IGNITE-12215
Thanks,
Rick
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Please find enclosed the memory crash with the following configuration along
with the data region metrics just before the crash. This should be easy to
reproduce. Simply keep injecting data into the cache at a high rate with a
small data region size.
Thanks,
Rick
17 matches
Mail list logo