Dear Igniters
Unfortunately, vote should be cancelled, because there is an absence of
LICENSE and NOTICE in source package and NOTICE in binary packages.
Issue created https://issues.apache.org/jira/browse/IGNITE-14564
New vote will appear soon.
--
Sincerely yours, Ivan Daschinskiy
Ivan Daschinsky created IGNITE-14564:
Summary: Add LICENSE and NOTICE file to all packages
Key: IGNITE-14564
URL: https://issues.apache.org/jira/browse/IGNITE-14564
Project: Ignite
Issue
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Control Utility
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility?branch=%3Cdefault%3E
No changes in the build
Andrey Mashenkov created IGNITE-14563:
-
Summary: Fix javadoc in Runner module.
Key: IGNITE-14563
URL: https://issues.apache.org/jira/browse/IGNITE-14563
Project: Ignite
Issue Type: Bug
Andrey Mashenkov created IGNITE-14562:
-
Summary: Fix javadoc in Network module.
Key: IGNITE-14562
URL: https://issues.apache.org/jira/browse/IGNITE-14562
Project: Ignite
Issue Type: Bug
Andrey Mashenkov created IGNITE-14561:
-
Summary: Fix javadoc in Configuration module.
Key: IGNITE-14561
URL: https://issues.apache.org/jira/browse/IGNITE-14561
Project: Ignite
Issue
Andrey Mashenkov created IGNITE-14560:
-
Summary: Fix javadoc in CLI module.
Key: IGNITE-14560
URL: https://issues.apache.org/jira/browse/IGNITE-14560
Project: Ignite
Issue Type: Bug
According to ASF release policy [1] non-PMC committers can sign artifacts:
> all artifacts placed in their directory must be signed by a committer,
> preferably by a PMC member.
[1] https://www.apache.org/legal/release-policy.html
чт, 15 апр. 2021 г. в 23:05, Dmitriy Pavlov :
>
> My best guess
My best guess that since PMCs have a binding vote in voting in release, a
PMC member should sign binaries as well. And I suppose that in the past
only PMC members were signing the release.
Meanwhile, https://infra.apache.org/release-signing.html does not contain
any mention of PMC role and only
Andrey Mashenkov created IGNITE-14559:
-
Summary: Fix javadoc in schema and table modules
Key: IGNITE-14559
URL: https://issues.apache.org/jira/browse/IGNITE-14559
Project: Ignite
Issue
I'm sorry, but is it OK, that artifacts are signed with signature of
non-PMC?
чт, 15 апр. 2021 г. в 19:26, Nikita Amelchev :
> Dear Ignite Community,
>
> I have uploaded a release candidate of the following extension modules:
>
> performance-statistics-ext
> spring-data-ext
> spring-data-2.0-ext
Folks,
I've briefly checked the total amount of the max length violations:
120 line length - 5540 violations
130 line length - 1891 violations
140 line length - 895 violations
150 line length - 478 violations
I think the 140 max line length might be the best option for us.
On Thu, 15 Apr 2021
I'll keep the common pool then, thank you.
Public pool is the "work-horse of the Compute Grid" [1], so it does not
seem to fit here at all.
[1]
https://ignite.apache.org/docs/latest/perf-and-troubleshooting/thread-pools-tuning#public-pool
On Thu, Apr 15, 2021 at 2:18 PM Stanislav Lukyanov
Dear Igniters!
Release candidate binaries are at least uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.4.0-rc0
If you follow the link above, you will find source package (*.tar.gz and
*.zip)
and binary packages (wheels) for windows
Andrey N. Gura created IGNITE-14558:
---
Summary: Add information about javadoc validation and generation
commands to DEVNOTES.md
Key: IGNITE-14558
URL: https://issues.apache.org/jira/browse/IGNITE-14558
Hello!
I have added you to the contributor role, now you can assign issues to
yourself.
Please familiarize with
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Regards,
--
Ilya Kasnacheev
чт, 15 апр. 2021 г. в 18:30, Eduard Rakhmankulov :
> Hello Ignite Community!
>
>
Hi all,
I created a pull request that creates new method on IgniteCache that returns
the current TTL of a record. I’m not entirely clear who I should tag for a
review, so I’m posting here.
> https://issues.apache.org/jira/browse/IGNITE-7641
>
Dear Ignite Community,
I have uploaded a release candidate of the following extension modules:
performance-statistics-ext
spring-data-ext
spring-data-2.0-ext
spring-data-2.2-ext
spring-data-commons
spring-tx-ext
The release candidate of the performance-statistics-ext extension:
Congrats, Ivan!
вт, 13 апр. 2021 г. в 20:02, Ivan Daschinsky :
> Guys, many thanks to all of you!
>
> вт, 13 апр. 2021 г. в 13:19, Alex Plehanov :
>
> > Ivan, congratulations!
> >
> >
> > вт, 13 апр. 2021 г. в 13:02, Andrey Mashenkov <
> andrey.mashen...@gmail.com
> > >:
> >
> > > Ivan,
Hello Ignite Community!
My name is Eduard. I want to contribute to Apache Ignite, my JIRA username
*erixon*.
Thanks!
--
Best regards, Eduard.
Hi Alexey,
I like the idea.
1.
> TBL-0001 is a *string representation* of the error. It is built from 2
> byte scope id (mapped to name TBL) and 2 byte number (0001). Both
> internally packed in int. No any kind of parsing will be necessary to read
> scope/category.
I think Alexey mean if it
Andrey Mashenkov created IGNITE-14557:
-
Summary: Imrove row layout.
Key: IGNITE-14557
URL: https://issues.apache.org/jira/browse/IGNITE-14557
Project: Ignite
Issue Type: Improvement
Andrey Mashenkov created IGNITE-14556:
-
Summary: Add Tuple validation.
Key: IGNITE-14556
URL: https://issues.apache.org/jira/browse/IGNITE-14556
Project: Ignite
Issue Type: Improvement
Konstantin Orlov created IGNITE-14555:
-
Summary: Calcite engine. Create table from query result
Key: IGNITE-14555
URL: https://issues.apache.org/jira/browse/IGNITE-14555
Project: Ignite
чт, 15 апр. 2021 г. в 14:26, Ilya Kasnacheev :
> Hello!
>
> > All public methods throw only unchecked
> org.apache.ignite.lang.IgniteException containing aforementioned fields.
> > Each public method must have a section in the javadoc with a list of all
> possible error codes for this method.
>
>
Konstantin Orlov created IGNITE-14554:
-
Summary: Calcite engine. Provide ability to parse huge numeric
literals
Key: IGNITE-14554
URL: https://issues.apache.org/jira/browse/IGNITE-14554
Project:
Konstantin Orlov created IGNITE-14553:
-
Summary: Calcite engine. Duplicated result on insert
Key: IGNITE-14553
URL: https://issues.apache.org/jira/browse/IGNITE-14553
Project: Ignite
Konstantin Orlov created IGNITE-14552:
-
Summary: Calcite engine. Alias for function CHARACTER_LENGTH
Key: IGNITE-14552
URL: https://issues.apache.org/jira/browse/IGNITE-14552
Project: Ignite
Dheeraj Saini created IGNITE-14551:
--
Summary: NodeJS Thin Client - Error: Invalid response id: in
ClientSocket.js
Key: IGNITE-14551
URL: https://issues.apache.org/jira/browse/IGNITE-14551
Project:
Dheeraj Saini created IGNITE-14550:
--
Summary: NodeJS Thin Client: Invalid response id: in
ClientSocket.js
Key: IGNITE-14550
URL: https://issues.apache.org/jira/browse/IGNITE-14550
Project: Ignite
Hello Ignite Community!
My name is Eduard. I want to contribute to Apache Ignite, my JIRA username
*erixon*.
Thanks!
--
Best regards, Eduard.
But super long lines are a real problem while merging. It is super
inconvenient.
120 chars is a good compromise.
чт, 15 апр. 2021 г. в 14:39, Zhenya Stanilovsky :
>
> Python is not so verbose as java )
> +1 for 140
>
> >Hi!
> >Personally, I suppose that 120 chars per line is OK. Moreover, many
>
Python is not so verbose as java )
+1 for 140
>Hi!
>Personally, I suppose that 120 chars per line is OK. Moreover, many
>codestyles suggests less chars per line.
>For example PEP8 recommends 80 (but we use 120 in pyignite and flake8
>codestyle checks it). Google java codestyle insists on 100.
>
Konstantin Orlov created IGNITE-14549:
-
Summary: Calcite. ORDER BY column not from SELECT LIST
Key: IGNITE-14549
URL: https://issues.apache.org/jira/browse/IGNITE-14549
Project: Ignite
> I think that we should keep the "soft" 120 chars limit in CC, but introduce a
> hard limit of 140 in checkstyle
Works for me.
> 15 апр. 2021 г., в 14:21, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Let me clarify: I think that we should keep the "soft" 120 chars limit in
> CC, but
Hello!
> All public methods throw only unchecked
org.apache.ignite.lang.IgniteException containing aforementioned fields.
> Each public method must have a section in the javadoc with a list of all
possible error codes for this method.
I don't think this is feasible at all.
Imagine javadoc for
Hello!
Let me clarify: I think that we should keep the "soft" 120 chars limit in
CC, but introduce a hard limit of 140 in checkstyle, since it should not be
too much work or annoy too much.
In the future we may wish to harmonize the two.
Regards,
--
Ilya Kasnacheev
чт, 15 апр. 2021 г. в
Giving this another thought - I'm kinda torn on this myself now, as I like you
argument that a chain of multiple (GG and not GG) continuations should execute
in the same pool.
This would probably be easier to understand for a beginning or intermediate
Ignite user, which is the majority.
Anyway,
Hi,
Personally I do not like an idea of excluding notifications for
created JIRA tickets from dev-list. I used such notifications in
following cases:
* React to tickets created by Ignite users in my area of responsibility.
* Redirect questions created as JIRA tickets to user-list.
* Trash spam
Taras Ledkov created IGNITE-14548:
-
Summary: BinaryThreadLocalContext must be cleaned when client is
closed
Key: IGNITE-14548
URL: https://issues.apache.org/jira/browse/IGNITE-14548
Project: Ignite
Hi Alexei,
> Each public method *must *have a section in the javadoc with a list of
all possible error codes for this method.
I consider it is redundant, because any public exception can be thrown from
public API.
If it not happens today, it may change tomorrow: one will be removed,
another one
Hi!
Personally, I suppose that 120 chars per line is OK. Moreover, many
codestyles suggests less chars per line.
For example PEP8 recommends 80 (but we use 120 in pyignite and flake8
codestyle checks it). Google java codestyle insists on 100.
More than 120 chars is too long as for me and is not
Hello, Ilya.
Thanks for the feedback.
140 characters is fine for me.
> 15 апр. 2021 г., в 12:25, Ilya Kasnacheev
> написал(а):
>
> Hello!
>
> Please find attached the distribution of line lengths in the project, in the
> form of (count, line length).
>
> I think that we can enforce a hard
Hello!
Please find attached the distribution of line lengths in the project, in
the form of (count, line length).
I think that we can enforce a hard limit of 140 chars per line. I think
that having longer lines is excessive and does not benefit readability.
Having a limit of 150 or 180 does
Hello, Igniters.
Right now, we have a code style rule [1] - the line should fit in 120
characters.
But, this rule violated in many and many places through code.
I have a plan to add a check style rule to force maximum line length.
For me, personally, 120 characters a bit old-fashioned
Hi Pavel,
I'd prefer public pool.
Thanks,
Stan
> On 12 Apr 2021, at 20:17, Pavel Tupitsyn wrote:
>
> Stan,
>
> Sorry for the late reply (had a vacation).
>
>> In my ideal world, the users don't configure thread pools, they just have
> safe default behavior (async execution)
>> and a way to
46 matches
Mail list logo
