You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Edward Chen <ja...@gmail.com> on 2020/02/13 17:43:02 UTC
where to download odbc driver ?
Hello,
As per Ignite doc, ignite is shipped with ODBC windows pre-built
installers. I can not find any odbc msi file in
apache-ignite-2.7.6-bin.zip. Do you know how to get the odbc driver ?
https://apacheignite-sql.readme.io/docs/odbc-driver#building-odbc-driver
Thanks. Ed
Re: where to download odbc driver ?
Posted by Mikhail <mi...@gmail.com>.
Hi Ed,
Please read the doc:
https://www.gridgain.com/docs/latest/developers-guide/SQL/ODBC/odbc-driver#installing-odbc-driver
you can find binaries here: %IGNITE_HOME%\platforms\cpp\bin\odbc\
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
how to achieve this topology ?
Posted by Edward Chen <ja...@gmail.com>.
Hello,
I want to achieve this topology, do you know how to configure ?
The critical parts are, cache2 in JVM2 should not be replicated or
copied to JVM 1 . cache1 in JVM1 should not be replicated or copied to
JVM 2 . JVM3 and JVM 4 are each other failed-over backup.
Thanks. Ed
Re: how to achieve this topology ?
Posted by Evgenii Zhuravlev <e....@gmail.com>.
>Therefore, I think JVM1 and JVM2 should be client node with near caches
and also have node filter.
Not really, you can choose only one solution here - NodeFilter or client
nodes with Near cache. If you want to store data on nodes JVM1 and JVM2,
then you should go with NodeFilter approach. In this case they will be
server nodes and they will have all needed data locally.
In case of using Near cache, entry will be added to it only after reading
this entry from the remote cache first time. Also, this data will be
removed after node restart.
Evgenii
вт, 10 мар. 2020 г. в 06:20, Edward Chen <ja...@gmail.com>:
> Here is a background. In enterprise wide, each application, like JVM1,
> will create its own cache and this data is useful for another application,
> so this data should push to server node , like JVM3. but each client node,
> like JVM1, should have freedom to contain other caches based on some rules,
> but definitely not every cache in JVM3. in this case, looks like Node
> filter will work.
>
> Therefore, I think JVM1 and JVM2 should be client node with near caches
> and also have node filter.
>
> My understanding is correct ?
>
> Thanks Stephen Darlington for the near cache idea.
>
>
> On 3/9/2020 7:04 PM, Evgenii Zhuravlev wrote:
>
> Hi,
>
> You can use NodeFilter for caches. Please use this JavaDoc for
> information:
> https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html
>
> Example can be found here:
> https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java
>
> Evgenii
>
> пт, 6 мар. 2020 г. в 18:34, Edward Chen <ja...@gmail.com>:
>
>> Hello,
>>
>> I want to achieve this topology, do you know how to configure ?
>>
>> The critical parts are, cache2 in JVM2 should not be replicated or copied
>> to JVM 1 . cache1 in JVM1 should not be replicated or copied to JVM 2 .
>> JVM3 and JVM 4 are each other failed-over backup.
>>
>> Thanks. Ed
>>
>
Re: how to achieve this topology ?
Posted by Edward Chen <ja...@gmail.com>.
Here is a background. In enterprise wide, each application, like JVM1,
will create its own cache and this data is useful for another
application, so this data should push to server node , like JVM3. but
each client node, like JVM1, should have freedom to contain other caches
based on some rules, but definitely not every cache in JVM3. in this
case, looks like Node filter will work.
Therefore, I think JVM1 and JVM2 should be client node with near caches
and also have node filter.
My understanding is correct ?
Thanks Stephen Darlington for the near cache idea.
On 3/9/2020 7:04 PM, Evgenii Zhuravlev wrote:
> Hi,
>
> You can use NodeFilter for caches. Please use this JavaDoc for
> information:
> https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html
>
> Example can be found here:
> https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java
>
> Evgenii
>
> пт, 6 мар. 2020 г. в 18:34, Edward Chen <java148@gmail.com
> <ma...@gmail.com>>:
>
> Hello,
>
> I want to achieve this topology, do you know how to configure ?
>
> The critical parts are, cache2 in JVM2 should not be replicated or
> copied to JVM 1 . cache1 in JVM1 should not be replicated or
> copied to JVM 2 . JVM3 and JVM 4 are each other failed-over backup.
>
> Thanks. Ed
>
Re: how to achieve this topology ?
Posted by Stephen Darlington <st...@gridgain.com>.
Or JVM3 and JVM4 would be your Ignite cluster (server nodes) and JMV1 and JVM2 would be client nodes, possibly with near caches.
> On 9 Mar 2020, at 23:04, Evgenii Zhuravlev <e....@gmail.com> wrote:
>
> Hi,
>
> You can use NodeFilter for caches. Please use this JavaDoc for information: https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html <https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html>
>
> Example can be found here: https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java <https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java>
>
> Evgenii
>
> пт, 6 мар. 2020 г. в 18:34, Edward Chen <java148@gmail.com <ma...@gmail.com>>:
> Hello,
>
> I want to achieve this topology, do you know how to configure ?
>
> The critical parts are, cache2 in JVM2 should not be replicated or copied to JVM 1 . cache1 in JVM1 should not be replicated or copied to JVM 2 . JVM3 and JVM 4 are each other failed-over backup.
>
> <laiddfgkccigilen.png>
>
> Thanks. Ed
>
Re: how to achieve this topology ?
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Hi,
You can use NodeFilter for caches. Please use this JavaDoc for information:
https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html
Example can be found here:
https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java
Evgenii
пт, 6 мар. 2020 г. в 18:34, Edward Chen <ja...@gmail.com>:
> Hello,
>
> I want to achieve this topology, do you know how to configure ?
>
> The critical parts are, cache2 in JVM2 should not be replicated or copied
> to JVM 1 . cache1 in JVM1 should not be replicated or copied to JVM 2 .
> JVM3 and JVM 4 are each other failed-over backup.
>
> Thanks. Ed
>
how to achieve this topology ?
Posted by Edward Chen <ja...@gmail.com>.
Hello,
I want to achieve this topology, do you know how to configure ?
The critical parts are, cache2 in JVM2 should not be replicated or
copied to JVM 1 . cache1 in JVM1 should not be replicated or copied to
JVM 2 . JVM3 and JVM 4 are each other failed-over backup.
Thanks. Ed