It didn't work as expected, tried disable/enable WAL too, still I see the
same behavior.
On Mon, Jun 24, 2019 at 7:32 AM Павлухин Иван wrote:
> Hi Goutham,
>
> I did not get from your last message does it work now as expected? If
> not does it work without a trick with disable/enable WAL?
>
>
Hello everyone. We're thinking about using ignite.
We have a need to transform some data in a MySQL database. We have a table
like
Data Table:
id val0_cv_id val1_cv_id val2_cv_id
1 2 2 1
2 2 3 null
the cv_id columns are foreign keys to this
Hi,
How do you execute your SQL queries? Java API SqlFieldsQuery has a
setTimeout method. Also there is a QueryCursor.cancel method.
Also KILL query SQL command [1] is targeted for 2.8.
[1] https://issues.apache.org/jira/browse/IGNITE-11564
пт, 21 июн. 2019 г. в 18:41, Ph Tham :
>
> Hello All,
It worth noting that IGNITE-9420 seems to be relevant for clusters
with enabled persistence.
пт, 21 июн. 2019 г. в 12:57, Ilya Kasnacheev :
>
> Hello!
>
> 2.7.5 definitely did not include it and there is no set date for 2.8.
>
> Regards,
>
> пт, 21 июн. 2019 г., 6:50 Justin Ji :
>>
>> 2.7.5 may
Hi,
I would suggest you to move your business logic out of queryable fields.
Put [QuerySqlField] to plain _JoinDate and rewrite your sql to "where
_JoinDate = ..."
This should work as your *cache.Get() result* example.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I tried non-zero values many times and the result is the same.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Goutham,
I did not get from your last message does it work now as expected? If
not does it work without a trick with disable/enable WAL?
ср, 19 июн. 2019 г. в 19:18, goutham manchikatla :
>
> Hi Denis,
>
> I tried removing Default_Region name property from config, still I see the
> same
Hi Max,
Thanks for your response !
Due to our data policy, I will not able share complete server logs.
But, I have checked that logs, there is no exception thrown at the time of
the incident. Only ignite sql line client was able to throw exception, which
I have put in previous thread.
No such
I think the problem could be with communicationSpi config.
You specified connectTimeout as 0, which is interpreted as infinite timeout.
Try to change it to a non-zero value.
--
Sent from:
Hi,
Please share full logs from all server nodes. It has to be an exception with
a stacktrace related to the incident.
Do you have a scenario to reproduce this issue?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
It recovered, but recovery lasts ~2 hours and customer says that there is no
crash on their network, other systems work fine
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I think you’d do operations like that using SQL, i.e., you’d use the
SqlFieldsQuery.
Regards,
Stephen
> On 24 Jun 2019, at 11:45, dhiman_nikhil wrote:
>
> I see many DS not present in Ignite like zrevrangeByScore, sortedSet, etc.
> Is there a way I can get all D.S. provided by Redis in
I see many DS not present in Ignite like zrevrangeByScore, sortedSet, etc.
Is there a way I can get all D.S. provided by Redis in Ignite.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I am using partitioned caches in my ignite 2.6 cluster. Faced this issue,
that the ignite cache query (using jdbc ) was unable to retrieve even
'Select count(*) query results'. Though the '!tables command' did display
the names of my 3 caches. The ignite server was also running without any
Hi,
It's not a warning, it's just an INFO message about writing checkpoint to
the disk. The reason for this checkpoint was that there were "too many
dirty pages". Here is how Ignite persistence works:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood
15 matches
Mail list logo
