dules/core/src/main/java/org/apache/ignite/spi/metric/Metric.java
--
Alexey Kuznetsov
or external systems and only useful thing is self
> documentation.
>
> On Wed, Nov 6, 2019 at 12:42 PM Nikolay Izhikov
> wrote:
> >
> > Hello, Alexey.
> >
> > I'm +1.
> > Let's do it.
> >
> > В Ср, 06/11/2019 в 16:37 +0700, Alexey
es
> > > towards this. If I won't see any activity, I will go forward with JIRA
> > > issue.
> > >
> > > Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
> > > We tried to move it to Quartz but it changed semantics in some ways.
> > >
> > > Regards,
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>
--
Alexey Kuznetsov
>
> > I tend to agree with Alexey - API compatibility should be preserved
> within
> > a major version. I would oppose doing such a change in 2.x.
> >
> > If this is planned for 3.0, then it's a definite +1 from me.
> >
> > -Val
> >
> > On Wed, D
ember 23, 2019, sgtech19 wrote:
> >>>>
> >>>>> Hello team,
> >>>>> I would like to add a new feature to the existing
> >>> visor
> >>>>> commands. Could you give me some direction on how to achieve this if
> >>> its
> >>>>> possible? Do we need a visor plugin ? if so,please provide any
> >> example
> >>> of
> >>>>> this plugin .
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -
> >>>> Denis
> >>>
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Ivan Pavlukhin
> >>>
> >>
>
>
--
Alexey Kuznetsov
a Kasnacheev demonstrated [4], the more 3rd party
> >> libraries
> >>> we
> >>>>>> have, the more potential vulnerabilities will show up in audit
> >> tools.
> >>>>> This
> >>>>>> may be a formal barrier for Apache Ignite adoption and moving to
> >>>>> production
> >>>>>> for many users. Having a slim image with the minimum number of
> >>>>> dependencies
> >>>>>> (yet complete enough to fit the majority of use-cases)
> >> significantly
> >>>>>> reduces this risk.
> >>>>>>
> >>>>>> I wonder what community thinks regarding this idea? Given the
> >> recent
> >>>>> study
> >>>>>> of Apache Ignite use-cases, I suggest the following list of modules
> >>> to
> >>>> be
> >>>>>> included to the slim release/image (a subject to discuss, of
> >> course):
> >>>>>> * ignite-core
> >>>>>> * ignite-indexing
> >>>>>> * ignite-rest-http
> >>>>>> * ignite-spring
> >>>>>> * ignite-log4j
> >>>>>> * ignite-log4j2
> >>>>>> * ignite-slf4j
> >>>>>> * ignite-urideploy
> >>>>>> * ignite-kubernetes
> >>>>>> * ignite-opencensus
> >>>>>>
> >>>>>> [1]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Ignite-3-0-and-to-be-removed-list-td42330.html
> >>>>>> [2]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html
> >>>>>> [3]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12361-Migrate-Flume-module-to-ignite-extensions-td45010.html
> >>>>>> [4]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-td43616i100.html#a44994
> >>>>>>
> >>>>>> --AG
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
--
Alexey Kuznetsov
-1 Prohibit
>From my point of view, we should not deprecate the old API if the new API
is marked as experemental.
On Mon, Feb 10, 2020 at 4:47 PM Konstantin Orlov
wrote:
> -1 Prohibit
>
> We should not deprecate the old API if the new API could change in the
> near future.
Alex,
Can you cherry-pick to Ignite 2.9 this issue:
https://issues.apache.org/jira/browse/IGNITE-13246 ?
This issue is about BASELINE events and it is very useful for notification
external tools about changes in baseline.
Thank you!
---
Alexey Kuznetsov
Dmitriy,
I'm working on moving Web Console to separate repository IGNITE-13038
<https://issues.apache.org/jira/browse/IGNITE-13038>,
but I can not commit to https://github.com/apache/ignite-web-console
Do you know how I can be granted with commit rights?
---
Alexey Kuznetsov
you tried "real" repository address
> https://gitbox.apache.org/repos/asf/ignite-web-console.git ?
>
> 2020-07-17 14:01 GMT+03:00, Alexey Kuznetsov :
> > Dmitriy,
> >
> > I'm working on moving Web Console to separate repository IGNITE-13038
> > <h
Alex, Denis
Issue with moving of Web Console to separate repository is merged to master.
See: https://issues.apache.org/jira/browse/IGNITE-13038
Please, consider to cherry-pick to ignite-2.9
---
Alexey Kuznetsov
t; > > it.
> >> > >> > > > > > > > > > > > > > > > > > Others won't notice it, because
> it
> >> will
> >> > >> get
> >> > >> > > > lost
> >> >
.11. Originally we have the old version of Scala
> for supporting old versions of Apache Spark.
>
> But support for Scala 2.10 was removed as of 2.3.0 Apache Spark released.
> And current version if 2.4.0.
>
> Please share your opinion
>
> Best regards,
> Yuriy Babak
>
--
Alexey Kuznetsov
I'm using comm...@ignite.apache.org to track who and what commits to
master :)
--
Alexey Kuznetsov
k, we should rework control.sh utility in Apache Ignite 3.0
> > > release.
> > > > I made umbrella ticket [1] for it.
> > > >
> > > > For a start we should move utitlity from ignite-core to separate
> module
> > > > [2]. It's enable using
Hi,
I think it make sense to remove Windows version detection, because Java 8+
will simply not even start on old Windows.
--
Alexey Kuznetsov
in tests, because it easily to set system
property in Java code,
and very non trivial to do the same for environment variables.
Does any body have objections if I create JIRA issue (with pull request) to
replace all direct calls of "System.getenv(key)" with
IgniteSystemProperti
gt;
> > Hello!
> >
> > I think it does indeed makes sense to always use
> > *IgniteSystemProperties.getStri**ng*
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 11 апр. 2019 г. в 16:40, Alexey Kuznetsov :
> >
>
:
> > > >
> > > > Hi,
> > > >
> > > > I have raised a PR for the below issue.
> > > >
> > > > IGNITE-7285 Add default query timeout
> > > >
> > > > PR - https://github.com/apache/ignite/pull/6490
> > > >
> > > > Please take a look and share feedback.
> > > >
> > > > Regards,
> > > > Saikat
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>
--
Alexey Kuznetsov
;> > * Fixed a bug that made it impossible to change the
> > inline_size
> > > > > >> property
> > > > > >> >of an existing index after it was dropped and recreated with a
> > > > different
> > > > > >> >value
> > > > > >> >
> > > > > >> >RELEASE NOTES:
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;hb=ignite-2.7.6
> > > > > >> >
> > > > > >> >Complete list of closed issues:
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6
> > > > > >> >
> > > > > >> >DEVNOTES
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.7.6
> > > > > >> >
> > > > > >> >The vote is formal, see voting guidelines
> > > > > >> >https://www.apache.org/foundation/voting.html
> > > > > >> >
> > > > > >> >+1 - to accept Apache Ignite 2.7.6-rc1
> > > > > >> >0 - don't care either way
> > > > > >> >-1 - DO NOT accept Apache Ignite Ignite 2.7.6-rc1 (explain why)
> > > > > >> >
> > > > > >> >See notes on how to verify release here
> > > > > >> >https://www.apache.org/info/verification.html
> > > > > >> >and
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > > > > >> >
> > > > > >> >This vote will be open for at least 3 days till Sun Aug 25,
> 18:00
> > > > UTC.
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/to?year=2019&month=8&day=25&hour=18&min=0&sec=0&p0=utc-1
> > > > > >> >
> > > > > >> >Best Regards,
> > > > > >> >Dmitriy Pavlov
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Zhenya Stanilovsky
> > > > > >>
> > > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
> >
>
--
Alexey Kuznetsov
heIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept Apache Ignite 2.7.6-rc2
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite Ignite 2.7.6-rc2 (explain why)
> > >
> > > See notes on how to verify release here
> > > https://www.apache.org/info/verification.html
> > > and
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-ReleaseVerification
> > >
> > > This vote will be open for at least 72 hours till September 16, 09:00
> > UTC.
> > >
> > >
> >
> https://www.timeanddate.com/countdown/to?year=2019&month=9&day=16&hour=09&min=0&sec=0&p0=utc-1
> > >
> > > -- Alexey Goncharuk
> > >
> >
>
--
Alexey Kuznetsov
> So I think i can go through code and cleanup thing like that.
>
> Need I create new issue in JIRA for cleanup or some issue for cleanup
> already exists? If that please give me a link.
>
--
Alexey Kuznetsov
Hello! My name is also Alexey Kuznetsov :)
And I'm one of developer of this utility (IGNITE-3385 Improve schema import
utility).
In general you could improve schema import utility, but we decided to drop
it in favor of Web Console.
Web Console also can import schema import and it is alrea
*Best Regards,*
>
> *Kuznetsov Aleksey*
>
--
Alexey Kuznetsov
Added comment to issue and removed "newbie" label.
On Fri, Jan 27, 2017 at 6:18 PM, ALEKSEY KUZNETSOV wrote:
> Hi!) Got it
>
> пт, 27 янв. 2017 г. в 13:22, Alexey Kuznetsov :
>
> > Hello! My name is also Alexey Kuznetsov :)
> >
> > And I'm one of d
ost of
> H2 DDL features, Ignite DDL structure will be even simpler.
>
> it should take no more than 1-2 days to implement fully-fledged parsing for
> these two commands.
>
> Thoughts?
>
> Vladimir.
>
> [1] http://www.h2database.com/html/grammar.html#create_table
> [2] http://www.h2database.com/html/grammar.html#create_index
>
--
Alexey Kuznetsov
What is your JIRA ID?
I will add you to Apache Ignite contributors.
On Fri, Jan 27, 2017 at 7:34 PM, ALEKSEY KUZNETSOV wrote:
> I know! But i don't have sufficient privileges yet
>
> пт, 27 янв. 2017 г. в 14:41, Alexey Kuznetsov :
>
> > Aleksey,
> >
> > FYI:
Added to contributors.
On Fri, Jan 27, 2017 at 9:04 PM, ALEKSEY KUZNETSOV wrote:
> https://issues.apache.org/jira/secure/ViewProfile.jspa?
> name=Alexey+Kuznetsov
>
> пт, 27 янв. 2017 г. в 16:48, Alexey Kuznetsov :
>
> > What is your JIRA ID?
> > I will add you to
a/browse/IGNITE-4627>
>
> Please share your thoughts and ideas.
>
> [1] https://www.voltdb.com/blog/testing-voltdb-sqlcoverage
> [2] https://github.com/VoltDB/voltdb/tree/master/tests/sqlcoverage
>
> --
> Sergey Kozlov
> www.gridgain.com
>
--
Alexey Kuznetsov
) Current implementation will collect info and cancel only "TwoStep"
queries.
Should we also support LOCAL queries?
2) Should we also support SqlQuery / ScanQuery ?
--
Alexey Kuznetsov
Any feedback, please?
On Mon, Jan 30, 2017 at 9:38 PM, Alexey Kuznetsov
wrote:
> Hi All!
>
> I prepared first version https://issues.apache.org/jira/browse/IGNITE-4436
> (SQL: create API to collect list of running SQL queries and cancel them).
>
> Please review it and giv
ou
> ask about SqlQuery.
> As for ScanQuery I would do it as a next step.
>
> The review of the code should be done by Sergi. Let’s give him some time
> to do that.
>
> —
> Denis
>
> > On Jan 31, 2017, at 5:13 AM, Alexey Kuznetsov
> wrote:
> >
> > Any
Hi, All!
I found a very special bug [1] in Continuation.
I debugged it and prepared fix.
Test added.
Please review [2].
1. https://issues.apache.org/jira/browse/IGNITE-4676
2. http://reviews.ignite.apache.org/ignite/review/IGNT-CR-91
--
Alexey Kuznetsov
t; bundle.
> > For instance, LoadCache class which is not covered there.
> > Project’s README claims that all the configuration is in “config” dir
> > while in fact all configuration files are under “resources/META-INF”.
> >
> > *Mac OS Specific*
> > It’s know that on Mac OS the project is downloaded as “Uknown” file.
> > However, the warning that states this is hard to notice. Viktoria, please
> > take a look at this issue as well.
> >
> >
> > —
> > Denis
>
--
Alexey Kuznetsov
e issue by the time of my
> webinar (Feb 15th).
>
> —
> Denis
>
>
> > On Feb 9, 2017, at 12:16 AM, Alexey Kuznetsov
> wrote:
> >
> > Denis, thanks for your feedback.
> >
> > I will take a look and make Web Console more user friendly.
> >
> > Dima,
&
ome Ignite nodes? If yes, what version of Ignite are you
> using.
> No, I don't start any Ignite nodes.
>
> -Prachi
>
>
>
> On Mon, Feb 6, 2017 at 6:34 PM, Alexey Kuznetsov
> wrote:
>
>> Prachi,
>>
>> Thanks for catching this.
>>
>>
pache.org/jira/browse/IGNITE-1178
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>
--
Alexey Kuznetsov
=refs/tags/1.9.0-rc2
>
> RELEASENOTES
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.9.0-rc2
>
> Please start voting.
>
> +1 - to accept Apache Ignite 1.9.0-rc2
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 1.9.0-rc2 (explain why)
>
> This vote will go for 72 hours.
>
--
Alexey Kuznetsov
Hi, Kartik!
What is your Apache JIRA ID?
On Fri, Mar 10, 2017 at 2:38 AM, Kartik Somani <
kartiksomani.offic...@gmail.com> wrote:
> Hi,
>
> Can someone add me to contributors list?
>
> I want to assign a ticket to myself, but unable to.
>
> Regards,
> Kartik
>
--
Alexey Kuznetsov
loverSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheValueConsistencyAtomi
> > cPrimaryWriteOrderNearEnabledS
> > >>>>>> elfTest
> > >>>>>>>>>>>>> -> GridCacheValueConsistencyNearEnabledSelfTest
> > >>>>>>>>>>>>>>>>>> CacheContinuousQueryAsyncFailo
> > verAtomicPrimaryWriteOrderSelfTest
> > >>>>>> ->
> > >>>>>>>>>>>>> CacheContinuousQueryAsyncFailoverSelfTest
> > >>>>>>>>>>>>>>>>>> CacheContinuousQueryFailoverAt
> > omicPrimaryWriteOrderSelfTest
> > >>>>>> ->
> > >>>>>>>>>>>>> CacheContinuousQueryFailoverSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.
> > testNoBackupsPrimaryWriteOrder
> > >>>>>> ->
> > >>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.testNoBackups
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.
> > >>>>>> testWithBackupsPrimaryWriteOrder
> > >>>>>>>>>>>>> -> GridCacheAtomicNearCacheSelfTest.testWithBackups
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> Remove classes:
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> IgniteCacheAtomicPrimaryWriteOrderStoreValueTest
> > >>>>>>>>>>>>>>>>>> GridCacheReplicatedAtomicPrima
> > ryWriteOrderMultiNodeFullApiSe
> > >>>>>> lfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrd
> > erMultiNodeFullApiSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrd
> > erMultiNodeP2PDisabledFullApiS
> > >>>>>> elfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWrityOrd
> > erOffHeapMultiNodeFullApiSelfT
> > >>>>>> est
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrd
> erOffHeapFullApiSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrderFullApiSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrderReloadAllSelfTest
> > >>>>>>>>>>>>>>>>>> IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest
> > >>>>>>>>>>>>>>>>>> GridCacheValueConsistencyAtomi
> > cPrimaryWriteOrderSelfTest
> > >>>>>>>>>>>>>>>>>> IgniteCacheAtomicPrimaryWriteOrderExpiryPolicyTest
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ok? :)
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> 1 марта 2017 г., в 2:04, Andrey Gura <
> ag...@apache.org
> > >
> > >>>>>> написал(а):
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> No, it should be removed. If somebody use entry last
> > update
> > >>>>>> time
> > >>>>>>>>>>>>> (e.g.
> > >>>>>>>>>>>>>>>>>>> for conflict resolving) they should store this time
> as
> > entry
> > >>>>>> field.
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> On Wed, Mar 1, 2017 at 12:57 AM, Dmitriy Setrakyan
> > >>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>> Do we still need GridClockSyncProcessor?
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> On Tue, Feb 28, 2017 at 5:26 AM, Andrey Gura <
> > >>>>>> ag...@apache.org>
> > >>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> Maxim,
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> Yes, this setting doesn't make sense anymore. So we
> > need
> > >>>>>> remove
> > >>>>>>>>>>>>> all
> > >>>>>>>>>>>>>>>>>>>>> related methods.
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> Also there is component called
> > GridClockSyncProcessor that
> > >>>>>> also
> > >>>>>>>>>>>>> should
> > >>>>>>>>>>>>>>>>>>>>> be removed. It will lead to removing globalTime
> > field from
> > >>>>>>>>>>>>>>>>>>>>> GridCacheVersion class and some related methods.
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> On Tue, Feb 28, 2017 at 3:21 PM, Kozlov Maxim <
> > >>>>>>>>>>>>> dreamx@gmail.com>
> > >>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>> Valentin,
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> Then there is no need for setting
> > CacheConfiguration.
> > >>>>>>>>>>>>> atomicWriteOrderMode.
> > >>>>>>>>>>>>>>>>>>>>> What do you think, remove it and and related
> methods?
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> 28 февр. 2017 г., в 2:49, Valentin Kulichenko <
> > >>>>>>>>>>>>>>>>>>>>> valentin.kuliche...@gmail.com> написал(а):
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> Hi Max,
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> In case we remove the CLOCK mode, I think we
> should
> > >>>>>> remove the
> > >>>>>>>>>>>>> enum
> > >>>>>>>>>>>>>>>>>>>>> too, as
> > >>>>>>>>>>>>>>>>>>>>>>> well as configuration properties and other code
> > using
> > >>>>>> this
> > >>>>>>>>>>>>> enum. Having
> > >>>>>>>>>>>>>>>>>>>>>>> enum with one value doesn't make sense to me.
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> -Val
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> On Mon, Feb 27, 2017 at 5:09 AM, Kozlov Maxim <
> > >>>>>>>>>>>>> dreamx@gmail.com>
> > >>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> Hi Igniters,
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> After remove CLOCK mode,
> > CacheAtomicWriteOrderMode enum
> > >>>>>>>>>>>>> contains now
> > >>>>>>>>>>>>>>>>>>>>> only
> > >>>>>>>>>>>>>>>>>>>>>>>> one value PRIMARY. Andrey Gura, proposition
> remove
> > >>>>>>>>>>>>>>>>>>>>>>>> CacheAtomicWriteOrderMode enum. Will there be
> > something
> > >>>>>>>>>>>>> special for
> > >>>>>>>>>>>>>>>>>>>>> this
> > >>>>>>>>>>>>>>>>>>>>>>>> purpose is enum?
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> jira: https://issues.apache.org/
> > jira/browse/IGNITE-4587
> > >>>>>> <
> > >>>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/
> jira/browse/IGNITE-4587
> > >
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> --
> > >>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>> Max K.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Best Regards,
> > >>>>>>>>>> Max K.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Best Regards,
> > >>>>>>>> Max K.
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Best Regards,
> > >>>>>> Max K.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>
> > >>> --
> > >>> Best Regards,
> > >>> Max K.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >> --
> > >> Best Regards,
> > >> Max K.
> > >>
> > >>
> > >>
> > >>
> >
> > --
> > Best Regards,
> > Max K.
> >
> >
> >
> >
> >
>
--
Alexey Kuznetsov
rEnabledS
> >>>>>> elfTest
> >>>>>>>>>>>>> -> GridCacheValueConsistencyNearEnabledSelfTest
> >>>>>>>>>>>>>>>>>> CacheContinuousQueryAsyncFailo
> verAtomicPrimaryWriteOrderSelfTest
> >>>>>> ->
> >>>>>>>>>>>>> CacheContinuousQueryAsyncFailoverSelfTest
> >>>>>>>>>>>>>>>>>> CacheContinuousQueryFailoverAt
> omicPrimaryWriteOrderSelfTest
> >>>>>> ->
> >>>>>>>>>>>>> CacheContinuousQueryFailoverSelfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.
> testNoBackupsPrimaryWriteOrder
> >>>>>> ->
> >>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.testNoBackups
> >>>>>>>>>>>>>>>>>> GridCacheAtomicNearCacheSelfTest.
> >>>>>> testWithBackupsPrimaryWriteOrder
> >>>>>>>>>>>>> -> GridCacheAtomicNearCacheSelfTest.testWithBackups
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Remove classes:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> IgniteCacheAtomicPrimaryWriteOrderStoreValueTest
> >>>>>>>>>>>>>>>>>> GridCacheReplicatedAtomicPrima
> ryWriteOrderMultiNodeFullApiSe
> >>>>>> lfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrd
> erMultiNodeFullApiSelfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrd
> erMultiNodeP2PDisabledFullApiS
> >>>>>> elfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWrityOrd
> erOffHeapMultiNodeFullApiSelfT
> >>>>>> est
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrderOffHeapFullApiSelfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrderFullApiSelfTest
> >>>>>>>>>>>>>>>>>> GridCacheAtomicPrimaryWriteOrderReloadAllSelfTest
> >>>>>>>>>>>>>>>>>> IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest
> >>>>>>>>>>>>>>>>>> GridCacheValueConsistencyAtomi
> cPrimaryWriteOrderSelfTest
> >>>>>>>>>>>>>>>>>> IgniteCacheAtomicPrimaryWriteOrderExpiryPolicyTest
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ok? :)
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> 1 марта 2017 г., в 2:04, Andrey Gura >
> >>>>>> написал(а):
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> No, it should be removed. If somebody use entry last
> update
> >>>>>> time
> >>>>>>>>>>>>> (e.g.
> >>>>>>>>>>>>>>>>>>> for conflict resolving) they should store this time as
> entry
> >>>>>> field.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Wed, Mar 1, 2017 at 12:57 AM, Dmitriy Setrakyan
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>> Do we still need GridClockSyncProcessor?
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On Tue, Feb 28, 2017 at 5:26 AM, Andrey Gura <
> >>>>>> ag...@apache.org>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Maxim,
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Yes, this setting doesn't make sense anymore. So we
> need
> >>>>>> remove
> >>>>>>>>>>>>> all
> >>>>>>>>>>>>>>>>>>>>> related methods.
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Also there is component called
> GridClockSyncProcessor that
> >>>>>> also
> >>>>>>>>>>>>> should
> >>>>>>>>>>>>>>>>>>>>> be removed. It will lead to removing globalTime
> field from
> >>>>>>>>>>>>>>>>>>>>> GridCacheVersion class and some related methods.
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> On Tue, Feb 28, 2017 at 3:21 PM, Kozlov Maxim <
> >>>>>>>>>>>>> dreamx@gmail.com>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>> Valentin,
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Then there is no need for setting
> CacheConfiguration.
> >>>>>>>>>>>>> atomicWriteOrderMode.
> >>>>>>>>>>>>>>>>>>>>> What do you think, remove it and and related methods?
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> 28 февр. 2017 г., в 2:49, Valentin Kulichenko <
> >>>>>>>>>>>>>>>>>>>>> valentin.kuliche...@gmail.com> написал(а):
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Hi Max,
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> In case we remove the CLOCK mode, I think we should
> >>>>>> remove the
> >>>>>>>>>>>>> enum
> >>>>>>>>>>>>>>>>>>>>> too, as
> >>>>>>>>>>>>>>>>>>>>>>> well as configuration properties and other code
> using
> >>>>>> this
> >>>>>>>>>>>>> enum. Having
> >>>>>>>>>>>>>>>>>>>>>>> enum with one value doesn't make sense to me.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> -Val
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Mon, Feb 27, 2017 at 5:09 AM, Kozlov Maxim <
> >>>>>>>>>>>>> dreamx@gmail.com>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Hi Igniters,
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> After remove CLOCK mode,
> CacheAtomicWriteOrderMode enum
> >>>>>>>>>>>>> contains now
> >>>>>>>>>>>>>>>>>>>>> only
> >>>>>>>>>>>>>>>>>>>>>>>> one value PRIMARY. Andrey Gura, proposition remove
> >>>>>>>>>>>>>>>>>>>>>>>> CacheAtomicWriteOrderMode enum. Will there be
> something
> >>>>>>>>>>>>> special for
> >>>>>>>>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>>>>>>>>> purpose is enum?
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> jira: https://issues.apache.org/
> jira/browse/IGNITE-4587
> >>>>>> <
> >>>>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-4587
> >
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> Best Regards,
> >>>>>>>>>>>>> Max K.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Best Regards,
> >>>>>>>>>> Max K.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Best Regards,
> >>>>>>>> Max K.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Best Regards,
> >>>>>> Max K.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>
> >>> --
> >>> Best Regards,
> >>> Max K.
> >>>
> >>>
> >>>
> >>>
> >>
> >> --
> >> Best Regards,
> >> Max K.
> >>
> >>
> >>
> >>
>
> --
> Best Regards,
> Max K.
>
>
>
>
>
--
Alexey Kuznetsov
forget to merge master to you PR.
On Tue, Mar 14, 2017 at 10:35 AM, Alexey Kuznetsov
wrote:
> Maxim,
>
> Could you merge master to your PR?
> I failed to review Web Console files due to conflicts.
>
> Thanks.
>
> On Fri, Mar 10, 2017 at 3:06 PM, Kozlov Maxim
>
this breaks the usability in some sense because my simplest query
> above no longer works.
>
> What if we add a special checkbox to Web Console that will add fields like
> ‘id’ to a POJO? If the checkbox is disabled (default) we should show a
> message at the final importing stage
ove no longer works.
>>
>> What if we add a special checkbox to Web Console that will add fields
>> like ‘id’ to a POJO? If the checkbox is disabled (default) we should show a
>> message at the final importing stage saying that fields like ‘id’ has to be
>> replaced with ‘_key’.
>>
>> Thoughts?
>
>
>
--
Alexey Kuznetsov
perty "Cluster Name" to
Ignite configuration?
Or as alternative way it could use "Mandatory User Defined Attribute".
Node should be rejected to join cluster with different "Cluster Name"
Thoughts?
--
Alexey Kuznetsov
about the existence of _key and
> _val fields? These fields, if needed, should be completely internal. Do you
> disagree?
>
> On Wed, Mar 15, 2017 at 5:32 PM, Alexey Kuznetsov
> wrote:
>
> > Dmitriy,
> >
> > Are you sure???
> >
> > AFAIK _key and _va
blem
> > of Web console how to name or rename different clusters for a user, but
> not
> > Ignite cluster itself.
> >
> > Sergi
> >
> > 2017-03-16 4:21 GMT+03:00 Dmitriy Setrakyan :
> >
> > > I am OK with having a cluster name, but I would l
Dima & Denis,
See: https://issues.apache.org/jira/browse/IGNITE-3487
and
http://apache-ignite-developers.2346864.n4.nabble.com/DML-data-streaming-td14385.html
On Thu, Mar 16, 2017 at 8:18 AM, Dmitriy Setrakyan
wrote:
> On Wed, Mar 15, 2017 at 5:42 PM, Alexey Kuznetsov >
> wrote:
et <
> > https://ignite.apache.org/community/contribute.html#pick-ticket>
> >
> > —
> > Denis
> >
> > > On Feb 22, 2017, at 3:34 PM, Jeyhun Karimov
> > wrote:
> > >
> > > Dear Ignite community,
> > >
> > > Can you please grant me (jeyhunkarimov) contributor access so that I
> can
> > > assign Ignite jira issues to myself ?
> > >
> > > -Best
> > > Jeyhun
> > > --
> > > -Cheers
> > >
> > > Jeyhun
> >
> > --
> -Cheers
>
> Jeyhun
>
--
Alexey Kuznetsov
ill show "long running queries"
and ability to cancel selected queries.
* Added tracking of Web Console features usage on "Admin Panel" screen,
descibed here: https://apacheignite-tools.readme.io/docs/usage-tracing
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
or queries' duration is less then
> the specified in filter."
>
> Thanks,
> -Prachi
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Igniters,
https://issues.apache.org/jira/browse/IGNITE-4838
http://reviews.ignite.apache.org/ignite/review/IGNT-CR-136
Yakov, as most expert in Compute Grid, could you take a look?
--
Alexey Kuznetsov
isorcmd will not stuck the whole cluster again.
>>
>> Is there anything wrong in "ClientMode" of the visorcmd?
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/GridCachePartitionExchangeManager-Pending-t
>> ransaction-deadlock-detection-futures-tp11362p11501.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
--
Alexey Kuznetsov
I will do it tomorrow.
On Thu, Mar 30, 2017 at 6:29 PM, Vyacheslav Daradur
wrote:
> Hello everyone.
>
> Looks like minor mistake.
>
> Please review if someone has time.
>
> --
> Best Regards, Vyacheslav
>
--
Alexey Kuznetsov
gt;
> cache.put(obj.getLongId(), obj);
> }
>
> I looked at ClusterMetrics and CacheMetrics, but I'am not sure wich method
> is real needed to me.
>
> p.s. I haven't found the answer in search.
>
> --
> Best Regards, Vyacheslav
>
--
Alexey Kuznetsov
Merged to master.
Thanks, for your contribution.
On Thu, Mar 30, 2017 at 6:29 PM, Vyacheslav Daradur
wrote:
> Hello everyone.
>
> Looks like minor mistake.
>
> Please review if someone has time.
>
> --
> Best Regards, Vyacheslav
>
--
Alexey Kuznetsov
I've prepared
IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
Discontinue the schema-import utility
Anton, could you review my changes related to Ignite *build*?
See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
--
Alexey Kuznetsov
av
>
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Data-compression-in-
> Ignite-2-0-tp10099p16317.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>
--
Alexey Kuznetsov
There were no commits for TWO years in ignite-scalar module.
Our java API is good, no need for any wrappers (IMHO).
Also we even do not use it by ourselves in Visor CMD.
Thoughts?
--
Alexey Kuznetsov
Hi,
I would like to change serialization of null strings in our
ignite-rest-http module.
Current serialization null -> "" (empty string).
Proposed serialization null -> null.
This will make things more straightforward.
Thoughts?
--
Alexey Kuznetsov
me
> >> suggests ‘null’ as a default one.
> >>
> >> I’m bringing this to your attention only because in AI 2.0 we’re trying
> to
> >> get rid of ‘null’ as a default for the cache name but, strangely, we
> keep
> >> following this criticized approache in the new API.
> >>
> >> —
> >> Denis
> >>
> >>
>
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
; Since Ignite web agent is required for almost everything on the Web
> > Console, shouldn't we have an option to download it from somewhere in the
> > top menu or side menu?
> >
> > -Prachi
> >
>
--
Alexey Kuznetsov
gt;
> > > Hi Roman,
> > >
> > > As far as I inderstand you're the author of the Redis protocol
> > > implementation.
> > >
> > > Currently I'm working on a task to prohibit null names for caches and
> > I've
> > > found that current implementation implies using of default (aka null
> > named)
> > > cache as a Redis database.
> > >
> > > So, I need your assistance to implement Redis databases and mappings
> them
> > > to particular caches.
> > >
> > > Is it in your plans to do it in near time?
> > >
> > > If not I'll appriciate your thoughts on how to do it properly)
> > >
> > > Regards,
> > > Igor
> > >
> > >
> > >
> >
>
>
>
--
Alexey Kuznetsov
I'd like to join the Ignite community and start contributing.
>
>
> May I have contributor access on JIRA? My JIRA ID is williamdo.
>
>
> I have raised an issue which I would like to work on.
>
>
> https://issues.apache.org/jira/browse/IGNITE-5119
>
--
Alexey Kuznetsov
-Ignite-2-0-0-
> RC1-tp17335p17338.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>
--
Alexey Kuznetsov
Sergey,
Good cacth. I think this issue is a blocker to release.
-1 from me (binding).
However I'v already pushed the fix, please check it.
On Sat, Apr 29, 2017 at 8:48 PM, Alexey Kuznetsov
wrote:
> Nik,
>
> Thanks, that you spotted this issue.
>
> Could you provide
s://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <https://git-wip-us.apache
> .
> > > org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=
> > > refs/tags/2.0.0-rc1>
> > >
> > > RELEASENOTES
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc1>
> > >
> > > Please start voting.
> > >
> > > +1 - to accept Apache Ignite 2.0.0-rc2
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite 2.0.0-rc2 (explain why)
> > >
> > > This vote will go for 72 hours.
> >
>
> --
> Alexey Kuznetsov
>
>
a from RDBMS - added support for table aliases.
* Many minor improvements and bugfixes.
Stay tuned for updates!
---
Alexey Kuznetsov
but cant find ignite libs on maven repository.
>
> https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
>
>
>
--
Alexey Kuznetsov
esolve ticket with Scala. Recommend me please such a issue.
> Maybe with Spark.
>
> Vadim Opolski
>
--
Alexey Kuznetsov
y jira account - NIzhikov
>
> Nikolay Izhikov
> nizhikov@gmail.com
>
--
Alexey Kuznetsov
PMC vote passes,
> > then the
> > >>>>>> SGA should be provided. Or does GridGain need to provide a signed
> > SGA
> > >>>>> right
> > >>>>>> away?
> > >>>>>
> > >>>>> That reminds me of that Pelosi's self-inflicted conundrum of "In
> > order
> > >>>>> to see the bill, we should pass the bill" ;)
> > >>>>>
> > >>>>
> > >>>> Haha :)
> > >>>>
> > >>>> SGA != code. In my view, the code should be provided to the
> community
> > for a
> > >>>> review. But I am struggling to see why should an SGA be signed prior
> > to the
> > >>>> community accepting the donation.
> > >>>
> > >>> There's no such thing as SGA without a reference to a code base.
> > >>>
> > >>> Also, as I explained -- as a community member I would refuse to look
> > >>> at the code base that doesn't have a proper licensing attached to it.
> > >>> SGA established this kind of proper licensing.
> > >>>
> > >>> Now, SGA is deinetly not the only way to do so, but it is the easiest
> > >>> and since you'd have to do it anyway the most convenient for the
> > >>> community.
> > >>>
> > >>> Thanks,
> > >>> Roman.
> > >
> >
> >
>
--
Alexey Kuznetsov
Prachi,
We added "Download Web Agent" button on right top corner.
Please, try it.
On Thu, Apr 20, 2017 at 1:27 AM, Prachi Garg wrote:
> Somewhere in the header would be more visible; I would prefer that.
>
> On Wed, Apr 19, 2017 at 12:37 AM, Alexey Kuznetsov
> wrote:
&
local deployment. Was it not part of 2.0 release?
>
> -Prachi
>
> On Fri, May 19, 2017 at 2:21 AM, Alexey Kuznetsov
> wrote:
>
>> Prachi,
>>
>> We added "Download Web Agent" button on right top corner.
>> Please, try it.
>>
>> On Thu
learance
> > > > process.
> > > > The SGA has been submitted and acknowledged by ASF Secretary. The IP
> > > > clearance form can be found here: http://incubator.apache.org/
> > > > ip-clearance/persistent-distributed-store-ignite.html
> > > > This vote is to discover if the Apache Ignite PMC and community are
> in
> > > > favour of accepting this contribution.
> > > > This vote will be open for at least 72 hours:
> > > > [ ] +1, accept contribution of the Persistent Store into the project
> > > > [ ] 0, no opinion
> > > > [ ] -1, reject contribution because...
> > > >
> > > > Regards,
> > > > Denis
> > > >
> > > >
> > >
> >
>
--
Alexey Kuznetsov
quot;default" - not the way to go, since "DEFAULT" is reserved SQL
> > keyword.
> > >>
> > >> Personally I prefer "public".
> > >>
> > >> Any other thoughts?
> > >>
> > >> Vladimir.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-5320
> > >>
> > >>
> > > --
> > > Taras Ledkov
> > > Mail-To: tled...@gridgain.com
> > >
> > >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
patibility mode for Apache Ignite was added to H2 parser
> recently. I think we can expose all these flags as SQL hints in the query
> itself, rather then setting them programmatically (or through JDBC/ODBC
> connection strings).
>
> Thoughts?
>
> Vladimir.
>
--
Alexey Kuznetsov
ossible for CREATE TABLE
> and CREATE SCHEMA) only. Anyway, this could be nice usability improvement
> for us.
>
> On Fri, Jun 2, 2017 at 5:13 PM, Alexey Kuznetsov
> wrote:
>
> > I like this, but could you show some examples?
> >
> > On Fri, Jun 2, 2017 at 9:08
anner with warning about upcoming updates.
* Support for Ignite 2.1
* Improved stack trace for SQL errors.
Stay tuned for updates!
--
Alexey Kuznetsov
idGain.
Please contact GridGain for that.
>> Will i able to use this as an alternative to say an ORM like MyBatis?
It depends in what you need. Please describe your use case.
--
Alexey Kuznetsov
Denis,
>>>Sounds great! BTW, was this ticket resolved as a part of the release:
>>> https://issues.apache.org/jira/browse/IGNITE-5303 (supporting multiple
RDBMS configurations from the wizard)
Yes we fixed this issue, now it is on testing with all major RDBMS.
--
Alexey Kuznetsov
ch will automatically read from DB
> if not in cache
> -- This includes read based on any predicate (where clause), custom
> select sql queries, bulk operations
>
> Regards,
> Muthu
>
> On Wed, Jun 7, 2017 at 12:19 AM, Alexey Kuznetsov
> wrote:
>
>> Muthu,
>>
&g
er as a distributed transactional SQL database,
> both in memory and on disk, while continuing to support all the existing
> use cases, including the in-memory data grid.
> ——————
>
> Any thoughts, suggestions?
>
> —
> Denis
--
Alexey Kuznetsov
notification to all Web Console user (useful to
notify about planned WebConsole updates).
3) Added "Basic" configuration - to configure cluster in several clicks.
4) Added panel with information about "Compute".
Stay tuned for updates!
--
Alexey Kuznetsov
Cron4J with Quartz we can move *ignite-schedule* module
from lgpl profile to main distribution.
Any objections?
If no, I will create JIRA issue and implement this change.
--
Alexey Kuznetsov
Jun 21, 2017 at 1:31 PM, Dmitriy Setrakyan
wrote:
> Alexey,
>
> Can you remind what we use the schedule module in Ignite for?
>
> D.
>
> On Wed, Jun 21, 2017 at 7:26 AM, Alexey Kuznetsov
> wrote:
>
> > Hi!
> >
> > 1) Cron4J is very old:
> > Lat
Jun 21, 2017 at 8:39 AM, Alexey Kuznetsov
> wrote:
>
> > Dima,
> >
> > IgniteScheduler provides functionality for scheduling jobs locally using
> > UNIX cron-based syntax. Instance of GridScheduler is obtained from grid
> as
> > follows:
>
d CRON;
> 5.spring's code quality is very good, maintainability is good, and the
> quality of quartz code is not very good.
> On 06/21/2017 13:26，Alexey Kuznetsov wrote：
> Hi!
>
> 1) Cron4J is very old:
> Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> Latest Quarz 2.3.0 re
; > distributed ignite job store, so you could setup and use quartz in a
> > distributed way, in a similar way to terracotta or hazelcasts quartz
> > jobstores.
> >
> >
> > Sent from my iPhone
> >
> > > On 21 Jun 2017, at 15:43, Alexey Kuznetsov
> &g
a month old...
>
> https://hub.docker.com/r/apacheignite/web-console-standalone/
>
> Regards,
> Muthu
>
> On Mon, Jun 19, 2017 at 8:04 PM, Alexey Kuznetsov
> wrote:
>
>> Igniters!
>>
>> I'd like to announce that we redeployed the new v
he
> product. Could you please help with granting me proper Ignite Jira
> permissions? My Jira user ID is "kukushal". Thank you!
>
> Best regards, Alexey
--
Alexey Kuznetsov
Hi Ankur,
What is your JIRA ID?
On Tue, Jun 27, 2017 at 3:42 PM, Ankur Kumar wrote:
> I can access Apache Ignite but can not assign any defect to myself. Can I
> get permission to assign issues to myself to work on these items?
>
> Regards,
>
> Ankur Kumar
>
--
Alexey Kuznetsov
Vova,
Huge +1 to do a stabilization.
--
Alexey Kuznetsov
ul if MBeans are not allowed e.g. for
security reasons.*"
The fix is trivial (one liner + simple text).
I can contribute the fix for this bug.
1. https://issues.apache.org/jira/browse/IGNITE-9792
--
Alexey Kuznetsov
stop using them for multi-word names,
> 3. and make them not mandatory at all (what it is actually already true,
> because of no any mention in the main code-style article).
>
>
--
Alexey Kuznetsov
Hi!
I have filter for e-mail from JIRA (very useful, I can quick search issue
there without visiting JIRA).
And I'm just deleting tons of e-mails from GitBox & about PRs.
I don't know what for we need them?
May by we try to move GitBox & PRs-related mails first and see how it
(cfg1, ... cfgN);
> > > > > >
> > > > > > where cfgX is a new cache configuration, which contains the name
> of
> > > an
> > > > > > existing persistent cache.
> > > > > >
> > > > > > The obvious limitation:
> > > > > > - affinity key mapping couldn't be changed;
> > > > > > - count of partitions couldn't be changed;
> > > > > > - MVCC couldn't be turned off/on;
> > > > > > - persistent couldn't be turned off;
> > > > > > - group settings couldn't be changed (group name);
> > > > > > - if cache belongs to group it's needed to restart all of them.
> > > > > >
> > > > > > Failure scenario is the crucial thing (and most difficult):
> > > > > > - initiator fail;
> > > > > > - cluster restart at any stage;
> > > > > > - joining/starting offline nodes.
> > > > > >
> > > > > > Some thoughts about implementation:
> > > > > > - stop cache with destroy=false;
> > > > > > - start cache dynamically with new configuration;
> > > > > > - if indexes settings changed - remove index.bin to start
> > indexation;
> > > > > > - change blt-history when start cache initiated to not allow join
> > > nodes
> > > > > > with old configuration;
> > > > > > - use restartId (IGNITE-8911) to not allow to start cache in
> > between.
> > > > > >
> > > > > > Your thoughts? Would it be a useful feature?
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Eduard.
> > > >
> > >
> >
>
--
Alexey Kuznetsov
nite-developers.2346864.n4.nabble.com/Time-to-remove-automated-messages-from-the-devlist-td37484i20.html
>
--
Alexey Kuznetsov
Hi,
We found a regression https://issues.apache.org/jira/browse/IGNITE-10432
Please take a look.
--
Alexey Kuznetsov
+1 (binding)
1. Download sources: *OK*
2. Build ignite from sources: *OK*
3. Build Web Console from sources: *OK*
4. Build Web Agent from sources: *OK*
5. Start node, Web agent and Web Console: *OK*
6. Executed several SQL queries from Web Console: *OK*
--
Alexey Kuznetsov
1 - 100 of 801 matches
Mail list logo
