Yes, the cache is already created before running my flink application.
The issue can be reproduced when you submit your flink application to your
flink cluster.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
The SQL queries are not getting me performance that I want. So I was trying
for alternative methods to handle the same using get.
Like getting the data using cache.get() and filtering them with the sql
operations that I actually wanted to do.
Suppose I have an equals method which will have two r
Hi,
When Ignite Sink Data Streamer start it checks if the cache name is already
present in the grid before the streaming process can begin.
Can you please confirm if cache got created before data sink process get
executed
Regards,
Saikat
On Mon, Jun 4, 2018 at 9:24 PM, Ray wrote:
> I think it
I have 3 doubts,
1. My model classes are externalizable. Still they can be queried using
SQLFieldsQuery at server node without any problem right?
2. Externalizable items cannot be queried from a client node in remote,
right? Is there a way to make it happen at client ?
3. Are there any other li
Sorry, the problem was that I had a wrong hash code implementation. Now when
I implemented it correctly, this works fine.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Thanks for the sample project. I will take a look.
Best Regards,
Roman
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for the response!
Session.removeattibute is not removing the attributes, its just setting the
value to null.
Sample project: https://github.com/daynok/ignite-webapp
I've seen this behavior in both java 9 and 10.
I will try java 8 and and see if that fixes things.
Thanks again!
--
I think it's a code bug in flink sink.
I had this same problem some time ago.
I think it's caused by compiler optimization of variable initialization in
multi thread environment(flink cluster mode).
In this case, the variable "cacheName" is not initialized when being used
because compile will optim
Hi Stephane,
Affinity collocation and affinity keys are crucial concepts/APIs to make
SQL JOINs work really fast. Similar concepts are adopted in other
distributed databases like Google Spanner, MemSQL, VoltDB, etc.
This page should shed more light on your question:
https://apacheignite-sql.readm
Ignite stores data in binary form and has its own algorithms for
hashCode/equals that are based on binary representation to avoid
deserialization. Therefore overriding equals would not have any affect.
Actually, I'm not sure I understand why you want to override it in the first
place. The followin
Hello!
Yes, you should be able to do that by specifying WITH "VALUE_TYPE=..."
Look it up on readme.io:
https://apacheignite-sql.readme.io/docs/create-table
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Can you share the full reproducer?
Thanks,
Evgenii
2018-06-04 15:10 GMT+03:00 the_palakkaran :
> Hi,
>
> I have both my Key and Model classes implementing Externalizable. I am able
> to put data into it correctly and also to do SQLFieldsQuery on it
> successfully. But when I use the same ca
Hi all,
it is an openjdk issue -> my fault
have a great day
Hello all,
I am trying to compile 2.5.0 from the source using jdk 1.8-172:
Using the command:
|mvn clean package -DskipTests
I get the following error while compiling the ignite-tools:
|
[ERROR]
/opt/ignite/apache-ignite-2.5.0-src/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/I
Hi!
Any chance you might have other putAll/removeAll that have the same
entries but in different order ? putAll not using some ordered set can
cause deadlocks, not sure if this can happen for removeAll also, what
kind of set are you using ?
Mikael
Den 2018-06-04 kl. 15:18, skrev akash shin
Hi,
My application hangs up when I execute following code. I tried to debug the
ignite source code but no luck. Complete thread dump is attached in this
mail.
*cache().removeAll(set)*
* Can someone please advise? *
*Thread dump is as follows.*
Name: local-task-pool-0
State: WAITING
Total blo
I figured out the solution for this.
Just implement Externalizable and you can override equals and hashcode
method.
//Key is unique for each cache entry. So, it is impossible to get entry by a
part of key.//
I understand that, I was checking for a way to do that.
Thanks a lot for the confirmat
Hi,
It's hard to get what's going wrong from your question.
Please attach full logs and thread dumps from all server nodes.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
You are free to use any hashcode and equals in your classes.
Ignite will convert your POJO to BinaryObject before save to cache and use
it's own hashing anyway.
It still unclear what are trying to do.
Key is unique for each cache entry. So, it is impossible to get entry by a
part of key.
You
Hi,
I have both my Key and Model classes implementing Externalizable. I am able
to put data into it correctly and also to do SQLFieldsQuery on it
successfully. But when I use the same cache object to get value by passing a
Key, it always returns null.
Why does this happen?
--
Sent from: http:/
Hi,
Yes, you can use BinaryStringArrayWriter / BinaryStringArrayReader.
No, to get BinaryStringArrayReader, you should use method
BinaryReader::ReadStringArray(const char* fieldName);
Best Regards,
Igor
On Sun, Jun 3, 2018 at 1:31 AM, F.D. wrote:
> Hi,
>
> I'm trying to develop a distributed
Hi Andrew,
I need to somehow override the equals and hashcode method in my key class.
ie;
I have a CustomerKey and CustomerModel configured in a customerCache. I need
to get results from the cache based on the key class that I am passing to
the cache for query.
like when I pass a key class to
Hi,
Would you please describe your scenario? Why you need to use binarylizable
or Externalizable?
Ignite allows overriding methods, but ignores object's hashcode and equals and
rely on its own implementation.
Ignite operates with BinaryObjects underneath and use BinaryObject hash
codes.
This allo
23 matches
Mail list logo