Who can give me some advice?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Who can give me some advice?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I also encountered this problem before when I am doing performance testing.
The reason why I get the exception is the CPU of the client is used 100%, so
the connection was closed occasionally.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
It is a Map storaging a snapshot of ignite cache data.You can see it defined in
my code.
private Map cacheMap = new ConcurrentHashMap<>();
public void continueQueryCache() {
try {
IgniteCache clientCache = makeIgniteCache();
if (clientCache != null) {
ContinuousQuery query = new
Can we have update on this?
-- Forwarded message -
From: Prasad Bhalerao
Date: Wed, Sep 5, 2018, 11:34 AM
Subject: Re: Query execution too long even after providing index
To:
Hi Andrey,
Can you please help me with this? I
Thanks,
Prasad
On Tue, Sep 4, 2018 at 2:08 PM Prasad
The second question:
I run the ignite nodes in the docker container with the following command:
sudo -u docker docker run -v /mnt/logs/apps/ignite:/mnt/logs/apps/ignite -v
/opt/ignite/ext-libs:/opt/ignite/ext-libs -v
/opt/ignite/config:/opt/ignite/config -v
Hi all -
We use Ignite in our production environment, But I found that the system
cache was increased slowly and never reclaim. when the free system memory
less than 200M, the node seemed did not work anymore and our system cannot
get any response from the server nodes. The image below is our
Hi,
Yes, you can connect to a remote(local running in some 475XX port or
another host in network ) ignite node using IgniteClient. Please take a
look into some examples available here
I have solved it.
Thanks..
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Ilya,
It did compiled...but it is not inserting records to ignite at all...
I waited for 20 mins for it to insert and terminated and there are no
exceptions in the ignite log.
Could you please suggest the right syntax to enable the streaming using jdbc
thin driver..and my key concern is
Hello!
It seems to me that MSSQL driver lacks any explicit support for
java.time.Instant so that's on MSSQL end. You could use blob cache store
instead.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 18:48, michal23849 :
> Hi,
>
> I have a Class with Instant data type:
>
> private
Hi,
I have a Class with Instant data type:
private Instant indexCreated;
Then I map it to VARCHAR in PojoStore:
Although I specify lower case public in the odbc definition in Windows 10,
the QLIK BI application, on its ODBC connection page, forces an upper case
"PUBLIC" as you can see in the screen shot, and as far as I can tell there
are no options to change that.
QlikOdbcPanel.png
Hi,
Here is my ODBC specification.
The schema is specified as Public and this looks (identical?) like the
example in the documentation:
On Thu, Sep 6, 2018 at 11:06 AM Вячеслав Коптилин
wrote:
> Hi,
>
> > I have tried various things on the Java side to make the Public schema
> explicit, such
Hello!
Please try using public (lower case) as schema, since quotes force case
sensitivity.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 18:25, David Robinson :
> I have no control over the format of the query coming through the ODBC
> driver.
>
> That is done automatically as far as I
I have no control over the format of the query coming through the ODBC
driver.
That is done automatically as far as I know by the[QLIK BI tool that is
leveraging the ODBC driver
to try to read data.
Are you suggesting it is QLIK adding the extra quotes that is causing the
problem with the H2
Hello!
Unfortunately, fulltext doesn't seem to have much traction, so I recommend
doing investigations on your side, possibly creating JIRA issues in the
process.
Regards,
--
Ilya Kasnacheev
пн, 3 сент. 2018 г. в 22:34, Courtney Robinson :
> Hi,
>
> We've got Ignite in production and decided
Hello!
SELECT COUNT(*) FROM ""PUBLIC"".CITY <-- I don't think you need any quotes
around PUBLIC.
Regards,
Ilya.
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 16:59, limabean :
> Scenario:
> 64-bit ODBC driver cannot read data created from the Java Thin driver.
>
> Ignite 2.6.
> Running a single
Hi,
> I have tried various things on the Java side to make the Public schema
explicit, such as this:
If I'm not mistaken the schema can be specified as a parameter of ODBC
connection string.
Please take a look at this page:
Scenario:
64-bit ODBC driver cannot read data created from the Java Thin driver.
Ignite 2.6.
Running a single node server on Centos to test this.
First:
Using Intellij to remotely run the sample code from the Ignite Getting
started page here on SQL:
First Ignite SQL Application
It is my understanding that for Ignite transactions to be ACID, we need to
have the caches configured as FULL_SYNC. [ Some of the code seems to
imply only at least one of the caches in the transaction needs to be
FULL_SYNC, but that is outside the scope of my question. ]
The initial load of
What are the differences between linux and ec2 machines? What disks are used
on ec2 instances?
Could you also get logs for crashed nodes for analysis, because crash might
be caused by differents reasons.
Regards
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
Can you clarify what is "local cache" in your use-case? What are you using
as a client for Ignite?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Do you have any kind of reproducer? I have tried to add Instant to Cache
Store tests but didn't see any problems outright.
Regards,
--
Ilya Kasnacheev
пн, 3 сент. 2018 г. в 10:54, michal23849 :
> Hi,
>
> I have a Instant data types in my Ignite data model and I want to map it to
> SQL
Hello!
You can use Thin Client, REST or SQL.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 15:00, monstereo :
> Is there any way to get only cache datas from ignite node(without creating
> new one)
> I can get via ClientCache cache =
> igniteClient.getOrCreateCache("sampleCache");
>
Hello!
Yes!
However, if you use simple name mapper, this restriction is lifted:
Regards,
--
Ilya Kasnacheev
ср, 5 сент. 2018 г. в 21:26, max8795 :
> Hello,
>
> I ran into an issue
Hello!
First of all, you can implement javax.cache.integration.CacheLoader only.
And there you can use stored procedures or specific SQL.
Ignite includes two JDBC cache stores but you are not limited to those.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 9:28, aa...@tophold.com :
> Hi
Is there any way to get only cache datas from ignite node(without creating
new one)
I can get via ClientCache cache =
igniteClient.getOrCreateCache("sampleCache");
However, I could not iterate over it.
I mean, I want to:
Iterator> iter =
igniteCache.iterator();
Hello!
Looks like some network problems, such as forced network timeout in case of
inactivity.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 5:14, Jeff Jiao :
> Hi guys,
>
> we are using Ignite 2.3.0
> we have a Ignite cluster in production which has 4 server nodes, recently
> we
> found
Hello!
I'm not sure but it doesn't look right to me. Does it compile?
Note that you also need to SET STREAMING OFF after data load is complete.
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 14:42, Sriveena Mattaparthi <
sriveena.mattapar...@ekaplus.com>:
> Thanks Ilya. Will try using together.
Hello!
You can only access Apache Ignite instances launched in the same JVM with
Ignition.ignite(). Come to think of it, how would you gain an Ignite object
that is in a different process?
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 10:44, monstereo :
> Think of it, i will work on
Thanks Ilya. Will try using together.
Please correct if the below statement work.
getConnection().createStatement().execute("SET STREAMING ON");
Regards,
Sriveena
From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
Sent: Thursday, September 06, 2018 3:28 PM
To: user@ignite.apache.org
Hello!
I don't see why not. Have you tried? Any difference in run time?
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 6:20, Sriveena Mattaparthi <
sriveena.mattapar...@ekaplus.com>:
> Hi Ilya,
>
>
>
> Can we cobimbe both of them together I mean
>
> 1. SET STREAMING ON;
>
> 2. JDBC
Think of it, i will work on production.
Here is the igniteConfig.xml
// others default configuration.
I have started this node on terminal: here is the log
2018-09-06 10:39:22 INFO IgniteKernal%as:95 -
>>> +--+
>>>
Hi,
We are using ignite for heavy datajoins operations with persistence enabled set
true. It was performing well on linux machines.
But once deployed to EC2( production environment), any data joins performed is
crashing the client application.
EC2 used is 32GB RAM and 24GB is assigned to
Hi Igniter,
If there any exist component implement read through only cache store.
And the read through SQL from a store proc or a specific customized SQL, as it
may join different tables.
Thanks for your time!
Regards
Aaron
I thought that I could connect specific ignite node via setting
userAttributes in the xml configuration.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
thank you for your response
you comments helped me alot
But there is point about IgniteStorm, one way or another I can run the code
via ide.(using ignite-storm). However when I convert to there was error like
you said backward compability. That's why I gave up to do with ignite-storm,
just do it
38 matches
Mail list logo
