Raymond,
When a checkpoint is triggered you need to have some amount of free page
slots in offheap to save metadata (for example free-lists metadata,
partition counter gaps, etc). The number of required pages depends on count
of caches, count of partitions, workload, and count of CPUs. In worst
ca
Hello,
For in-memory data reagions DataRegionConfiguration.getInitialSize() will
be allocated on node startup.
Additional memory will be allocated by chunks of some size on demand until
DataRegionConfiguration.getMaxSize() reached.
вт, 7 июл. 2020 г. в 16:17, 배혜원 :
> Hello!
>
> but I’m not use p
Hello,
Ignite thin client applies connection throttling if you have several
failed attempts to connect to some server (this server will be skipped for
some time to avoid waiting for connection timeouts on each attempt to
connect, the client will try to connect to the next servers if they are
confi
Hello.
Actually performance test results attached to IGNITE-11336 are not correct,
I forgot to delete these results from the ticket. The environment was not
tuned correctly and I get too often checkpoints for runs without WAL
compression and this leads to bad results for "compdisabled" runs. But I
Hello,
This feature was implemented for java and .Net thin clients in Ignite
version 2.9, but this version is not released yet.
пн, 21 сент. 2020 г. в 09:51, Mahesh Renduchintala <
mahesh.renduchint...@aline-consulting.com>:
> Hi,
>
> WIth a thin client handle, is it possible to launch tasks on
Hello,
TransactionConfiguration property has nothing to do with atomic caches.
Perhaps your threads were deadlocked due to atomic putAll/removeAll
operations with an unordered set of keys. It's a known issue and I hope
will be fixed soon. See [1] for detailed information. Until this ticked is
fixe
s. Is there any
> implementation available (or a reference) to sort user defined types of
> objects ?
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
> *From:* Alex Plehanov
> *Sent:* 20 October 2020 19:54
> *To:* user@ignite.apache.org
> *
Columns information is read by thin-client only after the first data
request, so you need to read at least one row to get columns.
вт, 3 нояб. 2020 г. в 09:31, Ilya Kazakov :
> Hello, Shravya! It is very interesting! I am trying to reproduce your
> case, and what I see. I can see column names in
est how to get the datatypes of those columns
> obtained from the query?
>
>
> Regards,
>
> Shravya Nethula,
>
> BigData Developer,
>
>
> Hyderabad.
>
>
> --
> *From:* Alex Plehanov
> *Sent:* Tuesday, November 3, 2020 12
Hello,
Thanks for the report, I will try to fix it shortly.
ср, 4 нояб. 2020 г. в 12:35, 18624049226 <18624049...@163.com>:
> Hi community,
>
> The operation steps are as follows:
>
> 1.use ignite.sh example-deploy.xml start a server node
>
> 2.Put the service jar package in the /home/test/depl
Hello,
This problem was only in Ignite 2.8 with enabled partition awareness. Fixed
in Ignite 2.8.1, see [1].
[1]: https://issues.apache.org/jira/browse/IGNITE-12743
вт, 17 нояб. 2020 г. в 01:53, Hemambara :
> Ignite thin client create and use ReliableChannel which starts below async
> thread, b
Hello,
Ignite compresses each page individually. The result of whole file
compression will always be better than the result of each individual page
compression. Moreover, Ignite stores compressed pages only if the page size
shrunk by one or more filesystem blocks. So, for example, if you have fs
b
ested with.
>
> Any other tips on how to reduce disk usage? Any point in using compression
> level more than 18 for ZSTD? Most of this data will only be written once so
> I am not so concerned about write speed.
>
>
> On Tue, Nov 17, 2020 at 9:34 AM Alex Plehanov
> wrote:
>
Hello, Naveen
In Ignite, when we talk about rotating data between disk and memory in the
data region with native persistence, we call it 'replacement', not
'eviction'.
Currently, there is only one replacement policy - Random-LRU. Perhaps,
there will be more policies soon, but without the ability t
Hello,
Unfortunately, for atomic caches in 2.9.1 there still java level deadlock
possible (Ignite system threads can hang) for mass operations (putAll,
removeAll, invokeAll) if an unordered key set is used. See [1]. This issue
will be fixed in 2.10 release.
[1]: https://issues.apache.org/jira/bro
Hello,
Try this: "select _val from mytesttable"
чт, 21 янв. 2021 г. в 17:38, siva :
> Hi,
> I am using .net Ignite v2.9.1 and
>
> Since SqlQuery deprecated in documentation suggesting please use
> SqlFieldsQuery.
>
> what is the way to get result as Type using sqlfieldsquery?
>
> for example que
Hello,
Can you please share your stacktrace? In 2.7.6 I think this bug
affects only cache configuration retrieval and binary metadata retrieval.
To avoid problems with binary metadata retrieval you should not use types
which typeId (IgniteClient.binary().typeId()) starts with byte 103 as cache
key
Hello,
There are no public methods to calculate CacheConfiguration size.
As Pavel already said all versions of the client compatible with all
versions of the server, the features set will be determined by the highest
common version.
Here is the feature compatibility list for the java thin client
Ilya, you can find reproducer in test
IgniteBinaryTest.testBinaryTypeWithIdOfMarshallerHeader
In this thread, we are talking about a workaround for older versions where
this issue is not fixed.
пт, 29 янв. 2021 г. в 11:49, Ilya Kasnacheev :
> Hello!
>
> Do you have reproducer for that entity name
Hello,
You can use as query filter only classes that already deployed to the
server. In your case, class ConnectAndExecuteTestDataInJava only exists on
the client-side and the server knows nothing about it. Unlike Ignite nodes,
Ignite thin clients don't have a P2P class deployment feature.
пн, 1
Hello,
To make it work you should put classes with filters you want to use
somewhere to the server's classpath.
вт, 2 мар. 2021 г. в 12:38, ChandanS :
> Thank you Alex Plehanov for the quick response. Could you please provide
> some
> details to make it work.
>
>
>
Hello,
There is no way to configure a custom failure handler for segmentation
error, you can only choose from 3 available variants bounded to
segmentation policy (Use IgniteConfiguration.setSegmentationPolicy to
change policy)
чт, 22 апр. 2021 г. в 17:10, ashishg :
> Hi,
>
> I have set the custo
Hello,
Probably related to [1] (Fixed in Ignite 2.9)
[1]: https://issues.apache.org/jira/browse/IGNITE-13192
пн, 24 мая 2021 г. в 18:55, Naveen :
> When I tried to retrieve the fields of the binary object it does throw
> exception, after deleting all such records, it started working fine. We do
Hello,
You can create your own cache templates with the affinity function you
require (currently you use a predefined "partitioned" template, which only
sets cache mode to "PARTITIONED"). See [1] for more information about cache
templates.
> Is this the right approach
> How do we handle existing
Hello,
Most probably it's related to [1], which is fixed since Ignite 2.9.1.
[1]: https://issues.apache.org/jira/browse/IGNITE-13401
чт, 19 авг. 2021 г. в 09:53, Naveen Kumar :
> Hi All
>
> We are using Ignite 2.8.1 and using the thin clients majorly.
> Facing a strange issues for last couple o
Hello,
Perhaps you have too small WAL segment size (WAL segment should be large
enough to fit the whole cache entry), try to
change DataStorageConfiguration.WalSegmentSize property.
чт, 14 окт. 2021 г. в 00:43, Semeria, Vincent :
> Hello Ignite,
>
>
>
> I currently use the C# API of Ignite 2.10
Log) segment.
> For performance reasons,
>
> // the whole WAL is split into files of fixed length called
> segments.
>
>
>
> The limit should also be written in this page
>
> Ignite Persistence | Ignite Documentation (apache.org)
> <https://ignite.apa
Hello,
How was the entry inserted to the cache? You are trying to get this entry
via thin client, if the entry was inserted via thick-client (Ignite node)
you can face such a problem. Ignite thin-client and Ignite nodes have
different default "Compact footer" property values, so POJO keys are
mars
Hello,
Thin client doesn't have a peer class loader (and most probably will never
have). To use predicates you should deploy classes for these predicates to
Ignite nodes. Serializable interface for Person class will not help here.
пн, 18 окт. 2021 г. в 20:14, Prasad Kommoju :
> Thanks for the ti
-
>
> Regards,
>
> Prasad Kommoju
>
>
>
> *From:* Alex Plehanov
> *Sent:* Monday, October 18, 2021 1:35 PM
> *To:* user@ignite.apache.org
> *Subject:* Re: Problem with ScanQuery with filter on ClinetCache
>
>
>
> Hello,
>
>
Hello!
Most probably it's related to ticket [1] that is fixed in 2.9 release.
[1]: https://issues.apache.org/jira/browse/IGNITE-13192
пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar :
> Hi All
>
> We are using 2.8.1
> At times, we do get this BinaryObjectException while calling GETs thru
> thin clie
ved if we do a node restart
>
> And, any work-around we have to fix this issue with current version
> ignite 2.8.1
>
> Thanks
>
> On Mon, Nov 22, 2021 at 12:20 PM Alex Plehanov
> wrote:
>
>> Hello!
>>
>> Most probably it's related to ticket [1] th
Hello,
Unfortunately, update to the newest H2 version is not possible, since H2
removed the Ignite support [1].
Currently, the new SQL engine for Ignite is under development. The first
beta release of this engine is planned to Apache Ignite 2.13 version [2].
But it still requires the ignite-indexi
John Smith,
Can you please show DDL for the car_code table? Does PK of this table
include provider_id or car_code columns?
I found a compatibility issue, with the same behaviour, it happens when
storage created with Ignite version before 2.11 is used with the newer
Ignite version. Have you upgrade
Hello,
Data pages have the same priority as index pages. Algorithm can be
configured by DataRegionConfiguration.PageReplacementMode property.
See
https://ignite.apache.org/docs/latest/memory-configuration/replacement-policies
for more information.
ср, 31 авг. 2022 г. в 04:18, 38797715 <38797...@q
16),
> primary key (provider_id, car_id)
> ) with "template=replicatedTpl, key_type=CarCodeKey, value_type=CarCode";
>
> On Wed, Aug 31, 2022 at 7:25 AM Alex Plehanov
> wrote:
>
>> John Smith,
>>
>> Can you please show DDL for the car_code table? Does PK of thi
x27;t somehow
> throw that error again? And if I upgrade to 2.13 from 2.12 will I have the
> same issue?
>
> On Wed, Aug 31, 2022 at 3:31 PM Alex Plehanov
> wrote:
>
>> John Smith,
>>
>> Thank you. This issue will be fixed in upcoming 2.14.
>>
>> ср, 3
Hello,
When "partition awareness" is enabled, the client tries to connect to all
server nodes from the connection string. If "partition awareness" is
disabled, only one connection is maintained. Since Ignite 2.11 "partition
awareness" is enabled by default. See [1] for more information.
[1]:
http
Hello,
There are no certain plans about beta status removal. I think it will be in
beta status at least one release more (at least until 2.16)
ср, 28 сент. 2022 г. в 16:30, Mike Wiesenberg :
> Hi,
> When(and in what version) is Calcite SQL engine integration scheduled to
> be out of experimenta
Hello, there is no such function DATEDIFF in the Calcite based SQL engine
in Apache Ignite currently, and it can't be enabled by any property.
But you can use alternatives like:
(date1 - date2) MINUTES > INTERVAL 30 MINUTES
TIMESTAMPDIFF(MINUTE, date1, date2) > 30
пн, 7 нояб. 2022 г. в 19:49, tor
Tore Yang,
Can you please provide a full stack trace of the exception and more details
about your case? Do you create the table via DDL or via QueryEntity? Do you
have a simple reproducer?
The error looks strange, because it's not a parser responsibility to check
column types.
пт, 11 нояб. 2022 г
Hello,
Looks like the bug is related to server-side continuous queries
functionality. I've tried to reproduce it using thick-client and got
the same results, in rare cases events are lost.
чт, 25 мая 2023 г. в 06:48, Pavel Tupitsyn :
>
> Thank you for the bug report, I will have a look.
>
> On Th
Hello,
The Calcite-based SQL engine currently doesn't analyze any properties
of SqlFieldsQuery except "Sql", "Schema", "Args" and
"QueryInitiatorId". Some of the rest properties are useless for the
Calcite-based engine at all (for example, "DistributedJoins", since
all joins in the Calcite-based e
s inefficient. That's why i need
> setLocal. What should I do if without setLocal?
>
>
>
> Yours,
> Hu Tiany
> 2023/6/30
>
>
> At 2023-06-05 19:21:13, "Alex Plehanov" wrote:
> >Hello,
> >
> >The Calcite-based SQL engine currently doesn&
Hitesh,
To unsubscribe, send a message to user-unsubscr...@ignite.apache.org
(not to user@ignite.apache.org).
пт, 30 июн. 2023 г. в 13:50, Hitesh Nandwana :
>
> Why It is not subscribing?
>
> On Fri, 30 Jun, 2023, 14:17 Alex Plehanov, wrote:
>>
>> Hello,
>>
>>
Hello,
Which Ignite version do you use?
Please share exception details after "Exception during start processors,
node will be stopped and close connections" (there should be a reason in
the log, why the page delta can't be applied).
вт, 18 июл. 2023 г. в 05:05, Raymond Wilson :
> Hi,
>
> We run
Hello,
1. Coordinator is the oldest server node. So you can use something
like: ignite.cluster().forServers().forOldest().node()
2. Why can't you upgrade to the new Ignite version? Perhaps this
problem is already fixed. But if not, you can provide details for the
actual Ignite version and this wil
Hello,
1. Client sends requests to random known server node for load balancing.
2. Client uses the provided address as entry point and gets
information about other nodes from the server. If you don't need such
functionality, you can set property
ClientConfiguration.ClusterDiscoveryEnabled to false
Hello,
Please provide the query you are using. Such a stack can't be caused
by just "select * from table" (at least sorting is used). Perhaps you
are using "ORDER BY" for fields which can't be compared in SQL
(complex _key or _val for example).
вт, 13 авг. 2024 г. в 17:17, Amit Jolly :
>
> Hi,
>
Amit,
Can you please show the output of "EXPLAIN PLAN FOR "?
I've found the bug in index scan on binary object field (ticket [1]),
but I can't reproduce it with select without "order by", or without
forcing index scan.
[1]: https://issues.apache.org/jira/browse/IGNITE-23004
ср, 14 авг. 2024 г. в
Hello,
It's a known issue [1]. Now you can get cache group size via JMX only if
persistence is used.
If persistence is not used you can get allocated size only for data region
(but you can have more then one data region and assign cache groups to data
regions any way you want)
[1] : https://issue
ew file to process, I create a cachegroup to handle it, then I
> > clean everything.
> >
> > Le jeu. 13 juin 2019 à 13:28, Alex Plehanov a
> > écrit :
> >
> >> Hello,
> >>
> >> It's a known issue [1]. Now you can get cache group size v
Hello, Rick
There should be a message in the server log:
"Client connector processor has started on TCP port x" with "INFO"
level.
пн, 1 июл. 2019 г. в 10:26, rick_tem :
> Thanks for your response. I tried 10801 and it failed. My question is how
> do I find out which port it is using?
>
>
ot;\tID = " + cachedVal2.field("id"));
> System.out.println("\tName = " + cachedVal2.field("name"));
>
> // Destroy the cache.
> System.out.print("Dropped caches...");
> igniteClient.destroyCache("persons");
>
> } c
Hello,
Most probably the reason is different default values of compactFooter
property of BinaryConfiguration for thin client and server (false for
client, true for server).
Here is a ticket: [1]
You can work around this by setting BinaryConfiguration including this
property explicitly.
[1] : http
Hello,
You can set custom affinityBackupFilter in RendezvousAffinityFunction. See
[1] for example.
[1] :
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.html
пн, 28 окт. 2019 г. в 11:31, c c :
> HI, we are w
Hello,
47500 - is a discovery SPI port. For thin client connection you should use
10800 port, or configure another by clientConnectorConfiguration property.
вт, 24 дек. 2019 г. в 10:38, userx :
> Hi team,
>
> I have started an ignite server with the below command on my local machine
>
> ignite.b
Hello Mitchell,
It seems that you didn't enable metrics on data storage and data regions.
You can enable it by DataStorageConfiguration.setMetricsEnabled and
DataRegionConfiguration.setMetricsEnabled methods. Also, you can enable it
in runtime by JMX
пт, 31 янв. 2020 г. в 04:25, Mitchell Rathbun
Hello,
AFAIK apache webserver load balancer it's a balancer only for HTTP
requests. Ignite thin client protocol it's not a HTTP based protocol.
Moreover, it's async (you can send several requests on the same channel
before receiving the first response) and it's stateful (for example, if you
start
Hello,
There are a set of views which only available via SQL (not moved to the new
metrics engine yet), NODE_METRICS is one of them.
Full list of such views for Apache Ignite 2.8:
NODE_METRICS
NODE_ATTRIBUTES
BASELINE_NODES
LOCAL_CACHE_GROUPS_IO
чт, 30 апр. 2020 г. в 08:00, Denis Magda :
> Niko
35
чт, 30 апр. 2020 г. в 12:22, Ivan Fedorenkov :
> Thank you Alex! Is there any ticket for adding those views that I can
> track?
>
> чт, 30 апр. 2020 г. в 09:23, Alex Plehanov :
>
>> Hello,
>>
>> There are a set of views which only available via SQL
Hello,
1. Yes, the same way as with the thick client.
2. Here [1] is a short description of partition awareness future for .NET
thin client (but this description also relevant to other thin clients,
including java thin client). Here [2] is a low-level description (mostly
for Apache Ignite develope
Hello,
Currently, there is no way to add a new address without the client restart.
But there is a feature under development [1], perhaps, it will be useful
for your case.
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-44%3A+Thin+client+cluster+discovery
ср, 6 мая 2020 г. в 10:48, ka
Hello,
I don't think that near cache for thin client on Ignite level it's a
good idea.
Expiration is not the only case here. For thick clients near caches are
transactionally consistent. For thin clients such a guarantee never can be
provided.
Near cache for thin clients will be either too heavy
Hello,
You can't get server-side JMX metrics by thin client, but you can query
views by SQL.
Here [1] is an example of querying system views using thin client
(currently system schema was renamed, so you should use setSchema("SYS")
instead of setSchema("IGNITE"))
The full list of system views impl
Hello,
On server-side there is property ExpiryPolicyFactory (not just
ExporyPolicy). Factory, in general, can return different expiry policy
values for each call, so there is no common way to convert factory class to
policy class, except some predefined factory implementations which always
return
Hello,
By thick client I mean "not by thin client" (sorry for the confusion), i.e.
by client node, by server node, by xml configuration, etc.
вт, 26 мая 2020 г. в 12:49, kay :
> Thank you so much for reply.
>
> I used xml config file for cache Expirypolicy at server node
> like
>
>
> f
Hello,
IgniteServices.service(String name) method return service instance if it's
deployed locally or null.
чт, 11 июн. 2020 г. в 11:16, Mikael :
> Hi!
>
> Is there any good way to detect if a service is running local or remote
> ? I guess I could check the instance of the returned proxy and see
Yes, you're right, control.sh does not support SSL.
2018-07-20 10:24 GMT+03:00 Paul Anderson :
> Well.. It appears not to, can you confirm pls.
>
As far as I know TOAD support only limited set of DBMS.
For SQL querying you can use any other tool which support JDBC, like
DBeaver (GUI) or sqlline (CLI, included into Ignite distributive).
2018-08-02 13:48 GMT+03:00 ApacheUser :
> Hello Ignite Team,
>
> Is it possible to connect to Ignite from
"Non-heap memory ..." metrics in visor have nothing to do with offheap
memory allocated for data regions. "Non-heap memory" returned by visor it's
JVM managed memory regions other then heap used for internal JVM purposes
(JIT compiler, etc., see [1]). Memory allocated in offheap by Ignite for
dat
AbstractStringBuilder.java:124)
>
>
> On Fri, Aug 3, 2018 at 4:16 AM, Alex Plehanov
> wrote:
>
>> "Non-heap memory ..." metrics in visor have nothing to do with offheap
>> memory allocated for data regions. "Non-heap memory" returned by visor
>>
Hi, Arun
When daemon node (visor) first time join the cluster it switch the cluster
to compatibility mode. In this mode node containing baseline topology
information will fail to join even if daemon node already leave the
cluster. This issue was fixed by ticket [1] and will be available in Ignite
You can restart the cluster. Compatibility mode flag is not stored to PDS,
it exists only in memory.
2018-08-13 9:06 GMT+03:00 arunkjn :
> Thanks Alex,
>
> How can I fix this in the current cluster without resetting the persistence
> state of entire cluster?
>
>
>
> --
> Sent from: http://apache-
Hi, Huang,
Already was discussed here [1]. You probably run visor (daemon node) to
join cluster, which switch cluster to compatibility mode. You can restart
to switch it to normal state again. Fix (ticket IGNITE-8774) will be
available in Ignite 2.7
[1]:
http://apache-ignite-users.70518.x6.nabble
Hello, Eugene!
> 2) How come Non-heap memory usage is minimal?
"Non-heap memory" here it's JVM managed memory regions other then heap used
for internal JVM purposes (JIT compiler, method area, etc.), it's not a
memory used by Ignite to store data (information about this memory can be
obtained by d
Hello,
Does baseline topology include both of your server nodes?
2018-08-21 3:32 GMT+03:00 scottmf :
> Hi, I'm seeing the errors below in my ignite cluster. This occurs
> consistently in my env when I apply a "rolling upgrade" where I take down
> one node at a time by updating them with a new ja
I think you are confusing the "current cluster topology" and the "baseline
topology" terms. Baseline topology cannot contain client nodes. Current
baseline topology can be printed or changed by "control.sh" script.
You can read more about baseline topology here: [1]
[1]: https://apacheignite.readm
Hi,
maxSize and initialSize are per-node values.
In your example, if you have more then one node with this configuration,
each node will allocate 16GB off-heap memory.
чт, 23 авг. 2018 г. в 18:04, yfernando :
> Hi All,
>
> When setting the defaultDataRegionConfiguration parameter in the
> Ignite
Hello,
StopRoutineDiscoveryMessage is sent when a continuous query is stopped
(when query cursor is closed) to unregister listener on all nodes.
DiscoveryCustomEvent is an internal API event, what for you listening to
this type of events?
вт, 28 авг. 2018 г. в 12:43, Sashika :
> Hi,
>
> In one o
Method ignite.cluster().active() shows whether or not a cluster was
activated.
To check started/stopped state you can use method
Ignition.state(igniteInstanceName).
ср, 29 авг. 2018 г. в 19:36, Paolo Di Tommaso :
> Hi Igniters,
>
> What's the suggested way to check if the grid is stopped. I'm try
Hello Chris,
There is no such metric as "node is healthy" now, but each node provides a
lot of low-level metrics such as CPU usage, memory usage, jobs
execution/waiting time etc, which you can combine and define your own
criteria of "healthy node". These metrics available cluster-wide and
contains
Hello Eugene,
Did you activate this cluster before?
Baseline topology can be set explicitly (via control.sh script or Java API)
or implicitly after the first activation. Currently, your cluster is not
activated. If cluster never was activated before and you didn't set
baseline topology explicitly,
There is also the bug (ticket [1]) related to daemon nodes (visor joins the
cluster as a daemon node). Visor switches cluster to compatibility mode, in
this mode baseline topology is not supported. You can read more details
here: [2]. I think this bug can be related to your case too.
Please shutdow
In your previous post was a message: "Current topology version: 20". It
does not look like a cluster with 3 nodes just started. So, I think the
cluster was not restarted correctly, it still was in compatibility mode.
In your last post, it was restarted correctly and not in compatibility mode
anymor
Hello, Wilhelm!
Default SQL schema is PUBLIC, when you create tables via SQL or query
tables without specifying schema - default schema is used. When you create
tables via java - cache name is used as schema. Your sqlline output shows
that there are two tables A and B0 were created in schemas A an
In case of Cache_A and Cache_B you need to use quote symbols, since table
schema is case-sensitive, but parser convert schemas in your query to upper
case.
Try these statements:
SELECT * FROM "Cache_B".B0;
SELECT * FROM "Cache_A".A;
2018-03-21 20:27 GMT+03:00 Wilhelm :
> Super - Thanks a lot Ale
It's incorrect to use cache object to calculate cache data size. What you
got now is a footprint of the Ignite infrastructure used to manage your
data, but not a footprint of your data itself, since data are stored in
off-heap and this tool only calculate on-heap size of objects referenced by
cache
Hello Amit,
You can use ClusterNodeAttributeAffinityBackupFilter and introduce
some virtual zones. For example, if you have 5 nodes in zone 1 and 5
nodes in zone 2, you can assign 'zone1' attribute value to 3 nodes
from zone 1, assign 'zone2' attribute value to 3 nodes from zone 2,
and assign 'zon
Hello,
Calcite engine in Ignite 2.16 can't expand the array parameter to table. It
can be done with the UNNEST operator, but it's planned for 2.18 Ignite
release.
пн, 17 мар. 2025 г. в 15:49, MJ <6733...@qq.com>:
> Ignite 2.16
>
> Thanks,
> MJ
>
> Original
> --
> From
90 matches
Mail list logo
