/jira/browse/IGNITE-14441
--
Taras Ledkov
Mail-To: tled...@gridgain.com
l#GUID-1C40C43B-3823-4848-8B5A-D2F97A82F79B
--
Taras Ledkov
Mail-To: tled...@gridgain.com
C and ODBC is mostly unified)
вт, 6 апр. 2021 г. в 15:05, Taras Ledkov :
Hi,
Ignite 3.0 requires a rethinking of the query API.
We have 'cache.query()' and 'SqlFieldQuery' abstractions at the Ignite
2.x native API and several JDBC implementation for clients.
I propose to thin
appreciate your help.
Bests,
Xi
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
--
Taras Ledkov
Mail-To: tled...@gridgain.com
/internal/processors/query/stat/hll/serialization/IHLLMetadata.java
--
Taras Ledkov
Mail-To: tled...@gridgain.com
cribe the features that was implemented in this
merge?
How users supposed to use them?
Do we have plans to document?
23 июня 2021 г., в 09:21, Taras Ledkov написал(а):
Hi,
We have discussed BCrypt include/add dependency here [1].
AFAIK and as long as I can remember Ignite project try to minimize
uired.
Also it'll be great to have a transactional support for such
queries,
like
the "select for update" query provides. But I don't dig there
much. It
will
be a next step if this API will be implemented.
I've prepared an IEP-71 for that [1] with more details. Please
share your
thoughts.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-71+Public+API+for+secondary+index+search
--
Taras Ledkov
Mail-To: tled...@gridgain.com
or throws exception if there is not any index
that match specific criteria.
BTW, Mongo DB doesn't make user to write index name in query. It just
works.
чт, 26 авг. 2021 г., 15:52 Taras Ledkov :
Hi,
It is an usability nightmare to make user write index name in all
cases.
I don't see an
our=17&min=0&sec=0&p0=224
-Val
--
Taras Ledkov
Mail-To: tled...@gridgain.com
Hi colleagues,
2Pavel:
> RecordView txView = view.withTransaction();
Can we use the syntax (see below) to attach the table / operation to the
started transaction?
RecordView txPersonView =
person.recordView().withTransaction(txView.transaction());
On Mon, Nov 29, 2021 at 1:34 PM Pavel Tupit
Hi Igniters,
There is an issue to add ability to specify INLINE_SIZE for sorted index on
the primary key and index on affinite fields [1].
Please take a look at the last comment (proposal).
I duplicate the proposal here.
*Proposal:*
add to the public QueryEntity properties:
- Integer primaryKeyI
Hi, Igniters.
There was know issue described at the [IGNITE- 16098] case 1.
These issue is the cause of not symmetric cache API and SQL API:
we cannot create the same table by SQL and cache API (with se identical
internal structures).
In more detail: it is impossible now to create a sorted PK inde
+1
On Tue, May 31, 2022 at 12:03 PM Aleksandr Pakhomov
wrote:
> Alexander,
>
> I am not sure that now we can define all
> security standards that will be implemented
> by Ignite 3. But I can mention the most popular:
> OAuth2/OpenId, LDAP.
>
> I’ve mentioned them in IEP but I believe that
> the
2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
--
With best regards,
Taras Ledkov
as updated:
Scope Freeze: August 18, 2022
Code Freeze: August 25, 2022
Voting Date: September 8, 2022
Release Date: September 15, 2022
[1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14
--
With best regards,
Taras Ledkov
as updated:
Scope Freeze: August 18, 2022
Code Freeze: August 25, 2022
Voting Date: September 8, 2022
Release Date: September 15, 2022
[1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14
PS. Fix typos at the prev message.
--
With best regards,
Taras Ledkov
Hi,
1. Petr, could you grant me TC permissions to run release builds please?
2. Pavel, please cherry pick your patch for IGNITE-17559 [1] to the release
branch ignite-2.14 [2]. Or we could move the issue to the next release?
[1]. https://issues.apache.org/jira/browse/IGNITE-17559
[2]. https://gi
Hello!
I have added you to JIRA and Wiki as contributor.
Please make sure to read
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Dear Ignite Community!
The planning release date was updated [1]:
Code Freeze: September 7, 2022
Voting Date: September 21, 2022
Release Date: September 28, 2022
I delayed code freeze for two weeks because there is bunch of important patches
for the release that require a bit of time to finaliz
Dear Ignite Community!
I'm announcing a code freeze for the 2.14 release [1]. Only blockers
are accepted to be included to the scope.
[1]. https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.14
Dear Ignite Community!
Release 2.14 has been delayed due to performance issues (compare with 2.13) for
IgniteSqlQueryBenchmark in in-memory mode. We're looking.
Any suggestions and support are welcome.
Hi, Ivan.
My apologies.
A blocking performance issue has been fixed [1]. And the release candidate is
verified and ready to be voted on. What do you think about the 2.14.1 release,
or can the fix wait until 2.15?
I'm going to start VOTE just now.
[1]. https://issues.apache.org/jira/browse/IGNIT
play/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
This vote will be open for at least 3 days till Mon Oct 3, 2022, 20:00 UTC.
https://www.timeanddate.com/countdown/vote?iso=20221003T20&p0=0&msg=VOTE+on+the+Apache+Ignite+Release+2.14.0+RC0&font=sanserif
--
With best regards,
Taras Ledkov
Pavlov (binding)
- mwiesenberg
0 votes:
- Ilya Kasnacheev
The new release will be announced soon.
--
With best regards,
Taras Ledkov
know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask
--
With best regards,
Taras Ledkov
Hi,
+1 for remove Visor related code.
Unfortunately we have to migrate `control-utility` to use IgniteClient (thin
client) before drop GridClient. I guess we will do it in the future.
Also, the old thin JDBC based on the GridClient (classes placed at the
org.apache.ignite.internal.jdbc.*) must
ures of thin clients
on both
server and client as they desire.
What are your thoughts guys?
Best Regards,
Igor
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ese two masks.
This change has many other positive effects:
1. It improves readability and also potentially simplifies debugging.
2. It gives users the ability to enable or disable features of thin clients
on both
server and client as they desire.
What are your thoughts guys?
Best Regards,
Igor
Continuously generated thread dumps in failure processor
slow
down the whole system
IGNITE-12489 Error during purges by expiration: Unknown page type
--
BR, Sergey Antonov
--
Taras Ledkov
Mail-To: tled...@gridgain.com
an.
I think PR may be useful to demonstrate the proposal.
Please let me know your opinion.
[1]. https://github.com/apache/ignite/pull/7559
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ay be changed in runtime
This applies to many other config properties, but we don't name them
`Initial`
Let's just make it SqlConfiguration.
On Mon, Mar 23, 2020 at 1:04 PM Taras Ledkov wrote:
Hi, Igniters.
I propose to introduce separate configuration class for S
the GridH2Table. (#7551)
- bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
#7494.
- 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
Denis Garus,
Taras Ledkov,
Alexey Plekhanov,
Ivan Bessonov,
Can you help me with above commits and cherry-pick your contributi
- 0b185b192f IGNITE-12800 SQL: local queries cursors must be
closed
or
full read to unlock the GridH2Table. (#7551)
- bcaae8deef IGNITE-12734 Fixed scan query over evicted
partition -
Fixes
#7494.
- 683f22e64f IGNITE-12756 TcpCommunication SPI metrics
improvement
Denis Garus,
Taras Ledkov,
Al
patch.
Any comments / suggestions?
[1]. https://issues.apache.org/jira/browse/IGNITE-13154
--
Taras Ledkov
Mail-To: tled...@gridgain.com
solve it. The text can mention these new
control.sh commands and advise to remove the old metadata.
-
Denis
On Thu, Jun 18, 2020 at 7:42 AM Taras Ledkov wrote:
Hi,
I propose to introduce ability for a user to manage cluster binary types.
This functionality is useful when user needs to change
ards,
Ivan Pavlukhin
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ault value.
Please your comments.
Please pay your attention to concept & design of the publishing a
property by 'PublicProperty' and set of the new commands.
[1]. https://issues.apache.org/jira/browse/IGNITE-13186
[2]. https://github.com/apache/ignite/pull/8208
--
Taras Le
ur users don’t have to wait «one more release» with only change ‘implements
SimpleDistributedPublicProperty’ for some property.
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145724615
2 сент. 2020 г., в 23:11, Taras Ledkov написал(а):
Hi,
Motivation: we have to ma
ults
of such kind of edits»
So user can fix this list manually.
WDYT?
3 сент. 2020 г., в 10:21, Taras Ledkov написал(а):
Hi,
Why do we want to restrict property management somehow?
I guess some properties (may be future properties) shouldn't be published
through generic
ve started drafting the IEP for this change [2]. Please let
me know your thoughts.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-Meetups
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-59%3A+JAR-based+code+deployment
-Val
--
Taras Ledkov
Mai
cache.put()' but it
looks like significant usability issue.
To confuse the 'PersonKey.class.getName()' and
'node.binary().builder("PersonKey")' is a typical mistake of Ignite
newcomers.
One more argument for check: SQL INSERT sematic means the row is
inserted
g. document-oriented, JSON, whatever).
On Fri, Feb 22, 2019 at 1:52 AM Denis Magda
wrote:
Folks,
Do we want to preserve the annotation-based configuration?
There
are
too
many ways to configure SQL indexes/fields.
For instance, if our new SQL API could see and access all of
the
fields
out-of-
onKey.class.getName()' and
'node.binary().builder("PersonKey")' is a typical mistake of
Ignite
newcomers.
One more argument for check: SQL INSERT sematic means the row
is
inserted into the specified TABLE, not into the cache.
So, throw IgniteSQLException is expected behavior in this
case, i
think.
[1]. https://issues.apache.org/jira/browse/IGNITE-5250
--
Taras Ledkov
Mail-To: tled...@gridgain.com
--
Taras Ledkov
Mail-To: tled...@gridgain.com
/core/src/main/java/org/apache/ignite/IgniteCompute.java)
Please look through the new API and let me know any comments.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
7 at 5:45 PM, Semyon Boikov wrote:
Hi Taras,
Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
seems that ComputeTaskFuture is needed only for tasks?
On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov
wrote:
Gents
I've done changes of the IgniteCompute a
Denis,
Please review the javadoc of the affinity jobs.
PR: https://github.com/apache/ignite/pull/1550
On 08.12.2016 12:06, Taras Ledkov wrote:
Denis,
The second point is absolutely correct.
The rebalancing isn't blocked. The partition will not be evicted while
the partition is res
Denis,
I've fixed javadocs for affinityRun/affinityCall.
Please review the changes at the PR:
https://github.com/apache/ignite/pull/1550
On 08.12.2016 12:06, Taras Ledkov wrote:
Denis,
The second point is absolutely correct.
The rebalancing isn't blocked. The partition will not
ughts?
Vladimir.
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
--
Taras Ledkov
Mail-To: tled...@gridgain.com
pool, additional one, or maybe force user to provide his own Executor?
[1] https://issues.apache.org/jira/browse/IGNITE-4477
Thanks!
-Dmitry.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
e to clearly document that
the same
affinity function must provide the same partition assignments for
all the
caches.
Also I know that Taras Ledkov was working on a decent stateless
replacement
for FairAffinity, so we should not loose anything here.
Thoughts?
Serg
v
2017-04-10 12:42 GMT+03:00 Sergi Vladykin <
sergi.vlady...@gmail.com
:
Why wouldn't we have useBalancer always enabled?
Sergi
2017-04-10 12:31 GMT+03:00 Taras Ledkov :
Folks,
I worked on issue https://issues.apache.org/
jira/browse/IGNITE-3018
that
is related to performance o
ic pool: b2e85208b51-4fbcb569-07a2-480e-9be1-512bc320
Issue: https://issues.apache.org/jira/browse/IGNITE-4699
Please share your thoughts or ask questions.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
nodes where the
specific executor is configured.
On 18.04.2017 18:00, Christos Erotocritou wrote:
I assume its not currently possible to constrain an executor pool to be started
only on a specific node?
--
Taras Ledkov
Mail-To: tled...@gridgain.com
Igor,
I see that you are the main contributor of the ignite-cassandra-* modules.
Could you please review the changes at the ingite-cassandra-store module
for the issue IGNITE-5036.
Please take a look at the issue:
https://issues.apache.org/jira/browse/IGNITE-5036
--
Taras Ledkov
Mail-To
go, since "DEFAULT" is reserved SQL keyword.
Personally I prefer "public".
Any other thoughts?
Vladimir.
[1] https://issues.apache.org/jira/browse/IGNITE-5320
--
Taras Ledkov
Mail-To: tled...@gridgain.com
- Linear regression algorithms: https://issues.apache.org/
jira/browse/IGNITE-5012
- K-means clustering: https://issues.apache.org/
jira/browse/IGNITE-5113
Please join the thread and share your thoughts, ideas and
concerns.
—
Denis
--
Best Regards, Vyacheslav
--
Best Regards, Vya
/IGNITE-4756
<https://issues.apache.org/jira/browse/IGNITE-4756>
What do you think about it ?
Issue is about RendezvousAffinityFunction and FairAffinityFunction
classes.
Vadim
--
Taras Ledkov
Mail-To: tled...@gridgain.com
135779.html
[5] http://www.java-countdown.xyz/
--
Taras Ledkov
Mail-To: tled...@gridgain.com
r
topology change must handled on user side by retry query implemented by
user, because some data have been delivered to user and we don't track
which data is delivered.
PROS:
- no deadlocks;
- no contention on table lock for SQL query.
What do you think?
--
Taras Ledkov
Mail-To: tled...@gridgain.com
cking
implementation may give them serious performance benefits (e.g. CREATE
INDEX).
So I propose to go with your solution for now, and start thinking about SQL
-> PME integration in the background.
Vladimir.
On Wed, Nov 21, 2018 at 2:23 PM Taras Ledkov wrote:
Hi community,
We will enhance
.
Makes sense?
On Wed, Nov 21, 2018 at 4:15 PM Taras Ledkov wrote:
Vladimir,
The query protocol will be changed in both solution.
The tables versions must be added to the 'GridQueryNextPageResponse'
message
and must be compared on the reduce node too. Because the DLL / DML race
may
GNITE-6048
[3] https://issues.apache.org/jira/browse/IGNITE-6046
[4] https://issues.apache.org/jira/browse/IGNITE-6047
[5] https://issues.apache.org/jira/browse/IGNITE-5233
D.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
);
assertEquals(1L, cursor.getAll().get(0).get(0));
}
}
}
[1] http://www.h2database.com/html/history.html
[2]http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ding with
H2 type mapping. But AFAIK Spark doesn't support plain java objects.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
lain why MatchError happens?
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ions that
must be reserved on the target node before job execution.
Dmitry, colleagues, please comment or approve.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
k*(...).affinityRun();
On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov
wrote:
Igniters,
Lets discuss the changes of public API at the IgniteCompute.
The new methods affinityRun & affinityCall is added by working on
IGNITE-2310.
https://issues.apache.org/jira/browse/IGNITE-2310
Please take
thods? We can resort to "with" semantics instead:
IgniteCompute.*withPartitionsToLock*(...).affinityRun();
On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov
wrote:
Igniters,
Lets discuss the changes of public API at the IgniteCompute.
The new methods affinityRun & affinityCall is added
as well. To my
knowledge, this feature ensures that a partition will not be migrated while
affinityRun/Call is executed, right?
On Thu, Jul 7, 2016 at 3:02 AM, Taras Ledkov wrote:
Igniters,
Please take a look at the next proposal of changes at
IgniteCompute.affinityRun / affinityCall:
https
t.
On Thu, Jul 7, 2016 at 5:44 AM, Taras Ledkov wrote:
Igniters,
The issue https://issues.apache.org/jira/browse/IGNITE-2310 is updated
with comment
about the changes at the IgniteCompute. Please comment the ticket.
The changed javadoc of the affinityRun/Call is available to review at the
bra
Thanks,
I updated the ticket because proposed API is ambiguous.
e.g.: affinityRun(null, 0, job);
The fist parameter is a collection or a cache name?
My changes are at the ticket.
11.07.2016 12:59, Yakov Zhdanov пишет:
I replied in the ticket.
--Yakov
2016-07-11 12:43 GMT+03:00 Taras Ledkov
On 11.07.2016 12:59, Yakov Zhdanov wrote:
I replied in the ticket.
--Yakov
2016-07-11 12:43 GMT+03:00 Taras Ledkov :
Hi,
Dmitry, thanks for your comments.
I've updated the ticket with the reasons of my version of the API changes.
I'm OK with the both version of the API.
Igniters, pleas
Ignite compute has no relation to the cache's transaction.
I think that IgniteCache.invokeAll() is appropriate for described case.
On Wed, Dec 7, 2016 at 4:00 PM, Игорь Г wrote:
> Hi, igniters!
>
> Before openning JIRA ticket, I want to ask question about affinityCall or
> affinityRun transacti
Denis,
The second point is absolutely correct.
The rebalancing isn't blocked. The partition will not be evicted while the
partition is reserved.
I'll update javadoc ASAP.
On Wed, Nov 30, 2016 at 10:23 PM, Denis Magda wrote:
> Taras,
>
> There is a question in regards to the feature contribute
GitHub user taras-ledkov opened a pull request:
https://github.com/apache/ignite/pull/1368
IGNITE-4462: Remove grid name from HadoopIgfsEndpoint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4462
to ignore the last field in the version when
doing a compatibility test, e.g., 2.5.0 and 2.5.foobar would be considered
compatible.Is there some reason ignite requires and exact match?
How do other Ignite users handle this problem?
Thanks,
-DH
--
Taras Ledkov
Mail-To: tled...@gridgain.com
+ hash] [1]
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ns and (possibly) analysis
what other vendors use.
On Tue, Jan 16, 2018 at 3:56 PM, Taras Ledkov wrote:
What do you think about usage bcrypt [1], [2] to store encrypted password?
[1] https://stackoverflow.com/questions/1561174/sha512-vs-blowfi
sh-and-bcrypt
[2] https://en.wikipedia.org/wiki/B
rypt.java' ?
[1].
https://github.com/jeremyh/jBCrypt/blob/master/src/main/java/org/mindrot/BCrypt.java
On 18.01.2018 13:50, Taras Ledkov wrote:
Password hashing algorithms of the popular vendors:
mysql: SHA-265, old-native-hash
postgres: MD5, DES, Extended DES, Blowfish-based
oracle: SHA-1
So
-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-tc20679.html
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ticationEnabled
recently.
Would you mind adding it to IgniteConfigutation.cs [1]?
Vladimir.
[1] https://issues.apache.org/jira/browse/IGNITE-8034
--
Taras Ledkov
Mail-To: tled...@gridgain.com
ment variable.
Thoughts?
Vladimir.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
+1 for remove
Taras Ledkov created IGNITE-14274:
-
Summary: Calcite integration: refactoring aggregates converter
rules: single and map/reduce
Key: IGNITE-14274
URL: https://issues.apache.org/jira/browse/IGNITE-14274
Taras Ledkov created IGNITE-14441:
-
Summary: Query plan printed for long running query must use
IGNITE_TO_STRING_INCLUDE_SENSITIVE policy
Key: IGNITE-14441
URL: https://issues.apache.org/jira/browse/IGNITE-14441
Taras Ledkov created IGNITE-14451:
-
Summary: PK becomes corrupted after node restart
Key: IGNITE-14451
URL: https://issues.apache.org/jira/browse/IGNITE-14451
Project: Ignite
Issue Type: Bug
Taras Ledkov created IGNITE-14461:
-
Summary: Track down those who initiated a query
Key: IGNITE-14461
URL: https://issues.apache.org/jira/browse/IGNITE-14461
Project: Ignite
Issue Type
Taras Ledkov created IGNITE-14471:
-
Summary: JDBCv2: query cursors leak when node to execute queries
is specified
Key: IGNITE-14471
URL: https://issues.apache.org/jira/browse/IGNITE-14471
Project
Taras Ledkov created IGNITE-14508:
-
Summary: Calcite integration: introduce SQL logical test runner
Key: IGNITE-14508
URL: https://issues.apache.org/jira/browse/IGNITE-14508
Project: Ignite
Taras Ledkov created IGNITE-14531:
-
Summary: Calcite improvements. Support DISTINCT for aggregates
call at the execution
Key: IGNITE-14531
URL: https://issues.apache.org/jira/browse/IGNITE-14531
Taras Ledkov created IGNITE-14535:
-
Summary: Caclite SQL engine capabilities
Key: IGNITE-14535
URL: https://issues.apache.org/jira/browse/IGNITE-14535
Project: Ignite
Issue Type: Improvement
Taras Ledkov created IGNITE-14537:
-
Summary: Nested arbitrary queries hangs on optimizing
Key: IGNITE-14537
URL: https://issues.apache.org/jira/browse/IGNITE-14537
Project: Ignite
Issue
Taras Ledkov created IGNITE-14539:
-
Summary: Calcite engine. Support DISTINCT ON expression
Key: IGNITE-14539
URL: https://issues.apache.org/jira/browse/IGNITE-14539
Project: Ignite
Issue
Taras Ledkov created IGNITE-14540:
-
Summary: Calcite engine. Support correlated subquery in having
Key: IGNITE-14540
URL: https://issues.apache.org/jira/browse/IGNITE-14540
Project: Ignite
Taras Ledkov created IGNITE-14541:
-
Summary: Calcite engine. HAVING fails on scalar
Key: IGNITE-14541
URL: https://issues.apache.org/jira/browse/IGNITE-14541
Project: Ignite
Issue Type: Bug
Taras Ledkov created IGNITE-14542:
-
Summary: Calcite engine. Need to support TableFunctions /
SYSTEM_RANGE dynamic table
Key: IGNITE-14542
URL: https://issues.apache.org/jira/browse/IGNITE-14542
Taras Ledkov created IGNITE-14543:
-
Summary: Calcite engine. COUNT agregate on scalar values fails
Key: IGNITE-14543
URL: https://issues.apache.org/jira/browse/IGNITE-14543
Project: Ignite
Taras Ledkov created IGNITE-14544:
-
Summary: Calcite engine. Implement DISTING aggregates
Key: IGNITE-14544
URL: https://issues.apache.org/jira/browse/IGNITE-14544
Project: Ignite
Issue Type
Taras Ledkov created IGNITE-14545:
-
Summary: Calcite engine. Unicode literal not supported
Key: IGNITE-14545
URL: https://issues.apache.org/jira/browse/IGNITE-14545
Project: Ignite
Issue
Taras Ledkov created IGNITE-14546:
-
Summary: Calcite engine. MIN/MAX aggregates doesn't support string
types
Key: IGNITE-14546
URL: https://issues.apache.org/jira/browse/IGNITE-14546
Project: I
1 - 100 of 280 matches
Mail list logo