Hi, Lev!
I'll return with explanation on next week, maybe I need to adds some
details to this ticket.
P.S. About dataset - you could search among the datasets presented in
MLSandbox class or could add your own (I'd prefer small datasets from
http://archive.ics.uci.edu/ml/index.php)
пт, 14 февр.
Hello everyone
I'd like to take following task:
https://issues.apache.org/jira/browse/IGNITE-12384?jql=project%20%3D%20IGNITE%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20component%20%3D%20ML%20AND%20labels%20%3D%20newbie
But I do not fully understand what exactly needs to be done.
As far as
Maxim,
There are some of the tasks that are being moved from a release to a
release or exist for a while and might be skipped for 2.8 if nobody is
willing to document them. A could of examples of such tickets:
https://issues.apache.org/jira/browse/IGNITE-10331
https://issues.apache.org/jira/browse
Denis,
Actually, I've already filtered documentation issues previously and
left only major documentation tasks. Should I shrink the list more?
On Thu, 13 Feb 2020 at 18:58, Denis Magda wrote:
>
> Maxim,
>
> Thanks for the list. How many of those tickets relate to new capabilities
> or changed be
Maxim,
Thanks for the list. How many of those tickets relate to new capabilities
or changed behavior in 2.8? You can probably come up with such a sub-list.
This filter returns all the documentation tickets we have in JIRA, and,
indeed, many of them can be pushed to further releases.
-
Denis
On
Thank you, Petr.
Sure, will not.
On Thu, 13 Feb 2020 at 18:21, Petr Ivanov wrote:
>
> Added you to Ignite Release Managers group — you should now be able to run
> Release build.
>
> Please, do not modify anything there without dev-list.
>
>
> > On 13 Feb 2020, at 17:19, Maxim Muzafarov wrote:
>
Added you to Ignite Release Managers group — you should now be able to run
Release build.
Please, do not modify anything there without dev-list.
> On 13 Feb 2020, at 17:19, Maxim Muzafarov wrote:
>
> Igniters,
>
>
> Can anyone provide access to release suites on TeamCity?
>
> [1] Main Rele
I think yes.
чт, 13 февр. 2020 г. в 16:52, Ivan Pavlukhin :
> Hi,
>
> It seems I found some more unused configuration properties:
> * TransactionConfiguration.PessimisticTxLogSize
> * TransactionConfiguration.PessimisticTxLogLinger
>
> Can we deprecate/remove them?
>
> Best regards,
> Ivan Pavluk
Ivan Pavlukhin created IGNITE-12679:
---
Summary: Simplify javadocs in SQL classes
Key: IGNITE-12679
URL: https://issues.apache.org/jira/browse/IGNITE-12679
Project: Ignite
Issue Type: Bug
Ivan,
Nothing from my side as well - looks like the property is not used.
Konstantin Orlov created IGNITE-12678:
-
Summary: GridLongList fails on add when created with explicit zero
size
Key: IGNITE-12678
URL: https://issues.apache.org/jira/browse/IGNITE-12678
Project: I
Should I wait any ML-related issues in examples?
I could wait a day or two if you are going to continue your testing deals
with ML and examples to push changes together.
Are you running your examples on the release staging as a ignite
dependency, isn't it?
чт, 13 февр. 2020 г. в 14:37, Stepan Pi
Igniters,
Can anyone provide access to release suites on TeamCity?
[1] Main Release Build (have no access)
[2] Apache Ignite Nightly Release (read-only access, can't run it,
can't configure)
login: mmuzaf
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_ApacheIgniteMain_R
Konstantin Orlov created IGNITE-12677:
-
Summary: Extend test coverage for GridLongList serialization
Key: IGNITE-12677
URL: https://issues.apache.org/jira/browse/IGNITE-12677
Project: Ignite
Pavel Tupitsyn created IGNITE-12676:
---
Summary: .NET: Add partition-based AffinityCall and AffinityRun
overloads
Key: IGNITE-12676
URL: https://issues.apache.org/jira/browse/IGNITE-12676
Project: Ign
Hi,
It seems I found some more unused configuration properties:
* TransactionConfiguration.PessimisticTxLogSize
* TransactionConfiguration.PessimisticTxLogLinger
Can we deprecate/remove them?
Best regards,
Ivan Pavlukhin
Anybody?
Best regards,
Ivan Pavlukhin
вт, 28 янв. 2020 г. в 18:29, Ivan Pavlukhin :
>
> Hi,
>
> I failed to find where CacheConfiguration.DefaultLockTimeout property
> is used. Does anyone know how is it used? If it is not used I suppose
> we can mark this property deprecated.
>
> Please share yo
I've created a wiki page based on the vote results [1]. Feel free to update
the page if it seems incomplete.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Development+Guidelines
чт, 6 февр. 2020 г. в 20:17, Alexey Goncharuk :
> Ivan, thanks, I agree, added this clause:
>
> The vote we a
Konstantin Orlov created IGNITE-12675:
-
Summary: Binary types registered in two stages when entry
processor is used
Key: IGNITE-12675
URL: https://issues.apache.org/jira/browse/IGNITE-12675
Projec
Konstantin Orlov created IGNITE-12674:
-
Summary: Extend test coverage for binary types registration
Key: IGNITE-12674
URL: https://issues.apache.org/jira/browse/IGNITE-12674
Project: Ignite
But in combination with BLT it will work as intended - no rebalancing under
the cover.
чт, 13 февр. 2020 г. в 14:39, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
> Of course, stable topology will be just a hint.
>
> Any node can leave at any moment.
>
> чт, 13 февр. 2020 г. в 14:35, Alexei
Of course, stable topology will be just a hint.
Any node can leave at any moment.
чт, 13 февр. 2020 г. в 14:35, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
> 1. Yes
>
> 2. This is right but doesn't sound like a bug. The rebalancing will be
> finished before releasing syncFut and partition
filled ticket - https://issues.apache.org/jira/browse/IGNITE-12673
чт, 13 февр. 2020 г. в 13:46, Alexey Zinoviev :
> I suppose one ticket is enough, collect where all your nites and thoughts
>
> чт, 13 февр. 2020 г., 12:12 Stepan Pilschikov :
>
>> And one (three) more thing
>>
>> In TutorialStepB
Stepan Pilschikov created IGNITE-12673:
--
Summary: ML examples logging
Key: IGNITE-12673
URL: https://issues.apache.org/jira/browse/IGNITE-12673
Project: Ignite
Issue Type: Bug
1. Yes
2. This is right but doesn't sound like a bug. The rebalancing will be
finished before releasing syncFut and partitions will contain all necessary
data (but are still in moving state).
3. No, local node doesn't wait the rebalancing on all grid nodes.
Actually, I think SYNC mode should be
Evgeniy Rudenko created IGNITE-12672:
Summary: Query annotations are not working if statement keywords
are in lower case
Key: IGNITE-12672
URL: https://issues.apache.org/jira/browse/IGNITE-12672
P
Denis,
We still need additional work over the whole documentation, not only
resolving comments for the new monitoring feature [2].
Here is the full list of issues related to documentation - [1].
Examples need to be extended too. For instance,
- suspend/resume for pessimistic transactions
- defau
Hello, everyone.
I’d like to propose to make behavior of cluster deactivation the same
independently on usage type: in code or manually with control.sh or JMX.
Let’s put it in one place like IgniteCluster#state(ClusterState newState,
boolean force) and require forced call for in-memory data.
Wh
Pavel,
It's still a big question regarding SYNC rebalance mode. Here is my thoughts.
1. Yes, we must rebalance such caches prior to ASYNC one (if the
rebalanceOrder configuration will be removed).
2. When persistence is enabled and when WAL is disabled (on the first
rebalance start), I think we
I suppose one ticket is enough, collect where all your nites and thoughts
чт, 13 февр. 2020 г., 12:12 Stepan Pilschikov :
> And one (three) more thing
>
> In TutorialStepByStepExample we running 17 examples
> First 12 logging is pretty good and looks like "Tutorial step N: name" ->
> model -> acc
> +1 to deprecate rebalanceOrder and remove related functionality,
Meant to "rework related functionality" not "remove".
чт, 13 февр. 2020 г. в 12:47, Pavel Pereslegin :
>
> Hello,
>
> +1 to deprecate rebalanceOrder and remove related functionality,
> should we create a separate ticket for this?
>
Hello,
+1 to deprecate rebalanceOrder and remove related functionality,
should we create a separate ticket for this?
Btw, as I understand, SYNC mode is only useful for in-memory caches,
because when persistence is enabled (and WAL is disabled during
rebalancing), even "ignite-sys-cache" owns part
And one (three) more thing
In TutorialStepByStepExample we running 17 examples
First 12 logging is pretty good and looks like "Tutorial step N: name" ->
model -> accuracy -> "Tutorial step N: completed"
But then starting with 13 this pattern is kind of broke, step start and
step completion is miss
Dear Ignite community,
The vote is now closed. The votes spread the following way:
[+1 Allow]: 5 votes:
Vyacheslav Daradur
Tkalenko Kirill
Nikolay Izhikov
Ilya Kasnacheev
Maxim Muzafarov
[-1 Prohibit]: 23 votes:
Sergey Antonov
Ivan Pavlukhin
Philipp Masharov
Alexey Zinoviev
Yuri Gerzhedovich
Mekh
Hello,
+1 from me for rebalance delay deprecation.
I can imagine only one actual case for this option: prevent excessive load
on the cluster in case of temporary short-term topology changes (e.g. node
is stopped for a while and then returned back).
Now it's handled by baseline auto adjustment in a
35 matches
Mail list logo
