Hi Mike,
Thanks for the reply and explanation.
I have further curious question.
1. If use thick driver, can we use JDBC connection pooling?
2. How/What is the process to backup the data in Apache Ignite?
3. Let's say initially I start Apache Ignite with only one node (cache mode
= replicated,
Hi there,
I found a issue that if we set deploymentMode to Private and using
ScanQuery for in InitialQuery. The inital query will failed for *Class not
found* error. Meanwhile, the remoteFilter and LocalListener works fine.
After change ScanQuery to SQLQuery, everything works fine.
Is this a
Igniters,
I’m pleased to invite all of you to a series of webinars that will introduce
you to the fundamental capabilities of in-memory computing platforms such as
Apache Ignite.
That will be a mix of theory and practice. A lot of code examples are waiting
to be shown so that you can apply
Sumanta,
This can be specified via CacheKeyConfiguration:
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
guil, could you share your solution?
Many thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Alexey, thanks for reply.
I wondered does Ignite will set a incremental value for incoming data so can
help people to do stuff like you said?
You know for isolate data pushers are not easy to generate a unique
incremental value. I know many distribute data store,like elastisearch,mango
has those
Tom,
Thanks for promoting the workshop! Igniters, minor correction, that’s gonna be
the first 2.5 hours advanced workshop on Ignite internals and capabilities.
Join me at 6.30 PM today if you’re Silicon Valley.
By the end of the workshop the you will learn how:
• Configure and deploy Apache
Hello everyone,
Hibernate often generates this kind of nested from queries, if you have a
complex hierarchy of entities:
SELECT
mtoplevelt0_.definition_id AS definiti1_5_0_,
mtoplevelt0_.entity_id AS entity_i2_5_0_,
mtoplevelt0_.m_owner_id AS
No. There are things in the general application that are not yet initialized.
It is essentially a chicken-and-egg problem.
I need to start Ignite, and do various other things before I am ready to
take load.
But as soon as Ignite is started -- it starts to take ComputeJobs.
We really need a way to
Just in case, in the next Ignite version you’ll be able to create thin C++
clients by communicating to the cluster via a raw low-level socket based
protocol.
—
Denis
> On Nov 16, 2017, at 5:45 AM, kotamrajuyashasvi
> wrote:
>
> Hi
>
> My doubts got cleared
>
Hi Miau,
1. no, thin client won't reconnect to cluster, you need to handle an
exception and re-connect to other servers manually.
I create a ticket to improve this part:
https://issues.apache.org/jira/browse/IGNITE-6942
2. Thick driver uses ignite instance under the hood, so ignite client will
Hi,
Can you tell me how to specify a different attribute (other than key) can be
specified as affinity key? I cannot use the annotation in my entity class.
Is there a way to do it using CacheConfiguration and related class? Can I
just not set the attribute name as string which will be used as
@dkarachentsev:
My scenario: Ignite 2.2, 10 server nodes. The above bug said it's from GC
pause in client side, however I found it in the server node and No full GC in
that server node occured.I am afraid whether too many broadcast messages could
block data rebalance or not.
thank
I've create a ticket [1] for this issue.
[1] https://issues.apache.org/jira/browse/IGNITE-6941
-
Regards,
Andrew.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I've create a ticket [1] for this issue.
[1] https://issues.apache.org/jira/browse/IGNITE-6941
-
Regards,
Andrew.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Tejas,
Ignite will store indexes in off-heap, but indexes can't be swapped to a
disk.
However in the latest version of ignite, disk storage was implemented and
indexes can be saved on the disk, but it's unlikely because indexes are hot
data that should be kept in memory.
Thanks,
Mike.
--
Also you can annotate your Listener or Filter class by IgniteAsyncCallback
annotation. In this case a callback will be called from other thread.
On Thu, Nov 16, 2017 at 7:13 PM, ezhuravlev
wrote:
> gunman524, I didn't say anything like that.
>
> I said that if you want
gunman524, I didn't say anything like that.
I said that if you want to access cache from CQ, you need to start a new
thread
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi again,
This looks quite similar to your issue, and it was fixed in 2.3 [1]. Check
it out.
[1] https://issues.apache.org/jira/browse/IGNITE-6071
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Try to enable paired connections [1].
[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setUsePairedConnections(boolean)
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Could you please provide the full stack trace? the best if you can upload
the full log.
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, I am beginner with Apache Ignite and have few questions related to JDBC.
1. Let's say I have 2 node in 2 different machine (cache mode = replicated,
native persistence is turned on). I want to connect to the Apache Ignite
server using JDBC thin client. In the JDBC thin client URL, I only can
Yes, but can you please open another IGNITE ticket to be resolved hopefully
in 2.4?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
The solution that I shared earlier is recommended I think.
Regards,
Evgenii
2017-11-16 17:31 GMT+03:00 Guilherme Melo :
> Is there a recommended pattern for reconnecting continuous queries after a
> disconnect event?
>
> Thanks !
>
> Cheers,
>
> Guilherme Melo
>
Is there a recommended pattern for reconnecting continuous queries after a
disconnect event?
Thanks !
Cheers,
Guilherme Melo
www.gmelo.org
On 16 November 2017 at 20:25, ezhuravlev wrote:
> It's not recommended to access caches from listeners. It's a general
>
those logs was from the node (192.168.34.189), which accepted a ton of
incoming communication connection frequently.
Are there some errors occured in this node?
how to handle this?
thanks.
Hi
My doubts got cleared
Thanks.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Looks like you witnessed this issue:
https://issues.apache.org/jira/browse/IGNITE-6555
Which is already fixed and will be available in 2.4 release
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
Thanks for your response. Actually I'm working on a C++ project where
multiple C++ processes run in parallel. Each process should connect to
Ignite Server initially and start a transaction. Cassandra is used as
persistent store(The main reason to use ignite on top of Cassandra is for
the
Hi Caleb,
JDBC Thin Client doesn't supports authorization for now.
On Wed, Nov 15, 2017 at 6:54 PM, calebs wrote:
> Hi Valdimir,
>
> There are at least two problems that I've found here. The first is the
> query
> execution engine as you have just pointed out. The second
It's not recommended to access caches from listeners. It's a general practice
to create a new thread after you get an event.
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Ignite really caches metadata but restarting cluster clears the cache.
If you want to change field type at runtime (without restarting the
cluster), then you need to first remove field and then add the field
something like:
BinaryObject o = binary.builder("MyType").removeField("f").build();
Hi,
Initial query just gets the data according to the query. It will always
bring all data if you query all data. You need to manually control what
data you want your initial query to get. For example, if your key is
incremental (like numeric ID or timestamp) then you could save the last
Hi, guys
I meet a error when using SQL to query cache. It happens when Ignite server
restart after OOEM issue.
Could you help me figure out why this happens?
[2017-11-16T14:59:36,937][ERROR][client-connector-#45][JdbcRequestHandler]
Failed to execute SQL query [reqId=0,
Hi,
This is because Ignite C++ is not just thin client. It is actually a node,
that can be a server node and can join topology. You can actually
store data on it, run queries and compute jobs over it, and so on.
Does it answer your question?
Best Regards,
Igor
On Thu, Nov 16, 2017 at 10:08 AM,
Hi,
Ignite C++ indeed starts JVM process, but it is not just client,
it is basically ordinary Ignite node, that can be client or server
and can do in cluster almost anything, that Java Ignite node can,
although, C++ still does not have all the features that Java API
has. So, basically, C++ allows
Hi,
Looks like your listener is statefull and holds a connection object that is
transfered to remote node.
Try to move connection to out of listener.
On Thu, Nov 16, 2017 at 3:42 AM, gunman524 wrote:
> Hi guys,
>
> I met a issue that "Duplicate field ID" Error occurs when
Hi Sumanta,
Please have a look at https://issues.apache.org/jira/browse/IGNITE-6828
This error message comes from Spring framework
(org.springframework.data:spring-data-commons).
It is not Ignite message and does not affect Ignite logging, so you can just
ignore it.
To avoid such message you
39 matches
Mail list logo