Re: POJO get from any ignite console? visor or rest?

Binti, You can try to use Web Console [1] "Queries screen" and execute SCAN on you cache. [1] https://ignite.apache.org/features/datavisualization.html On Fri, Sep 22, 2017 at 2:32 AM, bintisepaha wrote: > Hi, I see that ignire rest API does not yet have support for

Re: How to configure a QueryEntity for a BinaryObject

Thanks Evgenii,It does work! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[ANNOUNCE] Apache Ignite 2.2.0 Released

The Apache Ignite Community is pleased to announce the release of Apache Ignite 2.2.0. Apache Ignite [1] is the in-memory computing platform that is durable, strongly consistent and highly available with powerful SQL, key-value and processing APIs. You can view Apache Ignite as a collection of

Ignite Context failing with java.lang.NullPointerException: Ouch! Argument cannot be null: cfg

I am hitting the following exception when running Ignite with Spark on Yarn. Here is the snippet of the code. The same job runs fine in spark local mode (spark-master: local). Only failing when running on Yarn. val config = new IgniteConfiguration() val tcpDiscoverySpi = new TcpDiscoverySpi()

POJO get from any ignite console? visor or rest?

Hi, I see that ignire rest API does not yet have support for json/custom objects lookup by key. But is this something I can do via JMX or visor or a management console? I only would like to see how the object looks in the cache easily. The key is usually a composite key of 2 integers. Let me

Re: Ignite Context : java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentContainersIfNeeded

Thanks Denis for looking into the problem. Here are the dependencies from my build.sbt file lazy val Versions = new { val igniteVersion = "2.2.0" } libraryDependencies ++= Seq( "org.apache.ignite" % "ignite-core" % Versions.igniteVersion, "org.apache.ignite" % "ignite-spring" %

Re: Ignite Context : java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentContainersIfNeeded

Thanks Denis for looking into the problem. Here are the dependencies from my build.sbt file val Versions = new { val igniteVersion = "2.2.0" } libraryDependencies ++= Seq( "org.apache.ignite" % "ignite-core" % Versions.igniteVersion, "org.apache.ignite" % "ignite-spring" %

Re: TcpDiscoveryS3IpFinder AmazonS3Exception: Slow Down

The only possibly different thing we are doing is using a VPC endpoint to allow the nodes to access S3 directly, without having to supply credentials.

TcpDiscoveryS3IpFinder AmazonS3Exception: Slow Down

Is TcpDiscoveryS3IpFinder expected to work? I randomly get exceptions which seem to be considered part of normal S3 operation, but are not handled/retried. com.amazonaws.services.s3.model.AmazonS3Exception: Slow Down (Service: Amazon S3; Status Code: 503; Error Code: 503 Slow Down; Request

Using ignite with spark

Hello - What is currently the best practice of deploying Ignite with Spark ? - Should the Ignite node sit on the same machine as the Spark executor ? According to this documentation Spark should be given 75% of machine

回复： Fetched result use too much time

Andrey Mashenkov Thank you very much! 1.query parallelism:this will cause a problem: fetch wrong reslut. I set it to 10,and have table a with 150,000 records, table b with 12,000,000 records. when I query single table,the result is correct. but when the sql is like

Re: Ignite Context : java.lang.NoSuchMethodError: org.apache.curator.framework.api.CreateBuilder.creatingParentContainersIfNeeded

Hi! Apparently you have some problem with classpath. Looks like version of Apache Curator used in runtime differs from the one used during compilation. It will be easier to say what is wrong if you provide your pom.xml Denis чт, 21 сент. 2017 г. в 8:57, pradeepchanumolu :

Re: INSERT into SELECT from Ignite 1.9 or 2.0

To add to Andrey's example, here is how you would use IgniteAtomicSequence to make IDs unique across the whole distributed cluster: *public static class CustomSQLFunctions {* *@QuerySqlFunction* *public static long nextId(String seqName, long initVal) {* *return

Re: Compute Grid Request Tracing

Hi Chris! Take a look at the documentation of LoggerResource annotation: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/resources/LoggerResource.html You can annotate a field of ComputeTask, ComputeJob or some other classes and use the injected logger during execution. Does

Re: Fetched result use too much time

Lucky, 1. Looks like it make no sense to set query parallelism level higher number of available CPU on node. 2. Map query use index for field FASSIGCUID type of String and seems values are 16 chars length strings (32 bytes) By default, values with size < 10 bytes can be inlined in index, so

Re: Ignite/yardstick benchmarking from within Docker Image

You can change a docker entry point, so Ignite instance won't start by default. You can do something like this: *docker run --entrypoint=/bin/bash -it apacheignite/ignite* Denis -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client Mode and client to client communication

Hello John! Why don't you promote your clients to servers? In Ignite, it is possible that only your dedicated servers will contain caches data, while other servers will participate in cluster without storing data. You can set up custom Cluster Groups / server roles for that. For every cache you

Re: INSERT into SELECT from Ignite 1.9 or 2.0

Hi, As a workaround you can implement custom function [1] for unique number generation. 1.You need to create a class with static functions annotated with @QuerySqlFunction. E.g. for single node grid you can use some AtomicLong static field. public class MyFunctions { static AtomicLong

Re: INSERT into SELECT from Ignite 1.9 or 2.0

Hi, Here's an example how to implement this using sequences and SQL functions. Please note how I refer to node name here - most likely you'll have to tweak this thing. - Alex 2017-09-18 16:17 GMT+03:00 Alexander Paschenko : > Hello, > > Andrey, I believe you're

Ignite Server start failing with the exception with Ignite 2.1.0

I have a five node cluster and when I start the server, i get the following error randomly in some servers [2017-09-21 07:46:18,635][ERROR][exchange-worker-#34%null%][GridDhtPartitionsExchangeFuture] Failed to reinitialize local partitions (preloading will be stopped): GridDhtPartitionExchangeId

Re: exception in transaction, how to rollback all put?

Hi, you are doing wrong. cache = ignite.getOrCreateCache("txn test cache"); creates a new atomic cache, because you configure another cache as transactional cacheCfg.setName("cacheName"); 2017-09-21 8:44 GMT+07:00 bingili : > the test.print() before test.run() will