Hey Saikat,
Are you still working on this ticket?
https://issues.apache.org/jira/browse/IGNITE-7285
Seems that's the last API that doesn't support timeouts - JDBC and ODBC
drivers already go with it.
If you don't have time to complete the changes then someone else from the
community can take
>
> Do you find the presence of GG's tickets in the commit is a reason for
> revert?
No, GG employees just need to follow "commit messages" guidelines removing
GG-specific details from the messages.
-
Denis
On Thu, Aug 8, 2019 at 1:52 PM Dmitriy Pavlov wrote:
> Hi Igniters,
>
> I little
Dmitry,
Please add this BTree corruption fix to the scope:
https://issues.apache.org/jira/browse/IGNITE-11953
Plus, I would upgrade our Spark integration to version 2.4 as long as 2.3
goes with limitations reported by our users:
https://issues.apache.org/jira/browse/IGNITE-12054
Nickolay, could
Denis Magda created IGNITE-12054:
Summary: Upgrade Spark module to 2.4
Key: IGNITE-12054
URL: https://issues.apache.org/jira/browse/IGNITE-12054
Project: Ignite
Issue Type: Task
The Project Management Committee (PMC) for Apache Ignite
has invited Ilya Kasnacheev to become a committer and we are pleased
to announce that he has accepted.
Ilya is one of the most active and valuable Ignite committers who is not
only contributing source-code changes but also takes an active
Hi,
That's a known limitation caused by the fact that Ignite keeps metadata
even after a column is fully dropped. This to be addressed with the next
major release - Ignite 3.0.
As for now,
*When this happens _and you are still in development_, you need to go into
the*
*file system and remove
Hello Alexey, please check out this section:
https://apacheignite.readme.io/docs/transactions#section-integration-with-jta
Is that what you are looking for?
-
Denis
On Mon, Jul 29, 2019 at 9:44 AM Алексей Самойленко <
alexei.samoyle...@gmail.com> wrote:
> Hello, it would be nice to have a
r the clarification, will try to vote
>
> чт, 25 июл. 2019 г. в 04:11, Denis Magda :
>
> > Alexey,
> >
> > I've changed format on the wiki so that every community member can cast
> +1
> > and -1 vote explaining his/her stance. This should help us to filter out
> &
Igor, thanks for looking into this.
Even if the root cause is on an application end, our code mustn't generate
an NPE.
Ignite dev community and *Ivan Rakov* in particular, have you seen this
before? Should we file a ticket or the issue has already been resolved?
-
Denis
On Wed, Jul 24, 2019
Pavel,
Do we already have a ticket or do you want me to create one?
-
Denis
On Wed, Jul 24, 2019 at 1:21 AM Pavel Tupitsyn wrote:
> Denis, yes, looks like a simple thing to add.
>
> On Tue, Jul 23, 2019 at 10:38 PM Denis Magda wrote:
>
>> Looping in the dev list.
>>
and do forks if a new
conflicting version has to be supported but there is still significant
usage of the old one.
--
Denis Magda
On Tue, Jul 23, 2019 at 3:16 AM Alexey Zinoviev
wrote:
> I have a few ideas, maybe somebody will support me
> 1. Exclude Spatial Indexes from API for rem
Looping in the dev list.
Pavel, Igor and other C# maintainers, this looks like a valuable extension
of our C# APIs. Shouldn't this be a quick addition to Ignite?
-
Denis
On Mon, Jul 22, 2019 at 3:22 PM Raymond Wilson
wrote:
> Alexandr,
>
> If .WithExecute is not planned to be made available
rry if I am repeating something. I checked a page [1] and have
> not
> > > > > found several items.
> > > > > 1. I thought that there was an agreement of dropping OLD service
> grid,
> > > > > was not it?
> > > > > 2. Also IndexingSpi seems
Ignite is an open-source project and doesn't have any licenses. You can use
it for free the way you like.
As for a relation DB acceleration, please refer to these docs:
https://apacheignite.readme.io/docs/3rd-party-store
-
Denis
On Mon, Jul 22, 2019 at 11:35 AM Sercan DURSUN <
Igniters,
How about doing this release in October? There are many bug fixes plus by
that time we should be able to roll out our new metrics framework. Nickolay
what do you think about the latter?
-
Denis
On Mon, Jul 22, 2019 at 9:41 AM Nikolay Izhikov wrote:
> Hello, Akhil.
>
> There are no
Thanks Dmitry, this looks good to me.
-
Denis
On Fri, Jul 19, 2019 at 9:08 AM Dmitriy Pavlov wrote:
> Hi Igniters,
> Please review following announce email for 2.7.5. I would like to send an
> email during the weekend.
> {{{
> The Apache Ignite Community is pleased to announce the release of
it.
-
Denis
On Tue, Jul 16, 2019 at 7:58 AM Alexey Goncharuk
wrote:
> Denis,
>
> Are we ready to present the list to the user list?
>
> вт, 2 июл. 2019 г. в 00:27, Denis Magda :
>
> > I wouldn't kick off dozens of voting discussions. Instead, the content on
> > the
gt; There is no difference in company suggesting this: 'com.microsoft',
> > 'com.intel' - I see no difference there.
> >
> > Disclaimer: Opinions expressed in this email are those of the author,
> > and do not necessarily represent the views of any company the author
> > m
The question is - *Who can apply those changes*.
> > > > > > > >
> > > > > > > > I think all Ignite commiters should have write priveledges
> to H2
> > > fork.
> > > > > > > >
> > > > > > > > В Ср, 10/07/2019 в 1
:28 AM Rob Vesse wrote:
> Denis
>
>
>
> Stepping backwards from the legal question: why does the Ignite community
> feel that they need to fork H2?
>
>
>
> Can the community simply not work to contribute your desired changes to
> the upstream H2 community?
>
blished under
> "MPL-2.0", "EPL-1.0", or "(MPL-2.0 OR EPL-1.0)". I don't believe there
> would be interest in publishing ASF-community authored source under a
> different license than Apache 2.0.
>
> Hen
>
> On Tue, Jul 9, 2019 at 12:50 PM D
Pavel, Igor, Aleksandr,
Could you please check this thread:
https://stackoverflow.com/questions/56803904/java-outofmemoryexception-when-using-continuous-query-in-ignite
Here is a related ticket: https://issues.apache.org/jira/browse/IGNITE-11970
Is it easy to implement this optimization? Can
There is the "ignite-dev" user that manages Nubble forums linked to the dev
list:
http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1
Do you we know a password used for that account? Dmitry, is it in that
passwords page available for the PMC group?
Adding a valid legal mailing list.
-
Denis
On Tue, Jul 9, 2019 at 12:46 PM Denis Magda wrote:
> Apache Ignite's SQL engine is tightly coupled with the H2 database engine
> [1] that provides basic parsing and query execution capabilities.
>
> H2 is licensed under dual MPL 2.0 an
Apache Ignite's SQL engine is tightly coupled with the H2 database engine
[1] that provides basic parsing and query execution capabilities.
H2 is licensed under dual MPL 2.0 and EPL 1.0 [2], thus Ignite community
uses H2 binary artifacts for the development needs and doesn't have H2
source code
ct.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 4 июл. 2019 г. в 18:57, Denis Magda :
>
> > Hi Igniters,
> >
> > As you know, Ignite SQL engine is tightly coupled with the H2 database
> that
> > provides basic parsing and query execution capabilities.
Hi Igniters,
As you know, Ignite SQL engine is tightly coupled with the H2 database that
provides basic parsing and query execution capabilities. This synergy has
worked well for a while until Ignite SQL engine got a much broader adoption
for all sort of use cases.
Presently, there is a list of
Looping in Ignite dev community,
Nikolay, in my understanding the new metrics & tracing framework will be
flexible enough so that we can add required metrics for data structures
like queues. Is this counted in our design?
-
Denis
On Mon, Jul 1, 2019 at 8:42 AM Ilya Kasnacheev
wrote:
> Hello!
issue.
> Amir is working on implementation now.
>
> ср, 5 сент. 2018 г. в 1:53, Denis Magda :
>
> > Amir, Anton,
> >
> > How is dev/review process going? Is there any chance we get this
> capability
> > into 2.7?
> >
> > --
> > Denis
&
Clients have a separate
> repository and a release lifecycle or not.
> 2. Are we going to exclude tests for unsupported modules from Ignite
> TeamCity?
> 3. Will we adress implementing Java 9+ modules during that process?
>
> чт, 27 июн. 2019 г. в 18:11, Denis Magda :
> >
>
osed removals)
> > - we have to keep XXX because ...
> >
> > As a result, will gain lists
> > "to be removed" - no one objected
> > "can be removed" - single objection
> > "should be kept" - multi objections
> >
> > Denis or
; API now, it does not affect SQL.
>
> Best Regards,
> Igor
>
>
> On Thu, Jun 27, 2019 at 7:33 PM Denis Magda wrote:
>
> > Igor, Igniters,
> >
> > I've come across a couple of posts recently where users attempted to
> > preload initial data with a thin client
Alex,
I would do an email survey to hear an opinion of why someone believes a
feature A has to stay. It makes sense to ask about the APIs to be removed
as well as integrations to go out of community support [1] in the same
thread.
Has everyone expressed an opinion? If yes, I can go ahead and
that boosts the loading
for such use cases.
Will there be any benefits from the initial data loading standpoint when
partition-awareness is released or do we need to enhance our thin clients'
protocol? Users use SQL for preloading.
Denis Magda
Ignite developers and users,
I'd like us to consider Ignite modularization as part of Ignite 3.0
timeframe. Presently, Ignite codebase mixes both core capabilities with 3rd
party integrations. It leads to the following:
- Cumbersome and continuously growing codebase with many 3rd-party
used to get a
> count of pages in the reuse list and calculate total used pages by data
> region manually.
>
> ср, 19 июн. 2019 г. в 07:59, Denis Magda :
>
>> + dev list
>>
>> Ignite developers,
>>
>> Seems that the present solution for memory calculation doe
d out from my laptop. I will retry in
> 10
> hours.
>
> Sincerely
> Dmitriy Pavlov
>
>
> вт, 25 июн. 2019 г. в 23:58, Denis Magda :
>
> > In addition to that, how about adding an item for Ignite release policy
> to
> > validate that there are
Dmitriy,
Fully support this requirement. It took us an unreasonable amount of time
to complete post-process steps for this release.
I've involved Python, PHP and Node.JS contributors into our another
discussion. As for other outstanding items, please create tasks in Ignite
JIRA and assign to a
Dmitry, thanks for starting the conversation.
Generally speaking, there are two outstanding items:
- Npm (NodeJS), pip (Python) and composer (PHP) update instructions need
to be added to the release process page. Nuget (.NET) is a good reference
[1]. @Alexey Kosenchuk , @Pavel
The vote is ended with the following results:
+1 (9 total with 7 binding votes)
0 (0)
-1 (0)
A ticket for the decision execution is created and planned for the next
Ignite release: https://issues.apache.org/jira/browse/IGNITE-11942
The voting thread:
Denis Magda created IGNITE-11942:
Summary: IGFS and Hadoop Accelerator Discontinuation
Key: IGNITE-11942
URL: https://issues.apache.org/jira/browse/IGNITE-11942
Project: Ignite
Issue Type
In addition to that, how about adding an item for Ignite release policy to
validate that there are no cryptography related changes?
http://www.apache.org/licenses/exports/
--
Denis Magda
On Tue, Jun 25, 2019 at 1:54 PM Denis Magda wrote:
> Dmitry,
>
> I've updated the ASF website by
79cR8
>
>
> чт, 20 июн. 2019 г. в 00:10, Denis Magda :
>
> > Pavel,
> >
> > I still have no info related to starting version of .NET encryption
> > > support. So I supposed it was 1.5.
> >
> >
> > Could you please help with this last open
SUBMISSION TYPE: Section 742.15
SUBMITTED BY: Denis Magda
SUBMITTED FOR:The Apache Software Foundation
POINT OF CONTACT: Secretary, The Apache Software Foundation
FAX: +1-919-573-9199
MANUFACTURER(S): The Apache Software Foundation, Oracle
Igniters,
Based on our earlier discussion [1], let's formalize our decision and vote
for the following:
- IGFS and In-Memory Hadoop Accelerator components are to be
discontinued and no longer supported by the community
- The existing source code of IGFS and In-Memory Hadoop Accelerator
Pavel,
I still have no info related to starting version of .NET encryption
> support. So I supposed it was 1.5.
Could you please help with this last open item?
Dmitry, thanks for the final summary. I'll contact ASF folks trying to find
the ASF website dev instructions.
--
Denis Ma
+ dev list
Ignite developers,
Seems that the present solution for memory calculation doesn't work (check
the thread):
https://apacheignite.readme.io/v2.5/docs/memory-metrics#section-memory-usage-calculation
<https://apacheignite.readme.io/docs/cache-metrics>
Was it really broken?
--
> >
> >> > href=https://gitbox.apache.org/repos/asf?p=ignite.git
> >> >
> >> >
> >> >
> >> > Oracle
> >> >
> >> > title=Designed to use with built-in Java encryption libraries (JCE)
> >> >
> >> >
companies that exploit on-heap caching a lot.
-
Denis
On Tue, Jun 18, 2019 at 11:42 AM Павлухин Иван wrote:
> Do we still need onheap caches?
>
> вт, 18 июн. 2019 г. в 21:30, Denis Magda :
> >
> > +1
> >
> > Thick (aka. standard clients) provide comprehensive
fs-hadoop).
>
> But if someone could stand up and say he/she wants to do migration from one
> repo to another (option 2), I like it as well.
>
> Sincerely
>
> вт, 18 июн. 2019 г. в 21:05, Denis Magda :
>
> > Igniters,
> >
> > Thanks a lot for sharing your
+1
Thick (aka. standard clients) provide comprehensive compute APIs with
peer-class-loading. That's a huge differentiator for Ignite. Until thin
clients support compute and ML API at the same level as the standard client
does, I would not consider the standard clients' discontinuation. Plus, as
Alex,
I've separated all to-be-removed points from existing
> Ignite 3.0 wishlist [1] to a dedicated block and also added a few more
> things that look right to be dropped.
Could you please share a reference to the wishlist? It's not in your
original email nor anywhere else in the discussion.
hink we can move IGFS to the separate branch (from the
> master one) if someone will decide merge to latest changes from the
> master branch to build Ignite from scratch with IGFS feature.
>
> On Mon, 17 Jun 2019 at 22:42, Denis Magda wrote:
> >
> > >
> > > +1 from me to
Dmitriy,
Thanks for keeping us in the loop. Let us know once the final steps are
over. If any help is needed, call for it.
-
Denis
On Tue, Jun 18, 2019 at 7:07 AM Dmitriy Pavlov wrote:
> Hi Ignite developers,
>
> Thanks to Pavel T. for providing an initial description on how to upload
>
t; > > without sacrificing main Ignite goals then we still should discontinue
> > > it in my mind.
> > >
> > > P.S. Personally I am a fan of UNIX way. I like ideas of a single
> > > responsibility and integrations. And I suppose there are other Ignit
Alex, Igor, thanks for the details. Looks good.
*Pavel Tupitsyn, Aleksandr Shapkin,* could you please help with .NET?
-
Denis
On Thu, Jun 13, 2019 at 2:08 AM Igor Sapego wrote:
> Denis,
>
> C++ thin client and ODBC use OpenSSL to establish secure connection with
> the cluster and do not
Alright, the ticket is ready for contribution:
https://issues.apache.org/jira/browse/IGNITE-11919
--
Denis Magda
On Thu, Jun 13, 2019 at 2:50 PM Denis Magda wrote:
> Those are details and I can't think of a generic and crystal clear message
> that covers them. Plus, don't think we sho
Denis Magda created IGNITE-11919:
Summary: Change message format for incompatible fields' types
changes
Key: IGNITE-11919
URL: https://issues.apache.org/jira/browse/IGNITE-11919
Project: Ignite
type's modification is unsupported, clean {root_path}/marshaller
> directory
> > if the type change is required."*
> >
> >
> > ===
> >
> > Garrett Alley
> > Documentation
> > GridGain Systems
> >
> >
> > On Wed, Jun 12, 2019 at 11:15 AM Denis Magda wrote:
e Software
> Foundation".
>
> вт, 11 июн. 2019 г. в 19:22, Denis Magda :
> >
> > + Sergey
> >
> > -
> > Denis
> >
> >
> > On Tue, Jun 11, 2019 at 9:21 AM Denis Magda wrote:
> >
> > > Sergey,
> > >
> >
Igniters,
Regardless of the fact that Ignite is an open source software, ASF as an
entity based in the U.S. has to comply with certain exporting regulations
[1].
Dmitry Pavlov and I are working on adding Ignite to the table [2] of
projects allowed for export and might need the assistance of some
- I have some ideas to be implemented in
> the future in Ignite 3.0, will share some ideas later.
>
> чт, 6 июн. 2019 г. в 13:29, Denis Magda :
>
> > Hey Igniters,
> >
> > I'd like us to brainstorm how to solve the following usability issue.
> >
> > A us
Igniters,
I'd like us to move on and finish our conversation on the IGFS [1] and
Hadoop Accelerator [2] support.
To my knowledge, there is no single committer who maintains the
integrations; they are no longer tested and, even more, the community
stopped providing the binaries since Ignite 2.6.0
Such OutOfMemory protection will be available in next Ignite releases. In
particular, if a query is about to consume more than X memory than it will
be terminated. Yury, could you please share more details?
-
Denis
On Wed, Jun 12, 2019 at 10:13 AM Shane Duan wrote:
> Thanks, Ilya. Yes, I am
n for 2.7.0.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пн, 10 июн. 2019 г. в 14:30, Dmitriy Pavlov :
> > >
> > > > The vote for a new release candidate is closed, now
> > > >
> > > >
+ Sergey
-
Denis
On Tue, Jun 11, 2019 at 9:21 AM Denis Magda wrote:
> Sergey,
>
> Could you please chime in? I do believe we have special tests to ensure
> the javadoc is not broken. Visually, everything looks good. But I'll
> encourage others to double check.
>
> -
>
Sergey,
Could you please chime in? I do believe we have special tests to ensure the
javadoc is not broken. Visually, everything looks good. But I'll encourage
others to double check.
-
Denis
On Tue, Jun 11, 2019 at 7:04 AM Dmitriy Pavlov wrote:
> Igniters, Ivan,
>
> could you please verify
Hello,
This exception is unrelated to memory usage. The logs report that a wrong
schema is used:
Caused by: org.h2.jdbc.JdbcSQLException: Schema "FEATURE_TILE_CACHE" not
found; SQL statement:
Set schema PUBLIC as part of the JDBC connection string or pass it via the
queries:
Hey Igniters,
I'd like us to brainstorm how to solve the following usability issue.
A user starts developing an app and can change the data model via a
configuration or DDL frequently. However, if there is an incompatible data
model change like a type/field modification Ignite will fail to
+1 (binding)
Nice to have clusters nodes started with ignite.sh in my JVM 11 environment
without any settings.
-
Denis
On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov wrote:
> Dear Community,
>
>
>
> We have uploaded release candidate to
>
Hey Peter, Anton,
Are any of you able to help Nickolay with [1]?
-
Denis
On Mon, Jun 3, 2019 at 6:17 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> We have several issues with Examples suite on TC
>
> 1. IgniteExamplesSparkSelfTestSuite seems configure, bu not runs on suite
> execution.
Nikolay,
Do we really support encryption for pages in RAM? That's what I found in
the docs:
Ignite uses JDK-provided encryption algorithms: "AES/CBC/PKCS5Padding" for
WAL records encryption and *"AES/CBC/NoPadding" for memory page encryption.*
Shouldn't we remove the highlighted from the docs?
th this issue in current build.
>
> On Wed, May 22, 2019 at 4:20 AM Denis Magda wrote:
> >
> > Andrey,
> >
> > I would encourage us to roll this release out and consider this change
> for
> > the next one. We’re free to make the next release as soon as n
fix Java 12 with SSL issue?
>
> On Tue, May 21, 2019 at 10:26 PM Denis Magda wrote:
> >
> > Ignite PMC and committers, please cast your vote. It's time to roll the
> release out.
> >
> > --
> > Denis Magda
> >
> >
> > -- Forwarded messa
Ignite PMC and committers, please cast your vote. It's time to roll the
release out.
--
Denis Magda
-- Forwarded message -
From: Denis A. Magda
Date: Tue, May 21, 2019 at 7:26 AM
Subject: Re: [VOTE] Accept Apache Ignite 2.7.5-rc3
To:
+ 1 (binding)
Denis
On 2019/05/17 13:49
Yeap,
This looks like a candidate for the change.
Peter, Anton, is there a quick way to prepare a list of such dependencies
where "http" is to be replaced with "https"?
--
Denis Magda
On Tue, May 21, 2019 at 7:17 AM Ilya Kasnacheev
wrote:
> Hello!
>
> I think we
Hello Vladimir and welcome aboard!
Please get to know the process and share your JIRA id once you're ready to
take on a task:
https://ignite.apache.org/community/contribute.html#contribute
-
Denis
On Tue, May 21, 2019 at 8:46 AM Vladimir Malinovskiy <
vmalinovs...@gridgain.com> wrote:
>
Igniters,
Could anybody confirm we don’t have any issues with that?
Denis
-- Forwarded message --
From: *Apache Security Team*
Date: Tuesday, May 21, 2019
Subject: PRIORITY Action required: Security review for non-https dependency
urls
To: Apache Security Team
ASF Security
an Ignite Cluster in Kubernetes and can't
> move
> forward until I can solve this problem. Is there anyone who's used
> DataStreamers to do heavy write loads in a k8s environment who has any
> insight into what would be causing this?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
--
Denis Magda
Hello Balazs,
Thanks for reaching the community out. Certainly, we'll appreciate if you
contribute your changes back. Could you please create a ticket in JIRA and
open the pull-request? Someone from the community will review and accept
your improvements.
Just in case, you can find more on
Alright, it took me longer to get back and look into it. Sorry for a delay.
Overall, folks, the things look creepy, seriously. I see 3 primary issues
ranged by priority.
1st, until the failure handler gets smart enough how to deal with
SYSTEM_WORKER_BLOCKED/SYSTEM_CRITICAL_OPERATION_TIMEOUT
Well deserved, Vyacheslav! Thanks for hardening Service Grid pushing it to
a completely next level!
-
Denis
On Thu, Apr 11, 2019 at 7:00 AM Dmitriy Pavlov wrote:
> Dear Ignite Developers,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Daradur to become a
Done, you're in. Feel free to take over open tickets/issues.
-
Denis
On Tue, Apr 9, 2019 at 1:33 PM wrote:
> Sure.
>
> Username: olemogyl
> Email is same: olek...@reseguiden.se
>
> -
> Oleksii
>
> -Original Message-
> From: Denis Magda
> Sen
Hello Oleksii,
Sure, please tell your JIRA ID.
-
Denis
On Tue, Apr 9, 2019 at 10:18 AM Oleksii Mohylin
wrote:
> Hello
>
>
>
> I would like to become a contributor of Apache Ignite project. I'm working
> on an OSGI application project with cache implementation by Apache Ignite
> and have
I would support this idea of having integrations in separate Github
repositories. Ignite is already overwhelmed with a bunch of integrations
which complicates testing, release procedures, maintenance. Think that we,
as the community, should revisit the current project structure and move
even key
Hello Pascal,
We'll get you added to the 3rd parties list it's not a big deal. It will be
great if you have and can share any production deployments of the plugin,
just to increase confidence in the module.
However, how is your feature different from the default Ignite-compression
to be released
+1, that's a valid use case of having both native persistence and
CacheStore enabled. Users are aware of limitations such as no guaranteed
consistency across two stores.
-
Denis
On Tue, Apr 2, 2019 at 8:26 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Yes, we do support persistence + cache store.
>
rformance-tips
> is
> > outdated as well.
> > In particular,
> >
> >
> https://apacheignite-net.readme.io/docs/performance-tips#section-tune-cache-start-size
> > does not make sense as of Apache Ignite 2.x.
> > I added a comment to the mentioned jira ticket
Hi,
How does the JVM error look like?
Apart from that, Andrey, Igniters, the failure handler fired off but I have
no glue from the shared logs what happened or how it is connected to the
Java heap issues. Should I expect to see anything from the logs not added
to the thread?
--
Denis Magda
; Now under Java 12 Ignite suggests to set startup parameters, but even
> with
> > correct parameters, it fails and says please set parameters. Totally
> > unclear for end-user.
> >
> > I've reopened https://issues.apache.org/jira/browse/IGNITE-11600
> >
> > Since
ution for this.
>
> So these 2 fixes are last candidates to come to scope. WDYT?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 28 мар. 2019 г. в 18:10, Denis Magda :
>
> > Yes, the Python example's fix makes sense - that's a usability issue and
> > doesn't affect the co
Yes, the Python example's fix makes sense - that's a usability issue and
doesn't affect the core components.
In general, I would suggest us to do a code freeze and push other changes
to another release. We can't include everything.
-
Denis
On Thu, Mar 28, 2019 at 3:01 AM Ilya Kasnacheev
I think that Ignite can be placed in a list of NewSQL databases even though
that's not our strongest use case. Ignite is unique as the whole:
- Storage (memory + disk - 3rd party or native)
- Key/value for simple querying + SQL for advanced calls
- Collocated processing (compute grid,
t; > > > > >
> > > > > > If I would be a user of the product that just shutdown with poor
> log
> > > I
> > > > > > would throw this product away.
> > > > > > Do we want it for Ignite?
> > > > > >
> > > >
Nikolay,
Thanks for kicking off this discussion. Surprisingly, planned to start a
similar one today and incidentally came across this thread.
Agree that the failure handler should be off by default or the default
settings have to be revisited. That's true that people are complaining of
nodes
I think that we as the community should consider discontinuing the
full-text search support. It goes with many limitations and not widely
used. The market is flooded with many products designed for full-text
search scenarios.
-
Denis
On Wed, Mar 20, 2019 at 3:44 AM Dmitriy Pavlov wrote:
> +1
Hi, is there any reason why you can't use ElastiSearch or similar products
designed for full-text search use cases?
-
Denis
On Wed, Mar 20, 2019 at 2:51 AM Andrey Mashenkov
wrote:
> Hi,
>
> No, due to H2 limitation.
> H2 allow user define Function as a table, but seems an additional support
>
> > > "You told me you fixed this at 2.8, ... lair", that what I expect.
> > > >
> > > > 2) You'll have to update 1000+ issues to have 2.9 as the fixed
> version.
> > > > This will look odd to contributors.
> > > >
> > > >
t;
> >> > - *was hard to start the code samples (same issue as with cmd).*
> >> > - *The step above have to be repeated for every single sample*
> >>
> >> For this issue, do we have any solution at all? I'm afraid you will
> still
> >&
Igniters,
How about releasing Ignite 2.8 from the master - creating the release
branch on Monday-Tuesday, as fast as we can? Don't want us to delay with
Java 11 improvements, they are really helpful from the usability standpoint.
After this release, let's introduce a practice of maintenance
701 - 800 of 3093 matches
Mail list logo
