Ignite File System Support in R or Python

Is there a support for ignite file system running over hadoop file system in R or Python? Is there a support in scala? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-File-System-Support-in-R-or-Python-tp14088.html Sent from the Apache Ignite Users

Modelling Question

Hi, I have a general question about data model design. Currently we have java server nodes, and .net client nodes. We use services, messaging and the data grid. The current design is one single ignite cache, which contains all entity types. The key for entity types is an object, but it has

Read-through cache performance

Hi, I use the following code to find the maximum speed of a read-through cache. I use cacheCfg.setExpiryPolicyFactory(AccessedExpiryPolicy.factoryOf(Duration.ZERO)); and the load function just returns null: public static class NullCache extends CacheStoreAdapter { @Override

Performance WordCount to Hadoop

Hi, ìThanks to your suggestions i managed to configure good ignite. All Work but I found another issue... The computation is 20 or 30 times slower than the same computation without put word in cache. If i put just 1 word in cache at the beginning of map function the computation time it's the same.

Re: Scanquery and Peer classloading

Hi, could you please describe your case and elaborate a bit on your concern. Kind regards, Alex. On Fri, Jun 23, 2017 at 1:17 PM, Helge Waastad [via Apache Ignite Users] < ml+s70518n14061...@n6.nabble.com> wrote: > Hi, > Is it correct that scanquery will not work using Peer classloading? > > If

Configuring SQL queries - ClassNotFoundException: Unknown pair

Hello, I am trying to configure a cache with String key and a custom java class as value to be accessed using the ODBC driver. I tried configuring the SQL schema with both the annotation-based and the query entity approach, however I get a *java.lang.ClassNotFoundException: Unknown pair

Re: Transaction Boundary - Data Streamer

2017-06-26 15:27 GMT+03:00 fatality : > Hi > > We have also implemented a generic receiver as > TimestampBasedUpdateStreamReceiver and also > AbstractTransactionalStreamReceiver. I send you the source code if you > want > and maybe can be added to the ignite source code.

Re: Transaction Boundary - Data Streamer

Hi We have also implemented a generic receiver as TimestampBasedUpdateStreamReceiver and also AbstractTransactionalStreamReceiver. I send you the source code if you want and maybe can be added to the ignite source code. -- View this message in context:

Re: Hadoop and Ignite, Problem grid cache

Hi, Thank you for reply.Thanks to your suggestions i managed to configure good ignite. All Work but I found another issue... The computation is 20 or 30 times slower than the same computation without put word in cache, maybe 40. >From what can depend? This is the Server Code public static void

Re: Transaction Boundary - Data Streamer

2017-06-26 13:28 GMT+03:00 Yakov Zhdanov : > >>If you need transactional in your operations, you can use > optimistic transactions by implementing and registering a > receiver into your datastreamer as explained here > > >> https://apacheignite.readme.io/docs/transactions#

Re: Transaction Boundary - Data Streamer

>>If you need transactional in your operations, you can use optimistic transactions by implementing and registering a receiver into your datastreamer as explained here >> https://apacheignite.readme.io/docs/transactions#deadlock- free-transactions >> and for datastreamer here

Re: [TCP Discovery] connection ip configuration

Hi, You can specify localHost in IgniteConfiguration: https://ignite.apache.org/releases/2.0.0/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setLocalHost(java.lang.String). For example: Evgenii -- View this message in context:

[TCP Discovery] connection ip configuration

Hi, I would like to know how to specify the connection ip if the server has more than one ips during the TCP Discovery. Server A has 2 lan cards and so 2 ips (e.g. 1.2.3.4 and 7.8.9.0). I have applied the following configuration for the TCP discovery and the server is well connected. However,