Ivan Pavlukhin created IGNITE-9404:
--
Summary: Ignite start hangs infinitely when sync preloading is
cancelled
Key: IGNITE-9404
URL: https://issues.apache.org/jira/browse/IGNITE-9404
Project: Ignite
Denis, Nikolai,
Suppose, issue IGNITE-7165 [1] is already included in the release scope,
but I think I can mention it here.
It's about re-balance optimization - now client node join\left doesn't
affect re-balance process.
In general, it's not so much about client node as about if assignments not
Also in addition to that how about generating event when updates are failed
which can be listened to and custom logic can be added to handle the
failures?
On Wed, Aug 29, 2018 at 6:56 AM, Denis Magda wrote:
> Val,
>
> Sounds like a handy configuration option. I would allow setting a number of
>
Alexey Goncharuk created IGNITE-9405:
Summary: Update documentation for metrics for remains to evict
keys/partitions
Key: IGNITE-9405
URL: https://issues.apache.org/jira/browse/IGNITE-9405
Project
Since the write-behind store wraps the store provided by a user, I think
the correct solution would be to catch the exception and not propagate it
further in the store, because only the end-user knows which errors can be
retried, and which errors cannot.
In this case no changes in the write-behind
Igniters,
We have a lot of threads, created by bots on the dev list.
Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
others too, but these are the most active.
Take a look at this page:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-Developers-f1i35.ht
Vladimir Ozerov created IGNITE-9406:
---
Summary: Improve SQL "Performance and Debugging" page
Key: IGNITE-9406
URL: https://issues.apache.org/jira/browse/IGNITE-9406
Project: Ignite
Issue Typ
Anton Kalashnikov created IGNITE-9407:
-
Summary: Node is hang when it was stopping from several client in
one time
Key: IGNITE-9407
URL: https://issues.apache.org/jira/browse/IGNITE-9407
Project:
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/4639
IGNITE-9388: mesos IgniteProvider tries to access obsolete ignite.runâ¦
⦠or downloads from slow archive.
You can merge this pull request into a Git repository by running:
$ git pull https:
Modern mail services allow users to filter messages. You can easily filter
out bot messages.
2018-08-29 11:48 GMT+03:00 Denis Mekhanikov :
> Igniters,
>
> We have a lot of threads, created by bots on the dev list.
> Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> others
Roman Shtykh created IGNITE-9408:
Summary: Update mesos version
Key: IGNITE-9408
URL: https://issues.apache.org/jira/browse/IGNITE-9408
Project: Ignite
Issue Type: Task
Reporter:
Nikolay,
I think we should have 2 weeks after code freeze which by the way may
include RC1 voting stage. This way I would like us to agree that release
candidate should be sent to vote on Oct, 11th and we can release on Oct,
15th.
What do you think?
--Yakov
Roman Shtykh created IGNITE-9409:
Summary: yarn IgniteProvider uses an obsolete URL for a version
check
Key: IGNITE-9409
URL: https://issues.apache.org/jira/browse/IGNITE-9409
Project: Ignite
Denis,
I would like to keep a single entry point into the whole Ignite development
process project,
but maybe other Igniters have another opinion on this. As for me, it's a
more convenient way
for searching any activity on dev.list by single keyword (e.g. PRs, JIRAs,
topics).
As mentioned Dmitry,
Hi, Igniters!
Who can refresh TeamCity's security certificate?
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4640
IGNITE-9402
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9402
Alternatively you can review and apply these ch
Certificates are updated, TC is up and running.
ср, 29 авг. 2018 г. в 12:55, Dmitrii Ryabov :
> Hi, Igniters!
>
> Who can refresh TeamCity's security certificate?
>
Vladimir Ozerov created IGNITE-9410:
---
Summary: MVCC: add support to thin clients
Key: IGNITE-9410
URL: https://issues.apache.org/jira/browse/IGNITE-9410
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-9411:
---
Summary: Lock: make sure lock timeouts works fine
Key: IGNITE-9411
URL: https://issues.apache.org/jira/browse/IGNITE-9411
Project: Ignite
Issue Type: T
Thank you.
2018-08-29 13:33 GMT+03:00 Alexey Goncharuk :
> Certificates are updated, TC is up and running.
>
> ср, 29 авг. 2018 г. в 12:55, Dmitrii Ryabov :
>
> > Hi, Igniters!
> >
> > Who can refresh TeamCity's security certificate?
> >
>
Denis,
I am against filtering out MTCGA messages from the dev-list because test
failures affect every developer in the community and may be caused by any
developer in the community. Usually such emails require immediate action
and it would be wrong to move them to a separate list.
I understand, t
Guys,
Yep, I use filters on my mail account. But the portal is impossible to use.
When you subscribe to the dev list for the first time, you don't have any
history on your email,
and the archive is polluted with messages, sent by bots.
Some view on Nabble, that doesn't contain any automatically g
Yury Babak created IGNITE-9412:
--
Summary: [ML] GDB convergence by error support.
Key: IGNITE-9412
URL: https://issues.apache.org/jira/browse/IGNITE-9412
Project: Ignite
Issue Type: Improvement
Yury Babak created IGNITE-9413:
--
Summary: [ML] Learning rate optimization for GDB.
Key: IGNITE-9413
URL: https://issues.apache.org/jira/browse/IGNITE-9413
Project: Ignite
Issue Type: Improvement
Yury Babak created IGNITE-9414:
--
Summary: [ML] Using sparce vectors in Tree-based algorithms.
Key: IGNITE-9414
URL: https://issues.apache.org/jira/browse/IGNITE-9414
Project: Ignite
Issue Type:
Yury Babak created IGNITE-9415:
--
Summary: [ML] Using sparce vectors in LSQR and MLP
Key: IGNITE-9415
URL: https://issues.apache.org/jira/browse/IGNITE-9415
Project: Ignite
Issue Type: Improvemen
Anton Dmitriev created IGNITE-9416:
--
Summary: [ML] Update distribution approach for TensorFlow module
Key: IGNITE-9416
URL: https://issues.apache.org/jira/browse/IGNITE-9416
Project: Ignite
Ilya Suntsov created IGNITE-9417:
Summary: IgniteSqlInsertIndexedValueBenchamrks failed with more
than one driver
Key: IGNITE-9417
URL: https://issues.apache.org/jira/browse/IGNITE-9417
Project: Ignit
Turik,
Could you please take a look on those two bugs:
https://issues.apache.org/jira/browse/IGNITE-9354
https://issues.apache.org/jira/browse/IGNITE-9359
Thanks,
Yury
Pavel Kovalenko created IGNITE-9418:
---
Summary: Avoid initialize file page store manager for caches
during PME synchronously
Key: IGNITE-9418
URL: https://issues.apache.org/jira/browse/IGNITE-9418
Pr
Pavel Kovalenko created IGNITE-9419:
---
Summary: Avoid saving cache configuration synchronously during PME
Key: IGNITE-9419
URL: https://issues.apache.org/jira/browse/IGNITE-9419
Project: Ignite
Pavel Kovalenko created IGNITE-9420:
---
Summary: Move logical recovery phase outside of PME
Key: IGNITE-9420
URL: https://issues.apache.org/jira/browse/IGNITE-9420
Project: Ignite
Issue Type:
Github user SomeFire closed the pull request at:
https://github.com/apache/ignite/pull/3236
---
Stepan Pilschikov created IGNITE-9421:
-
Summary: ML Examples: LogisticRegressionSGDTrainerExample example
result not correct
Key: IGNITE-9421
URL: https://issues.apache.org/jira/browse/IGNITE-9421
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4641
IGNITE-9348 ML examples improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9348
Alternatively you c
Denis, Nikolay, Igniters,
This is a list of planned ML features for Apache Ignite 2.7 release:
- Tensor Flow integration (
https://issues.apache.org/jira/browse/IGNITE-8670)
- Data preprocessing (https://issues.apache.org/jira/browse/IGNITE-8662)
- Model validation (https://issues.apa
Stanilovsky Evgeny created IGNITE-9422:
--
Summary: All client node fails with ZKDiscovery enabled.
Key: IGNITE-9422
URL: https://issues.apache.org/jira/browse/IGNITE-9422
Project: Ignite
Oleg Ignatenko created IGNITE-9423:
--
Summary: unreliable test:
SVMMultiClassTrainerTest.testTrainWithTheLinearlySeparableCase[Data divided on
4 partitions, training with batch size {1}]
Key: IGNITE-9423
URL: htt
Alex,
I see your point, but I still think it should be incorporated into the
product.
First of all, your solution implies changing the CacheStore implementation
every time you switch between write-through and write-behind. This
contradicts with the overall design.
Second of all, one of the most
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/4642
IGNITE-9116 .NET: LINQ: Use CacheConfiguration.SqlSchema when generating SQL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite
Pavel,
I think that point 1 is the correct way to calculate the committed
size for a log. It is already calculated regardless of the
metricsEnabled flag.
In addition, I suggest more readable log format for data regions in
issue comments [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9305
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4643
IGNITE-8886 Fix position calculation for mixed raw binary objects.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
GitHub user SGrimstad opened a pull request:
https://github.com/apache/ignite/pull/4644
Ignite 8913
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-8913
Alternatively you can review and apply these
Anton Kalashnikov created IGNITE-9424:
-
Summary: Partition equal to -1 during insert to atomic cache
Key: IGNITE-9424
URL: https://issues.apache.org/jira/browse/IGNITE-9424
Project: Ignite
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4645
IGNITE-9424 set partition to KeyCacheObject after reading from page
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4646
IGNITE-9421: fixed model output
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9421
Alternatively you can revi
Dmitry Karachentsev created IGNITE-9425:
---
Summary: NPE on index rebuild
Key: IGNITE-9425
URL: https://issues.apache.org/jira/browse/IGNITE-9425
Project: Ignite
Issue Type: Bug
Affec
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4647
IGNITE-9425 - Fix NPE on index rebuild
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9425
Alternatively
Val,
There is no need to have two implementations of the store, the exception
may be handled based on the cache configuration, the store only need to
check whether write-behind is enabled. The configuration change will be
transparently handled by the store. This change can be easily incorporated
t
Hell, Yakov
I'm ok with your proposal.
* Scope freeze - September 17 - We should have a full list of tickets
for 2.7 here.
* Code freeze - October 01 - We should merge all 2.7 tickets to master
here.
* Vote on RC1 - October 11.
* Vote on release - October 15.
В
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/4648
IGNITE-9341
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sk0x50/ignite ignite-9341
Alternatively you can review and apply these changes as t
Dmitriy Govorukhin created IGNITE-9426:
--
Summary: IgniteAtomicSequence benchmarks
Key: IGNITE-9426
URL: https://issues.apache.org/jira/browse/IGNITE-9426
Project: Ignite
Issue Type: Bug
GitHub user ekaterina-nbl opened a pull request:
https://github.com/apache/ignite/pull/4649
IGNITE-7783 PHP Thin Client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nobitlost/ignite ignite-7783
Alternatively you can review an
The Project Management Committee (PMC) for Apache Ignite
has invited Dmitriy Pavlov to become a PMC member and we are pleased
to announce that he has accepted.
Being a PMC member enables assistance with the management
and to guide the direction of the project.
Congratulations Dmitriy! Keep contri
The Project Management Committee (PMC) for Apache Ignite
has invited Dmitriy Govorukhin to become a committer and we are pleased
to announce that he has accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should
Hi folks,
PHP thin client is ready for review.
Jira with the scope of work - [1].
Implementation, examples, tests:
PR - [2],
repository - [3].
API spec - [4].
Readme (how to for the client, instructions for the examples and tests,
etc.) - [5].
Regards,
-Alexey
[1] https://issues.apach
Dmitriy, congrats! Looking forward to many contributions to come.
On Wed, Aug 29, 2018 at 12:35 PM, Denis Magda wrote:
> The Project Management Committee (PMC) for Apache Ignite
> has invited Dmitriy Govorukhin to become a committer and we are pleased
> to announce that he has accepted.
>
> Bein
Is anyone in the community using or was using Nabble for the dev list
communication? Personally, I am subscribed to the dev list and use filters
in my email client.
D.
On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov
wrote:
> Guys,
>
> Yep, I use filters on my mail account. But the portal is i
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/4650
IGNITE-9408: Update Apache Mesos version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-9408
Alternatively you can rev
59 matches
Mail list logo
