Hi
Could you remove cacheCfg.setIndexedTypes(Long.class,ArrayList.class) and
only leave cacheCfg.setIndexedTypes(Long.class,YourPojo.class);
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-cache-range-query-using-cache-keys-tp10717p13042.html
Sent fro
Chris, then I need a bit more time to dive into this topic next week. Can
you share the source code of the ip finder?
Yakov, would you join the thread as well?
Denis
On Friday, May 19, 2017, Chris Berry wrote:
> Thank you for responding.
>
> I cannot see how either of these options will help m
Thank you for responding.
I cannot see how either of these options will help me.
I need to defer the IpFinder until my system is entirely alive and the
Consul Health Checks pass.
Similarly Ignite must be started on all of the Nodes, and they would all be
waiting on each other.
So the IpFinder wi
Hi,
Is there any reason why you can't register the nodes with Consul from the
code of the IP finder? This is what other cloud based IP finders (aws,
google compute engine, jdbc, etc) do in Ignite. The point here is that if
the ip finder returns non null list of adresses then the nodes should be
re
Hi,
I have a chicken-and-egg problem.
I am trying to create a ConsulIpFinder – which uses our Consul-based service
discovery under the covers.
(I asked about this without luck here:
http://apache-ignite-users.70518.x6.nabble.com/ConsulIpFinder-TcpDiscoveryIpFinder-issue-td12974.html
)
My problem
Thank you.
While timeout mechanism is fine it would be great if there is a way to
explicitly abort instantly if it is possible.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/C-Cancelling-Long-Query-tp12997p13037.html
Sent from the Apache Ignite Users mailing l
Hi Ivan,
Sorry , I am using my phone to type as emails are blocked in the
organization..
Example ~
IgniteCache cache = ignite.getorcreatecache("my cache")
Cache.put(key, value) ...
For the above, I am assuming there is no write thru cache implementation to
write to Hdfs ... One wud have to imple
Hi, Pranay,
to be honest, I'm not sure I 100% understand the question.
Yes, IGFS internally implemented by 2 caches (meta & data), but these 2
caches do not assume any direct modifications, that is, modifications done
otherwise than through IGFS API.
On Fri, May 19, 2017 at 7:12 PM, Pranay Tonpay
Thx Ivan.. appreciate your help...
Regarding point 3, I was specifically referring to the IgniteCache and not
Igfs. Sorry if my jargons are a bit incorrect in the context, but per my
understanding, ignite has ~
1) in memory data grid (ignite cache)
2) ignite file system
2 sits on top of 1 (rather
Basically, swap space is another storage layer. You have on-heap, off-heap
and then swap. So in case of on-heap mode only entry will be written in swap
when it's evicted from cache due to eviction policy. With off-heap enabled
it will be written to swap when it's evicted from there due to off-heap
Tableau report has "DISTINCT COUNT" field which doesn't work well with
ignite. After I removed it, live refresh is OK.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-issue-with-Tableau-live-ODBC-connection-tp12986p13032.html
Sent from the Apache Igni
Thanks a lot for your help. Now I get much clear.
Could you help me to understand what are the "client nodes". Do I need to
change configuration of the cluster, or I can simply set up "client nodes"
by changing codes within the spark application code? Currently, I am running
ignite with embedded m
Hi,
Could you please explain what you do?
Are you get some exception on start?
Usually enough download Ignite, extract it and run ignite.(but/sh).
If necessary modify default-config.xml.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/PCF-tile-for-Ignite-tp1246
Hi,
VisorCmd shows avarage value of some first cache rows, after multiplies over
all elements count. It does not got exact cache size, only estimate.
Furthermore in a latest Ignite version 2.0, work with memory radically
changed[1] and to make estimation by elements does not possible.
If you sow
Hi,
Can you provide a bit more info about your code and library you have used
to connect to ODBC?
We have not tested our driver with python so it seems very interesting, but
the only thing I can point you to right now is that our ODBC driver uses
UTF-8, not UTF-16 encoding. I'm not sure if encodi
1) Yes, unless some data have been evicted from Ignite cache.
2) Sure, this is expected: IGFS in dual modes always tries to reflect the
underlying file system contents.
3) This sounds strange. In DUAL_ASYNC mode it is possible that changes made
to IGFS appear in underlying file system with some d
Was it working prior to 2.0?
Guys, who's familiar with SQL engine, could you take a look?
Best Regards,
Igor
On Thu, May 18, 2017 at 10:04 PM, pingzing wrote:
> Data is very simple, POJO with a couple of QueryField of String/Double.
> Initial load to tableau is fine. Using Tableau extract also
Thanks for making feel like an ass this morning :). Please keep up the great
work on this fantastic project.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryFieldIdentityResolver-tp12896p13025.html
Sent from the Apache Ignite Users mailing list archive at
Hi,
While fetching string fields using ODBC driver from ignite cache in
python, I am getting following error,
Traceback (most recent call last):
File "pythonOdbc.py", line 13, in
row = cursor.fetchone()
UnicodeDecodeError: 'utf16' codec can't decode byte 0x00 in position 2:
truncated d
Hi ,
We have a 3 node ignite cluster and have configured cache in OFFHEAP_TIERED
memory mode with 2 back-ups.
All the caches are configured as PARTITIONED cache. There are ~90 caches
configured.
Once all the cache is loaded, we collect cache stats from Ignite Visor
console : 'cache -a'.
*CLARIFI
The issue you mention doesn't seem to be related to the issue we are having
as,
- The entire grid does not lock up as in the situation described in the bug
- There are no threads blocked or locked when our key lock occurs
- The bug seems to occur on Optimistic locking whereas our scenario occurs
on
21 matches
Mail list logo