Re: Issue IGNITE-3471

[dkarachentsev]

Hi,

Yes, for complex transaction this workaround will not work. So you need
either wait for fix or avoid using EntryProcessor for now.

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Effective Data through DataStream

[aealexsandrov]

Hi,

Could you please provide your code example, configuration and used Ignite
version?

Thank you,
Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Roadmap, especially TensorFlow integration

[Yury Babak]

Hi Dennis,

Yes, we will have this integration.

You clould check  this issue
   for more details.

We expect the first implementation of this integration after implementation
of  Python Thin Client  
.

Regards,
Yury



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Inconsistency reading cache from code and via REST?

[michael]

Hi Andrei

I simpler workaround for me for now is just to have keys a strings so REST

A few toString() tweaks to the sample code to put/get as strings instead of
integers shows this now works as expected both checking the cache in code
and from a browser.

thanks
Michael





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to start Ignite with a jar built from the source code

[aealexsandrov]

Hi,

In source code we have DEVNOTES.txt that contains the information how to
build ignite.

I believe that next steps could help you:

1)git clone https://git-wip-us.apache.org/repos/asf/ignite.git
2)Update your source code.
3)Build ignite as described from DEVNOTES.txt:

1.Compile and install:

mvn clean install -Pall-java,all-scala,licenses -DskipTests

2.Javadoc generation (optional):
  
mvn initialize -Pjavadoc

3. Assembly Apache Ignite fabric:

mvn initialize -Prelease

Look for apache-ignite-fabric--bin.zip in ./target/bin directory.

4)After that you can use generated jar files.

5)Run ignite command contains of next:

"%JAVA_HOME%\bin\java.exe" %JVM_OPTS% %QUIET% %JMX_MON%
-DIGNITE_HOME="%IGNITE_HOME%" -DIGNITE_PROG_NAME="%PROG_NAME%" -cp "%CP%"
%MAIN_CLASS% "%CONFIG%"


where:

%JAVA_HOME% - path to your java installation
%JVM_OPTS% - options for JVM where ignite will be started
%QUIET% - -DIGNITE_QUIET=true (or false)
%IGNITE_HOME% - path to your ignite location (path
apache-ignite-fabric--bin folder from unziped
apache-ignite-fabric--bin.zip)
%PROG_NAME% - program name
%CP% - classpath. By default it should be like next:

C:\Ignite\2.4\apache-ignite-fabric-2.4.0-bin\libs\*;C:\Ignite\2.4\apache-ignite-fabric-2.4.0-bin\libs\ignite-indexing\*;C:\Ignite\2.4\apache-ignite-fabric-2.4.0-bin\libs\ignite-spring\*;C:\Ignite\2.4\apache-ignite-fabric-2.4.0-bin\libs\licenses\*

%MAIN_CLASS% - org.apache.ignite.startup.cmdline.CommandLineStartup for
command line (maybe you will create your own)
%CONFIG% - path to config file  (default -  config\default-config.xml)

Provided options list isn't full but hope it will help you to build and
start ignite. 

Thank you,
Andrei

















--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

connection pool in ignite

[shawn.du]

Hi,Is there connection pool concept in ignite client?I notice there are only one TCP connection between my ignite client and server.Currently I don't find any issues with it, but please explain.If a client communicate(put/get/query) with server heavily, does one connection is enough?
Also I find this:https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.htmlwhat does setConnectionsPerNode do?







ThanksShawn

Re: Which ports does ignite cluster need to run normally?

[Olexandr K]

 what about UDP ports? what they are used for in Ignite?

On Thu, Apr 19, 2018 at 10:40 PM, vkulichenko  wrote:

> Most of these seem to ephemeral ports assigned to discovery and
> communication
> clients when they connect to well known configured ports on server side.
> That would always happen for any TCP connection.
>
> -Val
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

[Naveen]

HI Andrey 

The reason I was trying to explore this feature is, 

I will give you an example. I have a cache with 20M records and when I run
this query 
SELECT * FROM "AssociatedPartiesCache".ASSOCIATED_PARTIES

