Alexey Goncharuk created IGNITE-12802:
-
Summary: Move checkpoint state fields to CheckpointProgress
Key: IGNITE-12802
URL: https://issues.apache.org/jira/browse/IGNITE-12802
Project: Ignite
Hi Artem,
*apacheignite-fs,apacheignite-mix,apacheignite-tools*
these three parts, is it missing?confirm again?
thank you very much!
在 2020/3/19 下午3:41, Artem Budnikov 写道:
Hi,
Please find the archive with the latest docs attached.
-Artem
On Thu, Mar 19, 2020 at 6:32 AM 18624049226 <1862404
Sure, done!
On Thu, Mar 19, 2020 at 12:52 AM Guru Stron
wrote:
> Hi Pavel,
>
> Thank you for the review!
>
> Can you please also look at
> https://issues.apache.org/jira/browse/IGNITE-9017?
>
> On Mon, 17 Feb 2020 at 11:13, Pavel Tupitsyn wrote:
>
> > Hello Guru,
> >
> > I'll have a look today,
Hello Sergey,
I have checked and merged the pull-request. Thank you for your efforts!
Thanks,
S.
ср, 18 мар. 2020 г. в 16:31, Sergey Chernolyas :
> Hi igniters!
>
> I ask to review PR for issue
> https://issues.apache.org/jira/browse/IGNITE-12799 . My PR is approved by
> TeamCity and ready for
Hi,
I didn't include those sections because they had not changed since the last
version (2.7).
-Artem
On Thu, Mar 19, 2020 at 1:01 PM 18624049226 <18624049...@163.com> wrote:
> Hi Artem,
>
> *apacheignite-fs,apacheignite-mix,apacheignite-tools*
>
> these three parts, is it missing?confirm again
Sergey Antonov created IGNITE-12803:
---
Summary: Investigate exception message on too many open files in
different OS.
Key: IGNITE-12803
URL: https://issues.apache.org/jira/browse/IGNITE-12803
Project
Taras Ledkov created IGNITE-12804:
-
Summary: SQL: ConnectionManager refactoring
Key: IGNITE-12804
URL: https://issues.apache.org/jira/browse/IGNITE-12804
Project: Ignite
Issue Type: Task
Hello!
My fault, fixed already.
Regards,
--
Ilya Kasnacheev
вт, 17 мар. 2020 г. в 01:19, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that you were
> a volun
Hello!
I recommend filing issues and trying to tackle them yourself, since you
seem to be a rare active user of ignitevisorcmd.
Then again, maybe we should move more functionality to control.sh.
Regards,
--
Ilya Kasnacheev
вт, 17 мар. 2020 г. в 10:13, Nikolai Kulagin :
> Hello, Igniters!
>
>
Folks,
I'd like to add ticket IGNITE-12774 Transaction hangs after too many open
files NIO exception [1] to ignite-2.8.1 scope.
[1] https://issues.apache.org/jira/browse/IGNITE-12774
ср, 18 мар. 2020 г. в 16:53, Maxim Muzafarov :
> Folks,
>
> Can we add ignite-2.8.1 [2] branch under TC.Bot prot
Sarunas Valaskevicius created IGNITE-12805:
--
Summary: Node fails to restart
Key: IGNITE-12805
URL: https://issues.apache.org/jira/browse/IGNITE-12805
Project: Ignite
Issue Type: Bug
Igniters,
please, notice that right commit message format the following:
IGNITE- my message
There is no colon (:) after . There is no hyphen (-) between
and message. There is only one space.
How to contribute doc [1] doesn't state this as requirement and just
contains some examples
Hi Artem,
https://apacheignite.readme.io/docs/partition-map-exchange-27
This page has no corresponding menu link, is it correct?
在 2020/3/17 上午12:47, Denis Magda 写道:
Artem,
I'll create a ticket for the IGFS docs replacement once we publish the new
website that we'll have all the references ne
Igniters,
As long as 2.8.1 is inevitable and we already keep adding critical issues
to the working queue, let's settle on the release time frames and decide
who will be a release manager. This is the time proposed by Maxim and,
personally, I concur with such a schedule:
- Scope Freeze: April 1
I want to be a release manager.
> 19 марта 2020 г., в 17:52, Denis Magda написал(а):
>
> Igniters,
>
> As long as 2.8.1 is inevitable and we already keep adding critical issues
> to the working queue, let's settle on the release time frames and decide
> who will be a release manager. This is t
Correct. This page shouldn't be published.
-Artem
On Thu, Mar 19, 2020 at 5:35 PM 18624049226 <18624049...@163.com> wrote:
> Hi Artem,
>
> https://apacheignite.readme.io/docs/partition-map-exchange-27
>
> This page has no corresponding menu link, is it correct?
>
> 在 2020/3/17 上午12:47, Denis Mag
Igniters,
I've modified our release process introducing this step that ensures
documentation readiness before a vote can be started:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1EnsureDocumentationReadinessandAccouncementBlogPostActivity
Thanks to everyone
Dear Ignite community,
Many of us want to see where Ignite is heading and ask for some sort of a
2020 course/plan/roadmap and a predictable schedule of major releases.
Also, there are intentions to enhance some internal processes and
collaboration approaches.
Let's start moving in that direction
Andrey N. Gura created IGNITE-12806:
---
Summary: Incorret usage of Class.isAssignableFrom in
SystemViewLocal and SystemViewMBean classes
Key: IGNITE-12806
URL: https://issues.apache.org/jira/browse/IGNITE-12806
Alexey Kukushkin created IGNITE-12807:
-
Summary: Key and Value fields with same name and SQL DML
Key: IGNITE-12807
URL: https://issues.apache.org/jira/browse/IGNITE-12807
Project: Ignite
My top list of changes is as follows:
- Feature: New lightweight Apache Ignite website with advanced search
engine optimizations and updated technical content. Why? Much better
discoverability of Ignite via search engines like Google to let many more
application developers learn about
Mikhail Cherkasov created IGNITE-12808:
--
Summary: Allow create tables for existing caches
Key: IGNITE-12808
URL: https://issues.apache.org/jira/browse/IGNITE-12808
Project: Ignite
Issue
Ok, lets keep in mind and remind during PRs to each other
чт, 19 мар. 2020 г., 17:32 Andrey Gura :
> Igniters,
>
> please, notice that right commit message format the following:
>
> IGNITE- my message
>
> There is no colon (:) after . There is no hyphen (-) between
> and message. The
Could we add features to the scope of this release? Or we will fix known
bugs only?
чт, 19 мар. 2020 г., 17:59 Nikolay Izhikov :
> I want to be a release manager.
>
>
> > 19 марта 2020 г., в 17:52, Denis Magda написал(а):
> >
> > Igniters,
> >
> > As long as 2.8.1 is inevitable and we already ke
The Best way to require draft documentation with the proposed PR:) as a
part of TC check
чт, 19 мар. 2020 г., 21:06 Denis Magda :
> Igniters,
>
> I've modified our release process introducing this step that ensures
> documentation readiness before a vote can be started:
>
> https://cwiki.apache.o
Andrey,
Personally I would consider a proper format (where colon is optional):
IGNITE-[:] my message
Is there any any harm from a "colon" in a commit message? While we are
working in open source simplification is very important. And I suggest
to not bother contributors and committers with un
Ivan,
What could be simpler than exactly one format without any optional things? :)
I don't understand why examples of other project should be considered
at all. Most of commit messages in Apache Ignite have described format
without additional symbols. It is absolutely okay to require to follow
s
Andrey,
I am working with about 4 projects. And I do not want to bother myself
whether colon in a commit message is required or prohibited. And I
believe that we should encourage to contribute not only those whose
full-time job is contribution to Ignite. So, a contribution process
should be as sim
I agree with Ivan. All contribution rules should be reasonable and should
*add value*.
For example, a requirement to include the ticket number is a great idea as
it creates a clear link between a commit and a JIRA ticket. This helps to
track the history, simplifies searches, etc.
But is it really
Evgenii Zhuravlev created IGNITE-12809:
--
Summary: Python client returns fields in wrong order since the 2
row when fields_count>10
Key: IGNITE-12809
URL: https://issues.apache.org/jira/browse/IGNITE-12809
Hi Denis,
Thank you for sharing the list of top changes. The list looks good.
I wanted to share that efforts regarding IEP-36 is already underway and
there are also open PRs under review and working through review feedback.
One of the area that we are focussing is first we will merge changes in
i
31 matches
Mail list logo
