Hi Roman,
I suppose that we can resolve the ticket with 2.8 fix version if you
have no objections.
чт, 26 дек. 2019 г. в 10:52, :
>
> Hi Ivan,
> Does it mean that the problem is gone and I should close the JIRA
> IGNITE-12445 ?
>
>
> -Original Message-
> From: Ivan Pavlukhin
> Sent: Mon
Denis Chudov created IGNITE-12496:
-
Summary: Index deletion blocks checkpoint for all of its duration,
which can cause "Critical system error: system critical thread blocked"
Key: IGNITE-12496
URL: https://issues.
Ilya,
Indeed the matters can be improved.
Is not it useful to mark what region is default? Also some doubts
about internal memory regions. It is not obvious that we should print
an information about them for every user. If we need to have some
determinism about offheap memory than I can think abo
Kirill Tkalenko created IGNITE-12497:
Summary: PartitionsEvictManager should log all partitions which
will be evicted
Key: IGNITE-12497
URL: https://issues.apache.org/jira/browse/IGNITE-12497
Proj
Ivan Pavlukhin created IGNITE-12498:
---
Summary: Calcite integration. Create a test suite on TC.
Key: IGNITE-12498
URL: https://issues.apache.org/jira/browse/IGNITE-12498
Project: Ignite
Issu
Folks,
Do not we have plans to discontinue Visor? If so, it might be better
to add a desired functionality to another management API?
вт, 24 дек. 2019 г. в 08:02, Denis Magda :
>
> Forwarding to the dev list. How exactly would you like to expand Visor CMD?
> Please describe your idea and we can m
Hello!
I think that control.sh should be extended instead of Visor CLI, it is a
tool which sees a lot more activity currently.
Regards,
--
Ilya Kasnacheev
чт, 26 дек. 2019 г. в 12:45, Ivan Pavlukhin :
> Folks,
>
> Do not we have plans to discontinue Visor? If so, it might be better
> to add a
Hello!
Okay, I will mark default region.
We already log information about internal memory regions, so removing it
will require a lot of consensus. However, I can clearly map them as system
regions when printing.
Regards,
--
Ilya Kasnacheev
чт, 26 дек. 2019 г. в 12:10, Ivan Pavlukhin :
> Ilya
Anton,
Thank you for your efforts! And sorry for a late reply.
I am a little bit familiar with tx recovery. I personally like the
idea of removing such "magic" logic from the code. I think a proper
way is either justify and sustain (tests, documentation) some behavior
or get rid of it.
Regarding
Ivan Bessonov created IGNITE-12499:
--
Summary: Node took a long time to start after kill
Key: IGNITE-12499
URL: https://issues.apache.org/jira/browse/IGNITE-12499
Project: Ignite
Issue Type:
Denis Garus created IGNITE-12500:
Summary: IgniteProxy should be injected into non-system types only.
Key: IGNITE-12500
URL: https://issues.apache.org/jira/browse/IGNITE-12500
Project: Ignite
Amelchev Nikita created IGNITE-12501:
Summary: The
AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky.
Key: IGNITE-12501
URL: https://issues.apache.org/jira/browse/IGNITE-12501
Ivan,
The "magic numbers" are always the "magic numbers" :)
We must get rid of them to see problems covered by them.
>> Was there any
>> performance measurements for such multiple left nodes cases?
Since this fix made to speedup pme-free switch which prohibits the merges,
the answer is "no".
BTW
Hello!
I propose to add the following ticket to the scope:
https://issues.apache.org/jira/browse/IGNITE-12259 (3 commits, be careful
with release version)
Adding tickets to scope surely seems crazy now, but I will provide the
following considerations:
* This is Spring Data 2.2 integration, which
Ilya,
I agree with you that there is no risk and spring-data-2.2 can be
safely cherry-picked to the ignite-2.8 branch. I'm OK with it. Will
you do such merge or I should do it by myself?
As for the second part of your email, you are proposing to bump up a
minor dependencies version (no API chan
Personally, I see no reason for deprecating Visor CLI and moving all its
capabilities to the control.sh script. It's better to merge the script's
capabilities into Visor CLI and rework the connectivity/communication
protocol of the latter. If to recall the reason for the control.sh creation
it was
+1 to keep visor cmd and fix it’s issues.
> 26 дек. 2019 г., в 19:23, Denis Magda написал(а):
>
> Personally, I see no reason for deprecating Visor CLI and moving all its
> capabilities to the control.sh script. It's better to merge the script's
> capabilities into Visor CLI and rework the conne
A huge +1 for adding Spring Data related fixes/improvements. Ilya is right
that Spring Data related questions sparked last time due to missing support
of 2.2 version.
Ilya, could you elaborate on what you mean under "bumping the versions"? Do
you suggest performing a straightforward upgrade of "ig
Ivan,
There is no way to turn this off. Just check with the Nabble interface.
Anyway, if anybody unregistered sends a message via Nabble it will arrive
to a dev/user list moderator for approval. Dmitry P, I and some other folks
receive those emails.
-
Denis
On Tue, Dec 24, 2019 at 10:15 AM Ivan
Let me loop in the Ignite dev list as long as I've not heard about such an
issue. Personally, don't see any misconfiguration in your Ignite config.
-
Denis
On Thu, Dec 26, 2019 at 10:17 AM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
> I used cache.remove(key) method to delete an entr
Hello
I have been able to resolve the build issue in teamcity and was able to
pass the build failures.
https://ci.ignite.apache.org/viewLog.html?buildId=4883394&buildTypeId=IgniteExtensions_Build
The issue that was causing failure was that I had put ignite.zip as
artifact dependency and it was d
Hi Emmanouil,
I have been able to resolve the build failures for missing modules.
https://ci.ignite.apache.org/viewLog.html?buildId=4883394&buildTypeId=IgniteExtensions_Build
Will you please take the latest changes from my PR and run the build for
your PR.
https://github.com/apache/ignite-exten
Hello,
Please find the PR link below.
https://github.com/apache/ignite-extensions/pull/1/files
Regards,
Saikat
On Thu, Dec 26, 2019 at 1:43 PM Saikat Maitra
wrote:
> Hello
>
> I have been able to resolve the build issue in teamcity and was able to
> pass the build failures.
>
>
> https://ci.i
Hello Denis,
Thank you for publishing and modifying the Contributions page. Many time
folks have approached me over email, linkedin and offline about how they
can contribute to Apache projects and I share this link and about my
experience. I will continue to share this link going forward.
I am th
Hello Saikat,
Thanks for checking the page and suggesting the improvement. I'll add the
link to the page.
Also, I'm thinking to go for another round of changes by listing other
forms of contributions such as helping to answer users' questions,
reviewing changes or updating documentation. Like the
Igor S., Roman and others who involved in Calcite prototyping,
Is it true that Calcite can parse MySQL, Oracle, ANSI-99 and other dialects
as suggested by this page?
https://calcite.apache.org/apidocs/org/apache/calcite/sql/validate/SqlConformanceEnum.html
Do I need to select a dialect globally o
Hi, All!
I think that the best way is to do the following:
1. Move controls.sh to separate module (this will allow us to use any third
party libs for argument parsing, interactive mode, and other stuff).
2. Move all colde from visorcmd to controls.sh
3. Drop visorcmd
On Thu, Dec 26, 2019 at 11:2
+1 here.
>Hi, All!
>
>I think that the best way is to do the following:
>1. Move controls.sh to separate module (this will allow us to use any third
>party libs for argument parsing, interactive mode, and other stuff).
>2. Move all colde from visorcmd to controls.sh
>3. Drop visorcmd
>
>On Thu,
> 2. Move all colde from visorcmd to controls.sh
> 3. Drop visorcm
Hello, Zhenya, Alexey, can you, please, clarify, why you suggest dropping of
visorcmd?
What are the problems of the visorcmd that can’t be solved?
> 27 дек. 2019 г., в 09:26, Zhenya Stanilovsky
> написал(а):
>
>
> +1 here.
Hello!
I have committed ignite-spring-data_2.2 to ignite-2.8.
By bumping versisons I mean the following:
1.7.*7*
1.6.*4*
1.1.7.*2*
2.6.*5*
2.3.*0*
1.13.*14*.RELEASE
4.3.*18*.RELEASE
2.0.*9*.RELEASE
5.0.*8*.RELEASE
All thes
Ilya Kasnacheev created IGNITE-12502:
Summary: Document ignite-spring-data_2.2 module
Key: IGNITE-12502
URL: https://issues.apache.org/jira/browse/IGNITE-12502
Project: Ignite
Issue Type:
31 matches
Mail list logo
