Hello Guru,
I'll have a look today, thank you!
On Sat, Feb 15, 2020 at 11:33 PM Guru Stron
wrote:
> Hello, Igniters
>
> I've been out for some time and wanted to stretch a little bit my
> contributor muscles with some newbie tasks. There some changes both to Java
> and .NET, can somebody take a
Folks,
I have merged IGNITE-12650 (mark MVCC as experimental) to master and
ignite-2.8. What's left? Should we remove deprecation from the old metrics
and start the vote?
Hello, Igniters.
Can someone bring some light on the state of the ML module in Ignite?
As far as I know, for now, we have only 1 active contributor to this area -
Alexey Zinoviev.
I see how whole modules come and go from the module - [1]
Please, also note this quote:
> Also as a result of good t
Another thing I noticed is that during a update through jdbc client, there
could be 2 kinds of threads acting on it. The 'client-connector' thread and
the 'sys-stripe'. If the client-connector thread completes the transaction
and calls the record, it is able to send a 'cache_put' event with the uui
Is there anything I can do to associate the cacheevent with the logged in
jdbc client(DBEAVER user) (Can I do something in any of the methods of the
Security Plugin ) .
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello Vladimir,
> We do not know what exactly does *3-rd party persistence*.
>From my point of view, this is clearly stated here
https://www.jcp.org/en/jsr/detail?id=107 |
https://github.com/jsr107/jsr107spec and here
https://apacheignite.readme.io/docs/3rd-party-store.
In general, it is a caching
Alexey,
Yes. I will remove @deprecation according to the vote results and will
go further with the release steps [1] since there no blockers left.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
wrote:
>
> Folks,
>
> I have
Denis,
I have pre-reviewed your changes, LGTM.
Could some security maintainer take a look?
вт, 11 февр. 2020 г. в 20:37, Denis Garus :
>
> Hi, Igniters!
>
>
> I've prepared the PR[1] for the ticket[2], could somebody do a review?
>
>
> Thanks.
>
>
>
>1. https://github.com/apache/ignite/pull/
Hello, Vyacheslav.
> In my humble opinion, until we have a consensus that the existing behavior is
> a bug (and that is the question for now)
I think we have consensus that current behavior is *NOT A BUG*.
It is a design choice.
But, we have consensus that consequences of this choice is not tr
Hi Nikolay,
> 1. Explicitly warn user about consequences of the deactivation.
I absolutely agree it must be mentioned in the Javadoc, documentation, and
etc.
> Require additional confirmation.
it does make sense to me (control utility and jmx) To be honest, I don't
see a reason to introduce this
Hello, Igniters, and you, Nikolay.
First of all, if you have real interest to the ML module and its state, I
could make call with you and explain this.
*As far as I know, for now, we have only 1 active contributor to this area
-Alexey Zinoviev.*
Currently, we have 2 active contributors, me and R
>
> Hi, Vyacheslav.
>
>
>
> >>> In general, it is a caching layer above an existing 3rd party database.
> That is all.
> >>> I don't think so. It does not really matter which persistence is used
> (Ignite native persistence or RDBMS).
>
>
>
> Ok. I think we might also check if read/write-through i
Konstantin Orlov created IGNITE-12687:
-
Summary: Sqline throws unexpected exceptions on few specific
arguments to !describe and !primarykeys
Key: IGNITE-12687
URL: https://issues.apache.org/jira/browse/IGNITE-
Konstantin Orlov created IGNITE-12688:
-
Summary: Improve performance of index inline JAVA_OBJECT fields
Key: IGNITE-12688
URL: https://issues.apache.org/jira/browse/IGNITE-12688
Project: Ignite
Folks,
> Do we have plans to fix it?
It is not how community works. It depends on contributors and their
interests in maintaining and fixing particular bug/feature/module. If
someone would like to help, he/she is always welcomed.
Don't ask others to do stuff for you, in other words.
>CVE
CVEs
Hi Team,
First of all, let me introduce myself. I’m Ravil, I contribute to the ML
module since 2018 and from time to time I make talks about it. (I..e data
science summit in Warsaw [1]).
So, Alexey made a huge effort to develop the ML module but he is not alone.
If you check the repo you will fin
Hello!
I have created the following ticket:
https://issues.apache.org/jira/browse/IGNITE-12663
Our current number of threads in pools is max(8, NCPU), this means, we will
see different behavior depending on hardware.
I have adjusted GridAbstractTest so the default for most pools is 5,
excluding
Hello, Alexey.
> The main reason, the modules are not work proper way, were experimental,
> never released as a production-ready, support old, outdated version, the
> external frameworks, like Tensorflow, move integration with ignite to the
> special repos, they are not finished, the code there is
Ok, agree, that I should start discussion before making changes, but I was
limited by release 2.8 and trying don;'t be a delayed person for that.
During release I was focused on fixing bugs and don't tests TF and Ignite
together
I thought that as a maintainer of ML module I could do perform these
пн, 17 февр. 2020 г. в 14:18, Vladimir Steshin :
> > The only reason is the same implementation IgniteMXBean#active(boolean)
> > and Ignite#active(boolean). Looks like we have to choose whether to allow
> > user erase data unexpectedly or to change behavior of the API call.
>
Vladimir, those two
Alexey, as I mentioned, at now we have same implementation for IgniteMXBean
and Ignite in IgniteKernal. Already is. I agree, the implementations should
be decoupled. But extracting IgniteMXBean from IgniteKernal seems too bulky
solution to me. Tacking in account lot of variants of deactivation meth
Vladislav Pyatkov created IGNITE-12689:
--
Summary: Partitions should become owned after a checkpoint,
regardless of a topology change. Nevertheless a rebalance is not required.
Key: IGNITE-12689
URL: https://i
Ilya,
> 5 is smallest viable number, I hope that TC suites will run slightly
> faster, produce less logs, and will be easier to debug (smaller batches of
> threads to scroll)
It would be quite interesting for me to measure this positive effect.
Is it possible?
>From a practical standpoint I supp
Ticket [1] is ready for review. Comments about deprecation statements
and overall approach are highly appreciated.
[1] https://issues.apache.org/jira/browse/IGNITE-12686
Best regards,
Ivan Pavlukhin
вс, 16 февр. 2020 г. в 15:02, Ivan Pavlukhin :
>
> Andrey,
>
> Good that we care about compatibil
I updated javadoc TC job [1]. Completes successfully on master so far.
[1]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Javadoc?branch=%3Cdefault%3E&buildTypeTab=overview&mode=builds
Best regards,
Ivan Pavlukhin
пт, 14 февр. 2020 г. в 16:23, Ivan Pavlukhin :
>
> I merged c
Looks like something broke .NET NuGet tests [1] in the end of January.
Is anyone working on it?
[1]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetNuGet?branch=%3Cdefault%3E&mode=builds
Best regards,
Ivan Pavlukhin
пт, 31 янв. 2020 г. в 21:56, :
>
> Hi Igniters,
>
Maxim Muzafarov created IGNITE-12690:
Summary: Remove deprecation from DataRegionMetrics and mark
ReadOnlyMetricRegistry with IgniteExperimental
Key: IGNITE-12690
URL: https://issues.apache.org/jira/browse/IGN
Hi Manu,
As I understood you provide a link to samples showing how extensions
could be used. Do you know whether source code for extensions
(persistent text indices, etc.) is available?
Best regards,
Ivan Pavlukhin
пн, 10 февр. 2020 г. в 14:03, Manu :
>
> Hi! take a look to
> https://github.com/
I did a quick look some time ago, no idea what is going on, honestly. Tests
became flaky for no apparent reason.
I have this on my list, will investigate more.
On Mon, Feb 17, 2020 at 8:43 PM Ivan Pavlukhin wrote:
> Looks like something broke .NET NuGet tests [1] in the end of January.
> Is anyo
Pavel Tupitsyn created IGNITE-12691:
---
Summary: .NET: Native Near Cache
Key: IGNITE-12691
URL: https://issues.apache.org/jira/browse/IGNITE-12691
Project: Ignite
Issue Type: New Feature
Igniters,
I'm working on .NET Near Cache feature [1]
(storing deserialized cache entries in CLR memory to improve performance).
Implementation is based on Java near cache, with some callbacks to .NET
side
for updating and invalidating cached entries.
However, I'd like to make this feature option
Igor Seliverstov created IGNITE-12692:
-
Summary: Calcite integration. DML. Skip reducer optimization.
Key: IGNITE-12692
URL: https://issues.apache.org/jira/browse/IGNITE-12692
Project: Ignite
32 matches
Mail list logo
