Hello, Didar!
I've added you to the "contributors" role. Now you can assign tickets
to yourself.
чт, 10 апр. 2025 г. в 22:39, Didar Shayarov :
>
> Hello Ignite!
>
> Finally, I’ve got ASF JIRA account with username ‘superdidar’
>
> Please, help me to start contributing with this email and username
+1
Built from sources. Checked several queries on the Calcite-based SQL engine.
вс, 9 февр. 2025 г. в 21:05, Nikita Amelchev :
>
> Dear Community,
>
> The release candidate is ready.
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.17.0-rc2
> https://dist
+1
Built from sources. Checked several queries on the Calcite-based SQL engine.
Found that one more dependency is missing in ignite-calcite module:
commons-lang3. It affects 5 built-in functions: EXTRACTVALUE, EXTRACT,
XMLTRANSFORM, COMPRESS, TRANSLATE. The same problem was in previous
releases an
Hello, Ravil
I've added you to the contributors list. Now you can assign tickets to yourself.
ср, 27 нояб. 2024 г. в 19:47, Равиль Закиров :
>
> Hello, Everyone!
> My name is Ravil Zakirov. I want to contribute to Ignite. I would like to
> start from IGNITE-23794. Please, help me to start contri
+1
вт, 16 июл. 2024 г. в 14:14, Вячеслав Коптилин :
>
> +1
>
> Thanks,
> S.
>
> вт, 16 июл. 2024 г. в 09:46, Maksim Timonin :
>
> > Hi Igniters,
> >
> > I'd like to start a voting process about moving Ignite 2.x sources to
> > JDK11. Discussion of the proposal is here [1].
> >
> > The plan is as f
Andrey Novikov, Nusrat Shakarov,
Guys, we are still supporting java 8, this means that the project
should be compiled without errors on jdk 8 and jdk 11 (not only on jdk
17). You've already broken the compilation for jdk 8/jdk 11 twice
during the same activity ([1], [2]).
I've mentioned you in ti
else (e.g. Compute).
> > Full stack trace should be present in the server logs, or sent back to the
> > client when sendServerExceptionStackTraceToClient is enabled, so we have
> > all the means to find the root cause, right?
> >
> > On Tue, May 7, 2024 at 9:32 PM Al
general
> client/server exceptions.
>
> I don't think we do this anywhere else (e.g. Compute).
> Full stack trace should be present in the server logs, or sent back to the
> client when sendServerExceptionStackTraceToClient is enabled, so we have
> all the means to find the
Hi Igniters!
I've prepared a proposal about implementation of invoke/invokeAll
cache operations for thin clients. All proposed changes to the
protocol and client API (currently for java thin client only) are
described in IEP-122 [1]
Please have a look and share your thoughts.
[1]
https://cwiki.
+1
Checked sha512, signature. Built from sources. Checked examples.
чт, 25 янв. 2024 г. в 20:56, Nikita Amelchev :
>
> +1 (binding)
>
> Checked compilation, tests and some examples.
>
> вт, 23 янв. 2024 г. в 16:57, Ivan Daschinsky :
> >
> > Sorry for my mistake, this vote will be open till Jan 2
lude this feature as experimental
and disabled by default for at least one release.
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-113+Change+approach+to+store+checkpoint+recovery+data
чт, 9 нояб. 2023 г. в 20:05, Anton Vinogradov :
>
> Alex, agree to the proposal.
>
> On Thu, Nov
t; And, then implement an async physical logging as an alternative solution?
>
> On Thu, Nov 9, 2023 at 12:52 PM Alex Plehanov
> wrote:
>
> > Anton,
> >
> > My concern is not only about compatibility. The new recovery data
> > storing approach is not a silve
oving the code complexity.
>
> On Thu, Nov 2, 2023 at 4:55 PM Alex Plehanov
> wrote:
>
> > Hello, Igniters!
> >
> > I'd like to discuss the way of storing checkpoint recovery data.
> > Now, we are writing extra data to WAL files to protect from failures
Hello, Igniters!
I'd like to discuss the way of storing checkpoint recovery data.
Now, we are writing extra data to WAL files to protect from failures
during checkpoints. Later, we read and write WAL files with this extra
data a couple of times, causing excessive disk load, which can lead to
perfo
Hello Scott,
What kind of issues do you have with jdk17?
I've tested graalvm native images with Ignite 2.15 some time ago
(right after 2.15 was released) on jdk11 and jdk17 and it works on my
examples.
пн, 9 окт. 2023 г. в 11:24, Stephen Darlington :
>
> That's great news, thanks for sharing!
>
>
Pavel, do you know anyone who uses it?
Looks like it isn't used at all (no questions on mail lists, no
tickets), but we spend developers time to build module with every
Ignite rebuild, we spend users traffic to download module (ML with
dependencies takes about 1/4 of our binary release package siz
Dear community,
The release of Apache Ignite 2.15.0 RC0 has been accepted.
Vote result: The vote PASSES with six +1 votes (3 bindings),
no 0 votes,
and no -1 votes.
+1 votes:
- Pavel Tupitsyn (binding)
- Nikita Amelchev
- Vladimir Steshin
- Maxim Muzafarov (binding)
- Ilya Shishkov
- Ivan Daschi
Dear Community,
The release candidate is ready.
I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.15.0-rc0/
The following staging can be used for testing:
https://repository.apache.org/content/r
> > a lot of changes from 'ignite' to 'gridgain'
> That's not good, requested changes on that PR.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-DocumentationFeedbackviaBugyard
>
> On Tue, Apr 11, 2023
IGNITE-17892
>
> https://issues.apache.org/jira/browse/IGNITE-18496
>
> https://issues.apache.org/jira/browse/IGNITE-18260
>
> 在 2023/4/10 21:31, Alex Plehanov 写道:
> > Hello Igniters,
> >
> > I've cut the release branch: 'ignite-2.15'. Please, cherry-pi
Hello Igniters,
I've cut the release branch: 'ignite-2.15'. Please, cherry-pick new issues
if needed.
The 2.15 scope is frozen. Unresolved not-blocking issues will be moved to
the next release on the code freeze stage.
пт, 7 апр. 2023 г. в 17:03, Alex Plehanov :
> Hello Ig
y (10 Apr). I will inform
you accordingly, when it will be done.
[1] : https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.15
пт, 31 мар. 2023 г. в 13:18, Jian Chen :
> +1
>
> Вячеслав Коптилин 于2023年3月31日 周五下午6:12写道：
>
> > +1
> >
> > ср, 29
Dear Ignite Community!
I suggest starting Apache Ignite 2.15 release activities.
We've accumulated more than two hundred resolved issues [1] with new
features and bug fixes which are waiting for release.
The major changes related to the proposed release:
- Incremental snapshots.
- Java thin clien
Jian Chen,
There is such a view as STATISTICS_GLOBAL_DATA, but looks like it isn't
documented.
пт, 3 мар. 2023 г. в 11:13, Jian Chen :
> Hi Igniters,
>
> I am trying to get table statistics for a Ignite table, find the document
> in
>
> https://ignite.apache.org/docs/latest/monitoring-metrics/sy
Jian Chen, merged to master. Thanks for the contribution!
пт, 3 мар. 2023 г. в 08:13, Jian Chen :
> Hi Igniters!
>
> I have sent a PR https://github.com/apache/ignite/pull/10578 to fix the
> description demos about the refresh command.
> This should no impact to the live version, the change is ve
Hello, Jian Chen
In Ignite date values can also be inserted by KV API, so year stored in the
database can be outside of valid SQL standard range (0001-). If such
values will be prohibited inside the "toInternal" method, there can be
unexpected exceptions on select from the database. Some pure
rver.
> As I understand, the scenario is: we know that the server is at address
> a.b.c.d,
> but we are not sure which port will be chosen,
> because ClientConnectorConfiguration has a portRange.
> Most likely it is the first port in range, so we should try that first.
>
> On
Hello, Igniters!
I've found that since Ignite 2.12 java thin client always connects to the
first address from the provided addresses list. In typical configuration
this leads to overloading one server node and underloading other server
nodes. Even when partition awareness is enabled some types of
Hello,
Looks reasonable. Also, it looks like the 'ignite-direct-io' module has
redundant 'ignite-indexing' dependency too (perhaps it's required for
tests, but dependency scope should be 'test' in this case).
I will remove redundant 'ignite-indexing' dependencies from 'ignite-spring'
and 'ignite-d
+1 for remove visorcmd and daemon nodes (there was already discussion about
this on dev list as far as I remember).
GridClient and related classes are not used by visorcmd, but used by
control.sh and can't be removed.
чт, 1 дек. 2022 г. в 09:00, Zhenya Stanilovsky :
>
> +1 for remove.
>
>
>
>
> >
> Added new experimental, Apache Calcite based SQL engine
It was added in 2.13, in 2.14 it became ignite-indexing (and H2)
independent.
+1
Build from sources, start a cluster of two nodes, try some queries on
Calcite SQL engine (with removed ignite-indexing module).
пт, 30 сент. 2022 г. в 15:02,
Hello,
Yes, it really exists. See AbstractDataPageIO.compactIfNeed method.
вт, 27 сент. 2022 г. в 06:31, 18624049226 <18624049...@163.com>:
> hello team,
>
>
> https://ignite.apache.org/docs/latest/memory-architecture#memory-defragmentation
>
> Does this memory defragmentation function really ex
Hello!
Apache Calcite 1.32 is already released, but [1] is still not resolved.
I propose not to wait for this ticket. "NATURAL JOIN" is a relatively rare
case, I think we can live with it for a while. Other improvements
look more valuable.
I've prepared a ticket to upgrade Apache Calcite dependenc
Folks, why should we construct a fully functional affinity function on the
client side by custom client code? We need only a key to partition mapping,
so only this simple mapper factory will be enough.
>From my point of view there are to options possible:
- provide ability to set partition to key m
+1
Checked build from sources.
Checked tests and some examples.
Found minor issue: ignite-spring-data-ext RELEASE_NOTES.txt file contains
information about version 2.2.0 instead of 2.0.0
пт, 13 мая 2022 г. в 12:59, Anton Vinogradov :
> +1
>
> On Fri, May 13, 2022 at 12:59 PM Николай Ижиков
>
"0" from me.
Check signs and checksums.
Check build from sources.
Can't check tests since I don't have AWS/azure/GCE accounts.
Found issues:
1. The same problems with building instructions (DEVNOTES.md) as for
spring-data-ext/spring-sessions-ext/zookeeper-ip-finder-ext extensions.
2. Wrong using
"0" from me.
1. I don't quite understand why the version of ignite-spring-data-ext is
2.2.0?
There were already versions released earlier:
ignite-spring-data-ext 1.0.0
ignite-spring-data-2.0-ext 1.0.0
ignite-spring-data-2.2-ext 1.0.0
Artifacts ignite-spring-data-ext and ignite-spring-data-2.0-ext
+1
Built from sources, started 2 nodes cluster, checked some DDL/DML SQL
queries with H2-based and Calcite-based engines.
As earlier mentioned by Ivan there is an issue, ignite-calcite module
requires also slf4j library, but it's absent in the
libs/optional/ignite-calcite directory, so it's not en
Hello Igniters,
I've merged the pull request. The Calcite-based SQL engine is in the master
branch now.
If you desire to try it, you can find configuration instructions in
modules/calcite/README.txt file.
вс, 6 мар. 2022 г. в 13:03, Alex Plehanov :
> Hello Igniters,
>
> I'v
L engine in 2.13 as an
> experimental feature.
> ++1
>
> On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov
> wrote:
>
> > Andrey,
> >
> > > Is this [1] a full scope of the tickets that MUST be resolved before
> the
> > engine could be merged?
> > Y
Hello,
Flag expand=false is required to support some types of subqueries.
But we can also perform decorrelation explicitly after subquery rewriting.
I've filled the ticket [1].
Thank you!
[1]: https://issues.apache.org/jira/browse/IGNITE-16493
сб, 5 февр. 2022 г. в 14:50, Chang Chen :
> Hi All
Hello,
Why do you think CALCITE-4052 is a blocker for top-down optimization
in Ignite? As far as I understand, CALCITE-4052 is an umbrella ticket to
implement trait propagation for all physical relational operators of the
"enumerable convention" in Calcite. Ignite doesn't use enumerable
convention
Andrey,
> Is this [1] a full scope of the tickets that MUST be resolved before the
engine could be merged?
Yes, we must resolve at least these tickets before merging. If you see any
other release blockers fill free to attach them to this ticket.
> I think we have to add instructions to the readm
I forgot to attach links:
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
[2]: https://github.com/apache/ignite/tree/sql-calcite
ср, 29 дек. 2021 г. в 21:00, Alex Plehanov :
> Hello, Igniters!
>
> As you may already know there is the new I
Hello, Igniters!
As you may already know there is the new Ignite SQL engine based on Apache
Calcite currently under development.
Reasons to move from H2-based engine and motivation for creating the new
one in details described in IEP-37 [1].
You can find all related to the new engine source code
or not, there is no way to check, no way to disable
>
>
> > I'm voting for option (3).
>
> Can you clarify please, is it going to be a new interface, let's say
> IgniteServicesSomething,
> and "IgniteServices extends IgniteServicesSomething"?
>
>
&g
+1
Checked build from the source, cluster startup with 2 nodes.
пн, 20 дек. 2021 г. в 16:27, Nikolay Izhikov :
> +1 (binding)
>
> > 20 дек. 2021 г., в 16:20, Ivan Daschinsky
> написал(а):
> >
> > +1 from me
> > Checked ODBC drivers (32-bit and 64-bit) installers on Windows with
> running
> > lo
Pavel,
As for option (1): the count of methods will increase in geometric
progression with each new parameter. For example, if we decide to add
tracing to services, we should keep current methods as-is for backward
compatibility and add new methods supporting a tracing parameter.
> Also, we don't
Nikolay, Andrei,
I've already merged the patch.
чт, 25 нояб. 2021 г. в 14:36, Nikolay Izhikov :
> Hello, Andrei.
>
> I will review your changes shortly.
>
> > 25 нояб. 2021 г., в 14:31, Andrei Demidov
> написал(а):
> >
> > Hi!
> >
> > Could somebody please explain me.
> > Should I do something
+1
Checked sha512 and sign of archives, built from sources, started a cluster
with a few nodes.
вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
> Ilya,
>
> > I'm still confused by this publish/ directory. Why are we shipping
> > something which is not for publishing in our binary package? I've al
Zhenya, congratulations! Well deserved!
пт, 30 июл. 2021 г. в 00:06, Maxim Muzafarov :
> The Project Management Committee (PMC) for Apache Ignite has invited
> Zhenya Stanilovsky to become a committer and we are pleased to announce
> that
> he has accepted.
>
> For the last few years, Zhenya mad
Denis,
Should we also remove nabble from "community resources" page [1] on Ignite
website? Or, at least, somehow mark it as discontinued?
[1] : https://ignite.apache.org/community/resources.html
ср, 28 июл. 2021 г. в 14:41, Ilya Kasnacheev :
> Hello!
>
> I think there's nothing which prevents P
Petr, thank you!
It's working now.
ср, 28 июл. 2021 г. в 11:03, Petr Ivanov :
> I've created issue in INFRA project about this matter [1].
>
> Please, stand by,
>
>
>
> [1] https://issues.apache.org/jira/browse/INFRA-22150
>
> > On 28 Jul 2021, at 09
Hello, Igniters!
Looks like the MTCGA site hosted on Apache Ignite domain [1] is currently
down (at least since yesterday), however, this site hosted on GridGain
domain [2] is working.
Can anyone have a look what's happening?
[1] : mtcga.ignite.apache.org
[2] : mtcga.gridgain.com
-0 for both proposals
I agree with Ivan Daschinsky, we should not mix both approaches (interfaces
with "public" keyword and without "public" keyword), but I see no big
difference between "require public keyword in interfaces" rule and
"prohibit public keyword in interfaces" rule. To switch from on
es not perform any progress.
>
> вт, 20 июл. 2021 г. в 21:43, Ivan Daschinsky :
>
>> +1 For current fix. Code is clean and understandable. I suppose that the
>> current fix is a correct variant to update heartbeatTs.
>>
>> вт, 20 июл. 2021 г. в 16:13, Alex Plehanov :
&g
Hello, Ilya
> But anyway, I propose to remove the update of the heartbeat from other
threads altogether and wrap the call to listeners in a blockingSection.
I don't quite understand your proposal. Which call to listeners do you
mean? If we wrap the listener into the blocking section the result wil
Alexey,
Some of these tickets are already documented. Do we need to clear the "Docs
Required" flag if documentation for the ticket has been merged to the
master and release branch? AFAIK we didn't do that for previous releases.
пн, 5 июл. 2021 г. в 13:53, Alexey Gidaspov :
> Hi, Nikita!
>
> As I
+1
Check sha512, sign of archives and versions of released artifacts.
Check licenses with "mvn validate -P check-licenses"
Build from the source with Java 8, run unit tests
пт, 2 июл. 2021 г. в 12:01, Maxim Muzafarov :
> +1 (binding)
>
> On Thu, 1 Jul 2021 at 13:23, Nikolay Izhikov wrote:
> >
Nikita,
What's wrong with platform-specific thin-client articles? These articles
describe how to configure and use specific thin client implementation, why
should we remove them?
чт, 1 июл. 2021 г. в 16:06, Ivan Daschinsky :
> Binary prorocol description should stand and improved (there are some
+1
Check sha512, sign of archives and versions of released artifacts.
Check licenses with "mvn validate -DskipTests -P check-licenses"
Build modules from the source with Java 8
Run examples:
from modules/spring-data-2.0-ext/examples with artifacts: Ignite
v2.10.0/ignite-spring-data-2.0-ext v1.0.0/
+1
Check sha512, sign of archives and versions of released artifacts (BTW,
version of parent artifact is 1.0.0-SNAPSHOT, I don't think it's a blocker
now, but it's better to be fixed in the next releases).
Check licenses with "mvn validate -DskipTests -P check-licenses"
Build modules from the sour
Ivan, congratulations!
вт, 13 апр. 2021 г. в 13:02, Andrey Mashenkov :
> Ivan, congrats!
>
> On Tue, Apr 13, 2021 at 11:42 AM Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > Ivan, great work.
> >
> > вт, 13 апр. 2021 г. в 10:53, Ivan Pavlukhin :
> >
> > > Ivan, congrats!
> > >
>
method
> which takes takes interface as parameter? That will not break the back
> compatible
>
> On Fri, 2 Apr 2021, 14:32 Alex Plehanov, wrote:
>
> > Hello, Atri
> >
> > 1. ClientChannelDisconnectListener is thin client specific.
> > 2. Thick client API uses J
atible with Thick API
> ClientCache#query(ContinuousQuery, ClientChannelDisconnectListener) -
> specific to Thin, easy to discover
>
> Thoughts?
>
> On Fri, Apr 2, 2021 at 12:02 PM Alex Plehanov
> wrote:
>
> > Hello, Atri
> >
> > 1. ClientChannelDisconnectListen
t; parameters, then let ClientChannelDisconnectListener actually
> implement that interface and override the base methods? The methods
> can be no-op in the thick clients.
>
> On Fri, Apr 2, 2021 at 2:04 PM Alex Plehanov
> wrote:
> >
> > Hello, Igniters!
> >
> > I'd like to discus
Hello, Igniters!
I'd like to discuss java thin client Continuous Queries public API.
Currently, the thin client is not JCache compatible and without JCache
compatible cache instance we can't use classes and API which already used
by the thick client for cache entry events listening.
In my first a
Hello,
One more area where newcomers' contributions will be very helpful is MTCGA
activity (see [1], [2]). There are a lot of flaky tests in Ignite,
usually, the reason of flakiness is some concurrency issue in test code but
sometimes tests flaky due to some bugs in production code.
Why MTCGA is
Pavel,
IEP looks good to me overall. I have only one concern: currently, for thick
client "add" method we return the future which completes when the current
batch is actually added to the cache, even if "flush" method is not invoked
explicitly. For thin client with the proposed protocol we can't p
Hello Pavel,
Changing the "compact footer" property for an existing database can lead to
compatibility issues. Some clients (at least java) have "false" as the
default value of the "compact footer" property, but the default value for
the server-side is "true". If thin client will receive binary co
Mirza, sure. Will wait for your review.
пн, 25 янв. 2021 г. в 11:06, Mirza Aliev :
> Hello, Alexey!
>
> Thank you for your effort, the feature looks great!
>
> Could you please give a bit more time to review it?
>
> Best regards,
> Mirza Aliev
>
> пт, 22 янв.
://issues.apache.org/jira/browse/IGNITE-13761
пт, 25 дек. 2020 г. в 12:26, Alex Plehanov :
> Guys,
>
> I've implemented Segmented-LRU page replacement algorithm and benchmarked
> results, it gives some boost (5-10%) when page replacement is
> heavily used, but, unfortunately, when replacement
ething similar.
> >4. Repeat step 2. in this time performance of random queries should be
> lower due to the page replacement.
> >
> >Is this scenario correct?
> >
> >> 23 нояб. 2020 г., в 09:12, Alex Plehanov < plehanov.a...@gmail.com >
> написал(а):
&
+1 (binding)
(checked build from source and start, checked build C++ from source and
start, checked slim binary start, checked some examples)
чт, 17 дек. 2020 г. в 10:41, Yaroslav Molochkov :
> Denis,
>
> where should i make my PR to update documentation? To my understanding
> there was a discu
-1 for disabling test without removing the code. Current tests give us at
least "something works" status for the feature available to users, without
these tests, we can smoothly move to "totally unusable" status.
Complete removal of MVCC can be resource-consuming, but if we want to
disable tests at
ow all data - `SELECT SUM(x)
> FROM t` or something similar.
> 4. Repeat step 2. in this time performance of random queries should be
> lower due to the page replacement.
>
> Is this scenario correct?
>
> > 23 нояб. 2020 г., в 09:12, Alex Plehanov
> написал(а):
> &g
Nikolay, Zhenya,
Benchmark from IGNITE-13034 is fully synthetic, it makes random puts
uniformly. It can be used to compare different page replacement algorithms
(random-LRU vs segmented-LRU), but it is totally inapplicable to benchmark
batch page replacement.
Perhaps we can implement a special ben
Zhenya,
> Alexey, we already have changes that partially fixes this issue [1]
IGNITE-13086 it's a minor improvement. We still have major problems with
our page replacement algorithm (slow page selection and non-optimal
page-fault rate). I think changing from random 5 pages to 7 will make
things ev
Hello, Igniters!
Currently, for page replacement (page rotation between page-memory and
disk) we use Random-LRU algorithm. It has a low maintenance cost and
relatively simple implementation, but it has many disadvantages and affects
performance very much when replacement is started. We even have w
Thanks, guys!
ср, 18 нояб. 2020 г. в 17:29, Мирза Алиев :
> My congratulations!
>
> Best Regards,
> Mirza Aliev
>
> ср, 18 нояб. 2020 г. в 13:51, Vyacheslav Daradur :
>
>> Alex, congrats!
>>
>> ср, 18 нояб. 2020 г. в 13:39, Вячеслав Коптилин > >:
>>
>> > Hooray!
>> >
>> > Congratulations, Alex! W
e manually?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 6 нояб. 2020 г. в 09:38, Alex Plehanov :
>
> > Igniters,
> >
> > Ignite 2.9 announce blog post is published now: [1]
> >
> > [1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
&g
+1 for using GridNioServer as java thin client communication layer.
вс, 8 нояб. 2020 г. в 19:12, Pavel Tupitsyn :
> Igniters,
>
> This is a continuation of "Use Netty for Java thin client" [1],
> I'm starting a new thread for better visibility.
>
> The problems with current Java thin client are:
Guys,
We already have FileWriteAheadLogManager#maxSegCountWithoutCheckpoint.
Checkpoint triggered if there are too many WAL segments without checkpoint.
Looks like you are talking about this feature.
пт, 6 нояб. 2020 г. в 13:21, Ivan Daschinsky :
> Kirill and I discussed privately proposed appro
Igniters,
Ignite 2.9 announce blog post is published now: [1]
[1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
пт, 25 сент. 2020 г. в 11:04, Alex Plehanov :
> Denis,
>
> Ok, I will prepare the text soon.
>
> чт, 24 сент. 2020 г. в 23:36, Denis Magda :
>
Hello,
You can run current Ignite binaries on JDK11, no need to compile it on
JDK11.
If you still want to compile it by yourself on JDK11, try the command line
that I provided.
You can also try Ignite 2.9, this issue is fixed in the 2.9 release.
вс, 1 нояб. 2020 г. в 23:12, shm :
> Hi Ilya Kasna
Hello,
It can be compiled if you don't need JavaDoc and scala modules (visor
console, ignite-spark integration):
mvn clean install -Pall-java,licenses,-scala,-scala-2.10,-spark-2.4
-DskipTests -Dmaven.javadoc.skip=true
пт, 30 окт. 2020 г. в 18:49, Ilya Kasnacheev :
> Hello!
>
> I don't think so
impossible to use the release branch for documentation changes that will
> follow after. I'm suggesting to create another branch for the docs needs
>once the release is finished. @Alex Plehanov can
>we try out this approach for Ignite 2.9?:
>
> https://cwiki.apache
Fixed (rearranged imports)
вт, 27 окт. 2020 г. в 20:41, :
> 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 volunteer to make the contribution to this
ite/ignite-core/2.9.0/
ср, 21 окт. 2020 г. в 18:24, Ilya Kasnacheev :
> Hello!
>
> I can see that RC4 has vanished from the site but 2.9.0 did not
> materialize. When is it due?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 20 окт. 2020 г. в 17:03, Alex Plehanov :
Dear community,
The vote for a new release candidate is closed, now.
Vote result: The vote PASSES with seven +1 votes (6 bindings), no 0 votes
and no -1 votes.
+1 votes:
- Pavel Tupitsyn (binding)
- Zhenya Stanilovsky
- Ilya Kasnacheev (binding)
- Denis Magda (binding)
- Andrey Gura (binding)
-
Pavel,
Why can't we use GridNioServer for java thin clients?
It has the same advantages as Netty (future based async API, SSL, etc) but
without extra dependency.
GridClient (control.sh), for example, uses GridNioServer for communication.
сб, 17 окт. 2020 г. в 11:21, Ivan Daschinsky :
> Hi.
> >>
Zhenya,
It's not ok, but I think it's not a release blocker.
Sources can be compiled using instructions given in DEVNOTES.txt (there are
no requirements to enable checkstyle in our documentation).
But we can fix build scripts to check compilation with enabled checkstyle
for future releases.
Guys,
Dear Community,
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.9.0-rc4/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.0-rc4/
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-148
Canceling vote for RC3 due to wrong version (-SNAPSHOT) in source artifact.
ed .NET binaries, examples, documentation
> > > - Started a mixed cluster of .NET and Java nodes
> > > - Compiled Ignite from sources
> > >
> > > On Tue, Oct 13, 2020 at 10:48 PM Denis Magda
> wrote:
> > >
> > >> +1 (binding)
&
Dear Community,
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.9.0-rc3/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.0-rc3/
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-148
9 core.
вт, 13 окт. 2020 г. в 07:34, Denis Magda :
> Is it possible/reasonable to run a single vote for Ignite 2.9 and all the
> migrated extensions? This time. @Alex Plehanov ,
> what do you think?
>
> If we decide to release the versions 1.0.0 of the extensions after 2.9 is
> o
Command to print system view content
> >> IGNITE-13422 - Parameter to explicitly enable experimental commands
> >>
> >> IGNITE-13380 - Output IgniteSystemProperties via ignite.sh
> >>
> >> New system views:
> >>
> >> IGNITE-13409 Met
Dear community,
The vote for a new release candidate is closed, now.
Vote result: Vote not passes with one -1 vote.
-1 votes:
- Nikolay Izhikov (binding)
Vote thread:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-9-0-RC2-td49480.html
I will create a new rele
Hello guys,
I've finished the review and approved the patch.
Anybody else would like to review it?
пн, 28 сент. 2020 г. в 11:38, Pavel Pereslegin :
> Hello, Maksim!
>
> I am currently working on a review notes from Alexey Plekhanov, will
> let you know when I finish.
>
> пн, 28 сент. 2020 г. в 1
1 - 100 of 272 matches
Mail list logo