Query took more than 200 secs and ran out of memory, here is the error
thrown
This I have tried with lary=true, guess syntax and usage is correct. 
jdbc:ignite:thin://10.144.114.113?lazy=true

SQL Error [5]: javax.cache.CacheException: Failed to run map query
remotely.Failed to execute map query on the node:
ef5b4e7d-3423-4b84-8427-0491cd13f6c4, class
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query. Out of
memory.; SQL statement:
SELECT
__Z0.ASSOCIATED_PARTY_ID __C0_0,
__Z0.WALLETID __C0_1,
__Z0.UPDATEDDATETIME __C0_2,
__Z0.UPDATEDBY __C0_3,
__Z0.PARTY_ID __C0_4
FROM "AssociatedPartiesCache".ASSOCIATED_PARTIES __Z0 [90108-195]
  javax.cache.CacheException: Failed to run map query remotely.Failed to
execute map query on the node: ef5b4e7d-3423-4b84-8427-0491cd13f6c4, class
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query. Out of
memory.; SQL statement:
SELECT
__Z0.ASSOCIATED_PARTY_ID __C0_0,
__Z0.WALLETID __C0_1,
__Z0.UPDATEDDATETIME __C0_2,
__Z0.UPDATEDBY __C0_3,
__Z0.PARTY_ID __C0_4
FROM "AssociatedPartiesCache".ASSOCIATED_PARTIES __Z0 [90108-195]
  javax.cache.CacheException: Failed to run map query remotely.Failed to
execute map query on the node: ef5b4e7d-3423-4b84-8427-0491cd13f6c4, class
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query. Out of
memory.; SQL statement:
SELECT
__Z0.ASSOCIATED_PARTY_ID __C0_0,
__Z0.WALLETID __C0_1,
__Z0.UPDATEDDATETIME __C0_2,
__Z0.UPDATEDBY __C0_3,
__Z0.PARTY_ID __C0_4
FROM "AssociatedPartiesCache".ASSOCIATED_PARTIES __Z0 [90108-195]

In spite of, lazy=true, I got into this issue.

The way I was looking at possible solution to overcome this issue is. 

Long running queries should not impact server RAM, Ignite should run query
on Native persistent that is on DISK, the query which I am running should
not bring cluster down, I am still fine if the query takes couple of minutes
to execute, but ultimately should not disturb the cluster

After this error, cluster stopped working, we had to restart the cluster
again to make it work.
I believe there are definitely ways to overcome this issue, we do have
billion records in some of the tables, for some reason unknowingly runs
query on those tables, it should not bring down the cluster abtruptly

Thanks
Naveen



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Missing shu is a cross-cache associated query.

[hulitao198758]

My ignite configuration file looks something like this.






























uuid











































































uuid






































  



Then, after launching the ignite project with spring boot, I wrote
@repositoryconfig (cacheName = "SubscriptionOrderCache")
Public interface SubscriptionOrderRepository extends IgniteRepository <
SubscriptionOrder, Long > Save method, respectively in the two Cache to Save
a few same data, they all have UUID, is a primary key, and then select *
from "SubscriptionOrderCache" SubscriptionOrder shows three data, select *
from "SubscriptionCustomerCache" SUBSCRIPTIONCustomer also shows three data,
their RRCUSTOMERNUMBER the value of the field is the same, but the execution
SELECT * FROM "SubscriptionOrderCache".SUBSCRIPTIONOrder a WHERE r
RCUSTOMERNUMBER in(
The SELECT RRCUSTOMERNUMBER FROM "SubscriptionCustomerCache".
SUBSCRIPTIONCustomer
) the result of this statement is not correct. Where did I configure it?


JAVA POJO Like this：
 IgniteCache, SubscriptionOrder> cache
=ignite.cache("SubscriptionOrderCache");

String sql ="SELECT * FROM SUBSCRIPTIONOrder WHERE RRCUSTOMERNUMBER
in(" +
"SELECT RRCUSTOMERNUMBER FROM
\"SubscriptionCustomerCache\".SUBSCRIPTIONCustomer" +
")";
List> cursor = cache.query(new
SqlFieldsQuery(sql)).getAll();
System.out.println(cursor);








--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/