Hi,
Yes, looks like the KafkaStreamer doesn't support the DELETE behavior. It
was created to loading data to Ignite.
However, deleting data from Ignite is possible using Interface
IgniteDataStreamer API:
Hello,
That's a generic statement. Ignite uses the flags to enable Unsafe API
support for its off-heap memory. So, it's safe to pass the flags for Ignite
nodes processes. This will be optional once Unsafe is replaced with an
alternate solution, presently there is no easy one. Once we come up with
Hello
So it's not possible to index a money type ? Using double or float for
money is strongly unrecommended
Thx
Patrick Brunmayr
Software Architekt
PBS Logitek Dienstleistungen GmbH
Vogelweiderstrasse 37
A-4600 Wels
T: +43 59 614 2367
F: +43 59 614 92367
mail:
Hello,
Thanks for response. I don't think it is necessary to have country_id as key
in City. Because in the official documentation of ignite here
https://ignite.apache.org/features/collocatedprocessing.html (See SQL
schema) they haven't used 'Code CHAR(3)' as key in City table.
By the way, if
hi
can we use a SQL query to export data from an Ignite table into a CSV file?
thanks
Mahesh
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
is it possible to access a file on IGFS via http interface on the cluster?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Using fixed decimal point long should be just fine, though.
Regards,
--
Ilya Kasnacheev
вт, 19 мар. 2019 г. в 11:18, Patrick Brunmayr :
> Hello
>
> So it's not possible to index a money type ? Using double or float for
> money is strongly unrecommended
>
> Thx
>
>
>
>
>
> Patrick
Jack,
You can use pointer semantics [1] to differ nulls from zeroes. It won't
work for primitive types (as int), but it is a rare case, really, that your
value is a primitive type. And even if you want to use value, that only
contains single int it is simple enough to make a class-wrapper.
Hello!
So this gives the following QueryEntity:
[QueryEntity
[keyType=com.jio.digitalapi.edif.customer.model.EntAssociatePositionKey,
valType=com.jio.digitalapi.edif.customer.model.EntAssociatePosition,
keyFieldName=null, valueFieldName=null,
fields=LinkedHashMap {associateId=java.lang.String,
i need to access the odbc driver and have had problems building on windows at
work. Thanks in advanced
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Here you go: [1]
If you need binary release:
1. Click [APACHE IGNITE NIGHTLY RELEASE] #2 :: Assemble Binaries
2. Choose any success release (latest at the top).
3. Click "Artifacts" tab.
4. Click on "apache-ignite-2.8.0.XXX-bin.zip" to download nightly binary
release.
You can also
On Tue 19 Mar, 2019, 5:26 PM luongbd.hust, wrote:
> test subscribe
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
test subscribe
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
The default seems to be 0 so you can try and use that. I guess it's good
default unless your transaction is really large.
Regards,
--
Ilya Kasnacheev
вт, 19 мар. 2019 г. в 00:24, Ariel Tubaltsev :
> Hi
>
> I wanted to start the TX transaction with a timeout value, however the
>
Hi,
I have three entities/POJOs ,say A, B and C which corresponds to tables A,
B, and C in persistence DB
public class A {
private int key;
private String name;
}
public class B {
private int key;
private String city;
}
public class C {
private int key;
Hi David,
As far as I know your understanding is correct in general.
Let's try to figure out what's happening in this particular case.
Could you please share execution plans of the query with both partitioned
and replicated templates.
And it also would be great if you share execution time for
Hello!
Yes, data is kept in off-heap. But if you do a large group by or order by
without using index, the intermediate results may overwhelm your heap.
I have no idea whether increasing heap to 6G will help or not. The
recommendation is to test every query on development cluster and never
But you changed the schema from the documentation. In the guide, CountryCode is
the primary key for the country table/cache. In your schema, you have
country_id in the Country table and country_code in City.
Two possible solutions:
1. Change the primary key of Country from country_id to
Yes.
You could use sqlline.sh:
0: jdbc:ignite:thin://127.0.0.1/> !set outputFormat csv
0: jdbc:ignite:thin://127.0.0.1/> !record a.csv
Saving all output to “/tmp/a.csv". Enter "record" with no arguments to stop it.
0: jdbc:ignite:thin://127.0.0.1/> select * from ignite;
select * from ignite;
Hi Ilya,
Please find below config of cache with composite key:
associateId
jobFunction
I tried running Ignite with given flags.
/docker run -d -p 49112:49112 --rm -e
CONFIG_URI="https://raw.githubusercontent.com/apache/ignite/master/examples/config/example-cache.xml;
-e JVM_OPTS="-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=49112
Hi Vladimir,
thx for help.
*Setup:*
2x server - one ignite node per server = 2 nodes
city table size: 13_000 entries
person table size: 10_000_000 entries
*Execution times:*
city table *PARTITIONED *+ person table PARTITIONED
0: jdbc:ignite:thin://127.0.0.1/> SELECT count(*) FROM
That's because Ignite's ODBC driver does not support all possible
connection/statement attributes.
You can try enabling ODBC logging [1], then repeat your actions and
send resulted logs to us, so we can see what is the attribute SQL server
tries to set that Ignite does not support.
[1] -
You are welcome.
Best Regards,
Igor
On Tue, Mar 19, 2019 at 5:15 PM wt wrote:
> Thanks Igor
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Hello!
This is a new features and one which often misfires, see
https://apacheignite.readme.io/docs/critical-failures-handling
Other than what is described, increasing failureDetectionTimeout often
helps.
Regards,
--
Ilya Kasnacheev
вт, 19 мар. 2019 г. в 16:34, Philip Wu :
> Hi, recently we
Thanks Igor
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Is there a reason the following error is returned by the odbc driver
OLE DB provider "MSDASQL" for linked server "IGNITE" returned message
"Specified attribute is not supported."
I am trying to query the odbc driver from SQL server with 2.7. I can see the
table, the query returns empty columns
Hi, recently we upgraded Ignite from 2.5 to 2.7, got the following error.
Is this configurational, or known bug in 2.7?
2019-03-18 15:44:23,383 SEVERE [ (tcp-disco-msg-worker-#2%XXXGrid%)]
Critical system error detected. Will be handled accordingly to configured
handler
And how about DELETE?
On Fri, 15 Mar 2019 at 16:58, aealexsandrov wrote:
> Hi,
>
> You can use the Kafka streamer for these purposes:
>
> https://apacheignite-mix.readme.io/docs/kafka-streamer
>
> Also, take a look at this thread. It contains examples of how to work with
> JSON files:
>
>
>
Do you have an example of how that could be done. I am struggling to
figure out how to set this up.
On Mon, Mar 18, 2019 at 2:00 AM Ilya Kasnacheev
wrote:
> Hello!
>
> The best approach is to use .setIndexedTypes() instead of
> setQueryEntities(), and annotate complex types in question with
>
Hi,
I am testing my custom CacheStoreFactory. It worked fine previously on my
local dev machine. After I changed this class and run it, I got
`java.io.InvalidClassException: xxx.CacheStoreFactory; local class
incompatible: stream classdesc serialVersionUID = 7199421607011991053,
local class
Hello Igniters
The version of Ignite that we are using is 2.7.0. I'm adding the events
that I want to hear via the IgniteConfiguration using the
`setIncludeEventTypes`
Then using ignite.event().localListen(listenerPredicate, eventTypes);
EVT_CACHE_REBALANCE_STARTED,
EVT_CACHE_REBALANCE_STOPPED,
32 matches
Mail list logo
