rst means that schema exists in
> advance and all the stored data is compliant with it - that's exactly what
> is proposed. There are no restrictions prohibiting changes to the schema.
>
> -Val
>
> On Sat, Sep 5, 2020 at 9:52 PM Ivan Pavlukhin wrote:
>
>> Alexey,
>&
;
>> PR https://github.com/apache/ignite-extensions/pull/22
>>
>> Please review and share feedback.
>>
>> Regards,
>> Saikat
>
>
--
Best regards,
Ivan Pavlukhin
e created following Jira story for the same
> https://issues.apache.org/jira/browse/IGNITE-13412
>
> Regards,
> Saikat
>
>
> On Mon, Sep 7, 2020 at 3:43 AM Ivan Pavlukhin wrote:
>
>> Hi Saikat,
>>
>> Thank you for working on it!
>>
>> I notic
the projects as a
> JAVA and C++ developer.
> My JIRA username is 'sayantanu_dey'.
> Looking forward to getting my first patch merged :)
> Regards
> Sayantanu Dey
>
--
Best regards,
Ivan Pavlukhin
;.
>
> Best Regards,
> Charles Fonseca.
>
--
Best regards,
Ivan Pavlukhin
reating a cache without schema and inferring it from the first
>>> > insert.
>>> In
>>> > other words, we can have both "schema-first" and "schema-last" modes.
>>> >
>>> > Alexey, what do you think?
>>> >
>>
d
>> PDS
>> cleanup and defragmentation. As far as I know it won't bring too much
>> complexity in both cases.
>>
>> I cannot say for other components but I believe it will be possible to
>> integrate MM feature into their workflow as well with reasonabl
cation SPI as well to have 100% guarantee that no communication with
> other nodes will happen.
>
> It is important to note that GridRestProcessor is started normally as we
> need it to connect to the node via control utility.
>
> On Mon, Sep 21, 2020 at 7:04 PM Ivan Pavlukhin wrote:
>
-09-25 17:25 GMT+03:00, Kirill Gusakov :
> Hello, Ignite Community!
>
> My name is Kirill. I want to contribute to Apache Ignite, my JIRA username
> kgusakov. Any help on this will be appreciated.
>
> Thanks!
>
--
Best regards,
Ivan Pavlukhin
ant to contribute to Apache Ignite.
> My JIRA ID is *kazakov*
>
>
> Best...
> Ilya Kazakov
>
--
Best regards,
Ivan Pavlukhin
ed recipient you are notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you have received
> this email in error please notify the sender and delete this email.
>
--
Best regards,
Ivan Pavlukhin
e Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 12:11:17 06-10-2020
>
--
Best regards,
Ivan Pavlukhin
rous things.
>
> I created an issue (https://issues.apache.org/jira/browse/IGNITE-13478) and
> pull request for those changes
> (https://github.com/apache/ignite/pull/8304).
>
> Cheers, Sam.
>
--
Best regards,
Ivan Pavlukhin
;> > docs/_docs/sql-reference/system-functions.adoc
>> > docs/_docs/sql-reference/aggregate-functions.adoc
>> > docs/_docs/sql-reference/data-types.adoc
>> > docs/_docs/sql-reference/dml.adoc
>> > docs/_docs/sql-reference/date-time-
ould like to contribute to it starting with issue
> IGNITE-13563, my JIRA username being bojidar-bg.
> I have already submitted a patch, and reviews would be welcome.
>
> BRs,
> Bojidar
>
--
Best regards,
Ivan Pavlukhin
Bojidar,
While my knowledge can be outdated, but in my time it was required to
create a pull request in GitHub and launch a TC bot check against that
PR manually.
2020-10-09 18:08 GMT+03:00, Bojidar Marinov :
> On Fri, Oct 9, 2020 at 5:15 PM Ivan Pavlukhin wrote:
>
>> Hi Bojidar,
&
on is outdated, I would happily open a pull request on
> github instead.
>
> BRs,
> Bojidar
>
> On Fri, Oct 9, 2020 at 6:20 PM Ivan Pavlukhin wrote:
>
>> Bojidar,
>>
>> While my knowledge can be outdated, but in my time it was required to
>> create a
]
http://apache-ignite-developers.2346864.n4.nabble.com/Disabling-patch-validation-mechanism-on-TC-td5400.html
--
Best regards,
Ivan Pavlukhin
ould enable better
> productivity.
>
> Sergey, congratulations and welcome on board!
>
> Best Regards,
> Pavel Tupitsyn
> on behalf of Apache Ignite PMC
>
--
Best regards,
Ivan Pavlukhin
t;
> вс, 11 окт. 2020 г. в 04:43, Saikat Maitra :
>
>> +1
>>
>> Regards,
>> Saikat
>>
>> On Sat, Oct 10, 2020 at 8:22 AM Alexey Zinoviev
>> wrote:
>>
>> > Agree, need to update
>> >
>> > сб, 10 окт. 2020 г., 15:35 Iv
> Veena.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
--
Best regards,
Ivan Pavlukhin
heapExpiryPolicyTest
> IgniteCacheAtomicLocalOnheapExpiryPolicyTest
> GridCacheReplicatedOnheapFullApiSelfTest
> GridCacheBinaryObjectsLocalOnheapSelfTest
>
> oignate...@users.noreply.github.com:
> GridCacheTtlManagerEvictionSelfTest
>
> ira...@apache.org:
> CommonPoolStarvationCheckpointTest
>
> alievmi...@gmail.com:
> RemoveAllDeadlockTest
>
> schugu...@gridgain.com:
> FullyConnectedComponentSearcherTest
>
> sboi...@gridgain.com:
> IgniteDataStructuresNoClassOnServerTest
>
> timonin.ma...@gmail.com:
> ReliableChannelTest
> ThinClientPartitionAwarenessDiscoveryTest
>
--
Best regards,
Ivan Pavlukhin
rstand, Max also created verification check for not
>> included test and found a few tests, that have never been included in any
>> testsuites.
>>
>> Also, I suppose, that even if we cannot run some tests, these tests
>> should
>> be ignored using annotation,
>>>> <
>>>> https://issues.apache.org/jira/browse/IGNITE-13595?jql=project%20%3D%20Ignite%20and%20assignee%20%3D%20alex_pl%20and%20status%20in%20(Closed%2C%20Resolved)
>>>>>
>>>> since
>>>> then, was driving Ignite 2.9 as a release manager, regularly
>>>> participates
>>>> in the dev lists discussions pertaining to the future and evolution of
>>>> Ignite.
>>>>
>>>> Join me in congratulating Alex!
>>>>
>>>>
>>>> -
>>>> Denis
>>>>
>>
>>
>>
>> --
>> Best wishes,
>> Amelchev Nikita
>
>
--
Best regards,
Ivan Pavlukhin
>> > > > website. There is nothing wrong if a distributed database is used
>> > > > as
>> a
>> > > > cache or high-performance compute cluster; it's up to an
>> > > > application
>> > > > developer to decide.
>> > > >
>> > > > Overall, please cast your vote for defining Ignite as a
>> > > > "distributed
>> > > > database":
>> > > > +1 - support the change
>> > > > -1 - disagree with the change, explain why
>> > > > 0 - neutral
>> > > >
>> > > > This is a majority vote that is open for the next 7 days and to be
>> > closed
>> > > > on Monday, Nov 30th:
>> > > > https://www.timeanddate.com/countdown/to?year=2020&month=11&day=30
>> > > >
>> > > > -
>> > > > Denis
>> > > >
>> > >
>> >
>>
>
--
Best regards,
Ivan Pavlukhin
;>
>> >>>>>>>> +1 to vote for complete MVCC removal.
>> >>>>>>> It has already been discussed here [1] and, unfortunately, I have
>> >> not
>> >>>>>> seen
>> >>>>>>> an agreement on that.
>> >>>>>>>
>> >>>>>>> [1]
>> >>>>>>>
>> >>>>>>
>> >>>>
>> >>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Thanks,
>> >>>>>>> S.
>> >>>>>>>
>> >>>>>>> ср, 2 дек. 2020 г. в 13:05, Nikolay Izhikov
>> >>>>>>> :
>> >>>>>>>
>> >>>>>>>> +1 to vote for complete MVCC removal.
>> >>>>>>>>
>> >>>>>>>> MVCC is a great feature but we should implement it as a
>> >> first-class
>> >>>>>>>> feature and not «something that pretends to be working»
>> >>>>>>>>
>> >>>>>>>>> 2 дек. 2020 г., в 12:53, Maxim Muzafarov
>> >>>>>> написал(а):
>> >>>>>>>>>
>> >>>>>>>>> Hello Slava,
>> >>>>>>>>>
>> >>>>>>>>> I think we should vote for MVCC termination of support. If the
>> >> vote
>> >>>>>>>>> will be successful than remove it from the source code and
>> >> disable
>> >>>>>>>>> MVCC suites.
>> >>>>>>>>>
>> >>>>>>>>> Only disabling tests from MVCC sounds not good.
>> >>>>>>>>>
>> >>>>>>>>> On Wed, 2 Dec 2020 at 12:32, Вячеслав Коптилин <
>> >>>>>> slava.kopti...@gmail.com>
>> >>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Hello Igniters,
>> >>>>>>>>>>
>> >>>>>>>>>> It looks like there is no activity related to maintaining or
>> >>>>>> developing
>> >>>>>>>> the
>> >>>>>>>>>> MVCC feature.
>> >>>>>>>>>> So, I see no reason to waste TeamCity resources. I propose to
>> >>>> disable
>> >>>>>>>> the
>> >>>>>>>>>> corresponding test suites.
>> >>>>>>>>>> This has already been discussed here as well [1].
>> >>>>>>>>>>
>> >>>>>>>>>> [1]
>> >>>>>>>>>>
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
>> >>>>>>>>>>
>> >>>>>>>>>> Thanks,
>> >>>>>>>>>> S.
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>
>>
>>
>
--
Best regards,
Ivan Pavlukhin
the ONLY way to do that, and so far, I
>> > haven't
>> > > heard
>> > > > any
>> > > > > > clear alternatives or reasons why we shouldn't do this.
>> > > > > >
>> > > > > > That said, I'm inclined to proceed with this in the
>> > next
>> > few
>> > > days - I
>> > > > > will
>> > > > > > create a repo and describe the process (which we, of
>> > course, can
>> > > > discuss
>> > > > > > and modify going forward). Let's, at the very least,
>> > try
>> > and see
>> > > where
>> > > > it
>> > > > > > leads us.
>> > > > > >
>> > > > > > If someone has any concrete alternative options on how
>> > to
>> > we can
>> > > > maintain
>> > > > > > two major versions in parallel, let's have another
>> > voice
>> > > discussion
>> > > > this
>> > > > > > Friday. If we do the meeting, we should set it up with
>> > a
>> > clear
>> > > goal to
>> > > > > make
>> > > > > > a decision. Please let me know if there is interest in
>> > this.
>> > > > > >
>> > > > > > -Val
>> > > > > >
>> > > > > > On Mon, Nov 16, 2020 at 6:31 AM Alexey Goncharuk <
>> > > > > > alexey.goncha...@gmail.com> wrote:
>> > > > > >
>> > > > > >> Good,
>> > > > > >>
>> > > > > >> I think we have an intermediate agreement on the scope
>> and
>> > > > significance
>> > > > > of
>> > > > > >> the changes we want to make. I suggest creating
>> > separate
>> > > discussion
>> > > > > >> streams
>> > > > > >> and calls for each of the suggested topics so that:
>> > > > > >>
>> > > > > >>- It is clear for the community what is the
>> motivation
>> > of the
>> > > > stream
>> > > > > >>(this includes both functional targets and
>> > technical
>> > debt
>> > > issues
>> > > > > >> pointed
>> > > > > >>out by Sergey)
>> > > > > >>- Who is planning to take an active part in each of
>> the
>> > > streams
>> > > > (i.e.
>> > > > > >>the 'design committee', as Sergey suggested)
>> > > > > >>- What are the intermediate and final goals for
>> > each
>> > of the
>> > > streams
>> > > > > >>- What are the cross-stream interactions and how we
>> > > integrate them
>> > > > > >>- How each of the streams will be integrated with
>> > the
>> > current
>> > > > > codebase
>> > > > > >>based on the above (here is where we will see
>> > whether
>> > > drop-in or
>> > > > > >>incremental approaches make more sense)
>> > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > Best regards,
>> > > > Andrey V. Mashenkov
>> > > >
>> > >
>> > >
>> >
>> >
>>
>
--
Best regards,
Ivan Pavlukhin
,
Ivan Pavlukhin
; On Thu, Dec 17, 2020 at 11:16 PM Ivan Pavlukhin
> wrote:
>
>> Igniters,
>>
>> I noticed notifications about PRs in ignite-3 repository sent to
>> dev-list. I suppose we should configure notifications similar to main
>> ignite repository. I prepared a ticket [1]
ll be
>> > > installed and upgraded, how the user will interact with it, etc. I
>> would
>> > > like to use this to gather feedback from the community in the early
>> > stages.
>> > >
>> > > To make sure the experience is as close to real life as possible, I
>> want
>> > to
>> > > deliver what we have as an alpha release, meaning that all the
>> > > required
>> > > binaries will be deployed on the website and in Maven. There will
>> > > also
>> be
>> > > some basic documentation describing how to install and use the
>> > > product.
>> > > This way, anyone will be able to download the product and try it out.
>> > >
>> > > My main question here -- do we need a formal vote for such a build?
>> > > Or
>> it
>> > > can be treated as a release candidate?
>> > >
>> > > Any other thoughts?
>> > >
>> > > [1] https://github.com/apache/ignite-3
>> > >
>> > > -Val
>> > >
>> >
>>
>
--
Best regards,
Ivan Pavlukhin
Ticket was merged. Thanks to all participants.
2020-12-21 10:12 GMT+03:00, Ivan Pavlukhin :
> Folks,
>
> I will merge the PR tomorrow if there is no objections.
>
> 2020-12-19 0:56 GMT+03:00, Valentin Kulichenko
> :
>> Folks,
>>
>> Can someone take a look a
e feel free to share your thoughts on
>> this.
>>
>> -Val
>>
>> On Thu, Dec 17, 2020 at 10:53 PM Ivan Pavlukhin
>> wrote:
>>
>>> Hi Igniters,
>>>
>>> Forgive me that I am not reading dev list carefully these days. Was it
>>
Also I noticed that ignite-3 repository has "main" but not "master"
branch. Who can shed light on this? Did not find an explanation in
this thread.
2020-12-22 13:09 GMT+03:00, Ivan Pavlukhin :
> I noticed some free-from commit messages in ignite-3 repository. I
> think
rticle/github-to-replace-master-with-main-starting-next-month/
>
> On Tue, Dec 22, 2020 at 1:12 PM Ivan Pavlukhin wrote:
>
>> Also I noticed that ignite-3 repository has "main" but not "master"
>> branch. Who can shed light on this? Did not find an explana
anymore.
2020-12-22 13:05 GMT+03:00, Ivan Pavlukhin :
> Ticket was merged. Thanks to all participants.
>
> 2020-12-21 10:12 GMT+03:00, Ivan Pavlukhin :
>> Folks,
>>
>> I will merge the PR tomorrow if there is no objections.
>>
>> 2020-12-19 0:56 GMT+03:00, Val
er
>> Ivan's PR was merged
>>
>> ср, 23 дек. 2020 г. в 21:55, Pavel Tupitsyn :
>>
>>> Ivan, thank you for fixing this!
>>>
>>> On Wed, Dec 23, 2020 at 11:13 AM Ivan Pavlukhin
>>> wrote:
>>>
>>> > Actually a firs
w Year gifts.
>>
>>
>> In 2021, we want to track this type of contribution and ensure that the
>> contributors are recognized within the community. The Alfa version of our
>> tracking system is already functioning inside GridGain, so the next step
>> is
>> to upgrade the current system and start a discussion with PMC members.
>> Those who help to attract and retain users are definitely worthy of
>> praise
>> and promotion, as the value of their contribution matches the value that
>> is
>> provided through code and documentation.
>>
>>
>> Keep being awesome and have a Happy New Year!
>>
>>
>> Kseniya
>>
>> DevRel at GridGain
>>
>
--
Best regards,
Ivan Pavlukhin
committer enables easier contribution to the project since there
>> is
>> no need to go via the patch submission process. This should enable better
>> productivity.
>>
>> Please join me in welcoming Ivan, and congratulating him on the new role
>> in
>> the Apache Ignite Community.
>>
>> Best Regards,
>> Andrey Gura
>>
>
--
Best regards,
Ivan Pavlukhin
920
>> > > > >>
>> > > > >>
>> > > > >> On Sun, Dec 27, 2020 at 2:18 AM Valentin Kulichenko <
>> > > > >> valentin.kuliche...@gmail.com> wrote:
>> > > > >>
>> > > > >>
HA512 or MD5/SHA1 is OK for now?
>> >2. Is there a painless way to include SHA512 in addition to
>> > MD5/SHA1?
>> >
>> > Can anyone shed some light on this?
>> >
>> > [1] https://infra.apache.org/release-signing.html#basic-facts
>> > [2]
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapacheignite-1490/org/apache/ignite/ignite-core/2.9.1/
>> > [3]
>> https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
>> >
>> > -Val
>> >
>>
>>
>> --
>> Sincerely yours,
>> Ivan Bessonov
>>
>
--
Best regards,
Ivan Pavlukhin
ues.
>> >
>> > I have seen few Apache Project like Beam, Flink already uses Kanban
>> > board
>> >
>> >
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=BEAM&rapidView=325
>> >
>> >
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=356&projectKey=FLINK
>> >
>> > Please review and let me know your thoughts.
>> >
>> > Regards
>> > Saikat
>> >
>>
>
--
Best regards,
Ivan Pavlukhin
> On Mon, 7 Dec 2020 at 09:38, Ivan Pavlukhin wrote:
>>
>> Hi Igniters,
>>
>> > The feature is not production-ready, and I don't think it is used at
>> > all.
>>
>> Unfortunately, we cannot be sure that the feature is not used at all.
>>
Hi,
Stacktrace and exception message has some valuable details:
org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to
find a page for eviction [segmentCapacity=126515, loaded=49628,
maxDirtyPages=37221, dirtyPages=49627, cpPages=0, pinnedInSegment=1,
failedToPrepare=49628]
I see a
d from the current security context.
> > Thus, the description (and behavior) of the method should be the following:
> > Gets security subject ID initiated this task event if IgniteSecurity is
> > enabled, otherwise returns null.
> >
> > The same is actual for CacheEvent, C
t; > > H2 based engine and its execution flow.
> > >
> > > Some of them are critical (like impossibility to execute particular
> > > queries), some of them are majors (like impossibility to execute
> > > particular
> > > queries without pre-preparation your data to have a collocation) and many
> > > minors.
> > >
> > > Most of the issues cannot be solved without whole engine redesign.
> > >
> > > So, here the proposal:
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084
> > >
> > > I'll appreciate if you share your thoughts on top of that.
> > >
> > > Regards,
> > > Igor
> > >
--
Best regards,
Ivan Pavlukhin
opment
> > > > of ML
> > > > >> > > >
> > > > >> > > > components.
> > > > >> > > > > > > > > > > >
> > > > >> > > > > > > > > > > > On Fri, 20 Sep 2019 at 17:24, Alexey
> > Zinoviev <
> > > > >> > > >
> > > > >> > > > zaleslaw@gmail.com>
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > wrote:
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > I wrote about code freeze at December 18,
> > > > 2019, ok,
> > > > >> > we
> > > > >> > > >
> > > > >> > > > can move one
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > week
> > > > >> > > > > > > > > > > > > earlier to 11 December
> > > > >> > > > > > > > > > > > > Voting + Release could be after 10th
> > January.
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > пт, 20 сент. 2019 г. в 15:43, Maxim
> > Muzafarov <
> > > > >> > > >
> > > > >> > > > mmu...@apache.org>:
> > > > >> > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > Alexey,
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > It is not a problem to shift release a
> > bit
> > > > later or
> > > > >> > > >
> > > > >> > > > earlier, but I'm
> > > > >> > > > > > > > > > > > > > strictly against having `code freeze`
> > stage
> > > > on
> > > > >> > > >
> > > > >> > > > holidays (the
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > Christmas
> > > > >> > > > > > > > > > > > > > holidays at the end of December and New
> > Year
> > > > >> > holidays
> > > > >> > > >
> > > > >> > > > at the
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > beginning
> > > > >> > > > > > > > > > > > > > of January). From my point, it's better
> > to
> > > > have it
> > > > >> > > >
> > > > >> > > > completed `code
> > > > >> > > > > > > > > > > > > > freeze` stage before December 23th or
> > > > started after
> > > > >> > > >
> > > > >> > > > 10th January.
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > Thoughts?
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > On Fri, 20 Sep 2019 at 15:09, Dmitriy
> > Pavlov
> > > > <
> > > > >> > > >
> > > > >> > > > dpav...@apache.org>
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > wrote:
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > +1 For Maxim as release manager.
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > Maxim,
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > It is a good thing that you have
> > committer
> > > > >> > rights,
> > > > >> > > >
> > > > >> > > > and most of
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > the steps
> > > > >> > > > > > > > > > > > > > > you will be able to complete yourself.
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > But please engage one from PMC member
> > to
> > > > complete
> > > > >> > > >
> > > > >> > > > steps from the
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > release
> > > > >> > > > > > > > > > > > > > > process where PMC rights are required
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > >
> > > > >> > > >
> > > > >> > > >
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process At
> > > > >> > > > > > > > > > > > > > > least, access to docker and nuget creds
> > > > requires
> > > > >> > PMC
> > > > >> > > >
> > > > >> > > > membership.
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > Feel free to ping me, I will assist, as
> > > > well.
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > Sincerely,
> > > > >> > > > > > > > > > > > > > > Dmitriy Pavlov
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:59, Alexey
> > > > Zinoviev <
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > zaleslaw@gmail.com>:
> > > > >> > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > For Spark and ML components the best
> > > > dates
> > > > >> > should
> > > > >> > > >
> > > > >> > > > be moved to
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > one month
> > > > >> > > > > > > > > > > > > > > > later, what's about?
> > > > >> > > > > > > > > > > > > > > > There are a lot of features there,
> > but a
> > > > lot of
> > > > >> > > >
> > > > >> > > > bugs and minor
> > > > >> > > > > > > > > > > > > > > > improvements in JIRA too
> > > > >> > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > Also I support you as a release
> > manager
> > > > >> > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > Scope Freeze: December 4, 2019
> > > > >> > > > > > > > > > > > > > > > Code Freeze: December 18, 2019
> > > > >> > > > > > > > > > > > > > > > Voting Date: January 10, 2019
> > > > >> > > > > > > > > > > > > > > > Release Date: January 17, 2019
> > > > >> > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:44, Maxim
> > > > Muzafarov <
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > mmu...@apache.org>:
> > > > >> > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Igniters,
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > It's almost a year has passed since
> > > > the last
> > > > >> > > >
> > > > >> > > > major Apache
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > Ignite 2.7
> > > > >> > > > > > > > > > > > > > > > > has been released. We've
> > accumulated a
> > > > lot of
> > > > >> > > >
> > > > >> > > > performance
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > improvements
> > > > >> > > > > > > > > > > > > > > > > and a lot of new features which are
> > > > waiting
> > > > >> > for
> > > > >> > > >
> > > > >> > > > their release
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > date.
> > > > >> > > > > > > > > > > > > > > > > Here is my list of the most
> > interesting
> > > > >> > things
> > > > >> > > >
> > > > >> > > > from my point
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > since
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > the
> > > > >> > > > > > > > > > > > > > > > > last major release:
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Service Grid,
> > > > >> > > > > > > > > > > > > > > > > Monitoring,
> > > > >> > > > > > > > > > > > > > > > > Recovery Read
> > > > >> > > > > > > > > > > > > > > > > BLT auto-adjust,
> > > > >> > > > > > > > > > > > > > > > > PDS compression,
> > > > >> > > > > > > > > > > > > > > > > WAL page compression,
> > > > >> > > > > > > > > > > > > > > > > Thin client: best effort affinity,
> > > > >> > > > > > > > > > > > > > > > > Thin client: transactions support
> > (not
> > > > yet)
> > > > >> > > > > > > > > > > > > > > > > SQL query history
> > > > >> > > > > > > > > > > > > > > > > SQL statistics
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > I think we should no longer wait
> > and
> > > > freeze
> > > > >> > the
> > > > >> > > >
> > > > >> > > > master branch
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > anymore
> > > > >> > > > > > > > > > > > > > > > > and prepare the next major release
> > by
> > > > the
> > > > >> > end of
> > > > >> > > >
> > > > >> > > > the year.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > I propose to discuss Time, Scope of
> > > > Apache
> > > > >> > > >
> > > > >> > > > Ignite 2.8 release
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > and
> > > > >> > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > also
> > > > >> > > > > > > > > > > > > > > > > I want to propose myself to be the
> > > > release
> > > > >> > > >
> > > > >> > > > manager of the
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > > > planning
> > > > >> > > > > > > > > > > > > > > > > release.
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > Scope Freeze: November 4, 2019
> > > > >> > > > > > > > > > > > > > > > > Code Freeze: November 18, 2019
> > > > >> > > > > > > > > > > > > > > > > Voting Date: December 10, 2019
> > > > >> > > > > > > > > > > > > > > > > Release Date: December 17, 2019
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> > > > > > > > > > > > > > > > > WDYT?
> > > > >> > > > > > > > > > > > > > > > >
> > > > >> >
> > > > >>
> > > > >> --
> > > > >> BR, Sergey Antonov
> > > >
> >
--
Best regards,
Ivan Pavlukhin
around 7 from 211 tests are muted now)
>
> Please, if somebody interested in it, make an initial review of modular
> ignite structure and changes (without deep diving into Spark code).
>
> And yes, the proposed code is a copy-paste of spark-ignite module with a
> few fixes
--
Best regards,
Ivan Pavlukhin
> В Пн, 30/09/2019 в 20:29 +0300, Alexey Zinoviev пишет:
> > > > > Yes, as I understand it uses Spark internals from the first commit)))
> > > > > The reason - we take Spark SQL query execution plan and try to
> > execute it
> > &g
high-level users we
> > > see by working with our users. Hope it helps. Let's carry on and let me
> > > send a note to Apache Calcite community.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Mon, Sep 30, 2019 at 1:56 AM Ivan Pav
would be even better to handle this unsupported use case in the
> code as well instead of throwing a NullPointerException. I can add
> this check as improvement to the Ignite code if this is wanted and
> agreed. But I need a hint on what would be the right place to add this
> check i
> SystemView API.
>
> Any objections?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-10754
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392
> [3] https://issues.apache.org/jira/browse/IGNITE-12223
> [4] https://issues.apache.org/jira/browse/IGNITE-12224
--
Best regards,
Ivan Pavlukhin
Ivan Pavlukhin created IGNITE-12424:
---
Summary: Fix default query timeout behavior for thin JDBC
Key: IGNITE-12424
URL: https://issues.apache.org/jira/browse/IGNITE-12424
Project: Ignite
Ivan Pavlukhin created IGNITE-12457:
---
Summary: Cache 6 test suite fails with exit code 137
Key: IGNITE-12457
URL: https://issues.apache.org/jira/browse/IGNITE-12457
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-12476:
---
Summary: Slow test in Continuous Query 1 test suite
Key: IGNITE-12476
URL: https://issues.apache.org/jira/browse/IGNITE-12476
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-12477:
---
Summary: Slow test in Queries 1 test suite
Key: IGNITE-12477
URL: https://issues.apache.org/jira/browse/IGNITE-12477
Project: Ignite
Issue Type: Task
Ivan Pavlukhin created IGNITE-12482:
---
Summary: SQL: sql returns incorrect results for replicated caches
if started on node where rebalance is in progress
Key: IGNITE-12482
URL: https://issues.apache.org/jira
Ivan Pavlukhin created IGNITE-12498:
---
Summary: Calcite integration. Create a test suite on TC.
Key: IGNITE-12498
URL: https://issues.apache.org/jira/browse/IGNITE-12498
Project: Ignite
Ivan Pavlukhin created IGNITE-12565:
---
Summary: Extend test coverage [IGNITE-9279] Support custom default
SQL schema name
Key: IGNITE-12565
URL: https://issues.apache.org/jira/browse/IGNITE-12565
Ivan Pavlukhin created IGNITE-12574:
---
Summary: Fix failing IoStatisticsBasicIndexSelfTest
Key: IGNITE-12574
URL: https://issues.apache.org/jira/browse/IGNITE-12574
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-12591:
---
Summary: Scan query scans invalid partitions on unstable topology
Key: IGNITE-12591
URL: https://issues.apache.org/jira/browse/IGNITE-12591
Project: Ignite
Ivan Pavlukhin created IGNITE-12610:
---
Summary: Disable H2 object cache reliably
Key: IGNITE-12610
URL: https://issues.apache.org/jira/browse/IGNITE-12610
Project: Ignite
Issue Type: Bug
Ivan Pavlukhin created IGNITE-12619:
---
Summary: Extend test coverage of [IGNITE-11056] SQL: Create a view
with list of existing indexes
Key: IGNITE-12619
URL: https://issues.apache.org/jira/browse/IGNITE-12619
Ivan Pavlukhin created IGNITE-12630:
---
Summary: Remove developers sections from parent pom.xml
Key: IGNITE-12630
URL: https://issues.apache.org/jira/browse/IGNITE-12630
Project: Ignite
Ivan Pavlukhin created IGNITE-12644:
---
Summary: Get rid of Hadoop javadocs web link
Key: IGNITE-12644
URL: https://issues.apache.org/jira/browse/IGNITE-12644
Project: Ignite
Issue Type
Ivan Pavlukhin created IGNITE-12664:
---
Summary: Failed to dump debug information. Failed to create string
representation of binary object.
Key: IGNITE-12664
URL: https://issues.apache.org/jira/browse/IGNITE
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 Pavlukhin created IGNITE-12686:
---
Summary: Deprecate obsolete configuration properties
Key: IGNITE-12686
URL: https://issues.apache.org/jira/browse/IGNITE-12686
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-12787:
---
Summary: Remove obsolete Selector.open workaround code from
GridNioServer
Key: IGNITE-12787
URL: https://issues.apache.org/jira/browse/IGNITE-12787
Project
Ivan Pavlukhin created IGNITE-12965:
---
Summary: Redirect ignite-website GitHub notifications
Key: IGNITE-12965
URL: https://issues.apache.org/jira/browse/IGNITE-12965
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-12980:
---
Summary: Use Apache Ignite logo with registered trade mark symbol
in README.md
Key: IGNITE-12980
URL: https://issues.apache.org/jira/browse/IGNITE-12980
Ivan Pavlukhin created IGNITE-12987:
---
Summary: Remove TC badge from README.md
Key: IGNITE-12987
URL: https://issues.apache.org/jira/browse/IGNITE-12987
Project: Ignite
Issue Type: Task
Ivan Pavlukhin created IGNITE-12998:
---
Summary: Fix a typo in CONTRIBUTING.md
Key: IGNITE-12998
URL: https://issues.apache.org/jira/browse/IGNITE-12998
Project: Ignite
Issue Type: Task
Ivan Pavlukhin created IGNITE-13875:
---
Summary: Configure notifications for ignite-3 git repository
Key: IGNITE-13875
URL: https://issues.apache.org/jira/browse/IGNITE-13875
Project: Ignite
Ivan Pavlukhin created IGNITE-10917:
---
Summary: IgniteCacheQueryNodeRestartSelfTest2.testRestarts stable
failure
Key: IGNITE-10917
URL: https://issues.apache.org/jira/browse/IGNITE-10917
Project
Ivan Pavlukhin created IGNITE-10999:
---
Summary: NOT NULL sql constraint is not checked for data streamer
operations
Key: IGNITE-10999
URL: https://issues.apache.org/jira/browse/IGNITE-10999
Project
Ivan Pavlukhin created IGNITE-11020:
---
Summary: Document edge-chasing deadlock detection
Key: IGNITE-11020
URL: https://issues.apache.org/jira/browse/IGNITE-11020
Project: Ignite
Issue Type
Ivan Pavlukhin created IGNITE-11029:
---
Summary: Public API for edge-chasing deadlock detection
configuration
Key: IGNITE-11029
URL: https://issues.apache.org/jira/browse/IGNITE-11029
Project: Ignite
Ivan Pavlukhin created IGNITE-11168:
---
Summary: .NET: changing TxTimeoutOnPartitionMapExchange has no
effect
Key: IGNITE-11168
URL: https://issues.apache.org/jira/browse/IGNITE-11168
Project: Ignite
Ivan Pavlukhin created IGNITE-11246:
---
Summary: Do not use pending entries tree in MVCC execution flow
Key: IGNITE-11246
URL: https://issues.apache.org/jira/browse/IGNITE-11246
Project: Ignite
Ivan Pavlukhin created IGNITE-11289:
---
Summary: BPlusTree.AbstractForwardCursor can use obsolete page
Key: IGNITE-11289
URL: https://issues.apache.org/jira/browse/IGNITE-11289
Project: Ignite
Ivan Pavlukhin created IGNITE-11300:
---
Summary: MVCC: forbid using DataStreamer with allowOverwrite=true
Key: IGNITE-11300
URL: https://issues.apache.org/jira/browse/IGNITE-11300
Project: Ignite
Ivan Pavlukhin created IGNITE-11301:
---
Summary: MVCC: Remove extra MVCC initialization messages from logs
Key: IGNITE-11301
URL: https://issues.apache.org/jira/browse/IGNITE-11301
Project: Ignite
Ivan Pavlukhin created IGNITE-11356:
---
Summary: Test framework: Remove custom assumption exceptions
handling
Key: IGNITE-11356
URL: https://issues.apache.org/jira/browse/IGNITE-11356
Project: Ignite
Ivan Pavlukhin created IGNITE-11357:
---
Summary: MVCC: SQL tx operations and DDL inside tx block
Key: IGNITE-11357
URL: https://issues.apache.org/jira/browse/IGNITE-11357
Project: Ignite
Ivan Pavlukhin created IGNITE-11398:
---
Summary: Remove leftover @RunWith(JUnit4.class)
Key: IGNITE-11398
URL: https://issues.apache.org/jira/browse/IGNITE-11398
Project: Ignite
Issue Type
Ivan Pavlukhin created IGNITE-11503:
---
Summary: MVCC: Handle partition loss policies
Key: IGNITE-11503
URL: https://issues.apache.org/jira/browse/IGNITE-11503
Project: Ignite
Issue Type
Ivan Pavlukhin created IGNITE-11534:
---
Summary: Partition loss policy is not handled properly for
implicit single key transactions
Key: IGNITE-11534
URL: https://issues.apache.org/jira/browse/IGNITE-11534
Ivan Pavlukhin created IGNITE-11808:
---
Summary: Scale test execution time constant along in
IgniteCacheCrossCacheTxFailoverTest
Key: IGNITE-11808
URL: https://issues.apache.org/jira/browse/IGNITE-11808
Ivan Pavlukhin created IGNITE-11888:
---
Summary:
CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup
fails on GG TC
Key: IGNITE-11888
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Pavlukhin created IGNITE-11901:
---
Summary: CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple
is flaky
Key: IGNITE-11901
URL: https://issues.apache.org/jira/browse/IGNITE-11901
Project
Ivan Pavlukhin created IGNITE-11908:
---
Summary: OOM in MVCC PDS4
Key: IGNITE-11908
URL: https://issues.apache.org/jira/browse/IGNITE-11908
Project: Ignite
Issue Type: Bug
Ivan Pavlukhin created IGNITE-11933:
---
Summary: Build scalar scaladoc only if javadoc profile is active
Key: IGNITE-11933
URL: https://issues.apache.org/jira/browse/IGNITE-11933
Project: Ignite
Ivan Pavlukhin created IGNITE-11940:
---
Summary: MVCC
SysPropWalDeltaConsistencyTest.testPutRemoveMultinode fails frequently
Key: IGNITE-11940
URL: https://issues.apache.org/jira/browse/IGNITE-11940
Ivan Pavlukhin created IGNITE-11946:
---
Summary: Do not add java.transaction module in Ignite launch
scripts
Key: IGNITE-11946
URL: https://issues.apache.org/jira/browse/IGNITE-11946
Project: Ignite
Ivan Pavlukhin created IGNITE-11948:
---
Summary: Row count statistics tests fail frequently
Key: IGNITE-11948
URL: https://issues.apache.org/jira/browse/IGNITE-11948
Project: Ignite
Issue
Ivan Pavlukhin created IGNITE-11951:
---
Summary: Set ThreadLocal node name only once in JdkMarshaller
Key: IGNITE-11951
URL: https://issues.apache.org/jira/browse/IGNITE-11951
Project: Ignite
Ivan Pavlukhin created IGNITE-11996:
---
Summary: Assertion error in
IgniteCacheOffheapManagerImpl#destroyCacheDataStore
Key: IGNITE-11996
URL: https://issues.apache.org/jira/browse/IGNITE-11996
Ivan Pavlukhin created IGNITE-12000:
---
Summary: IgniteSqlQueryMinMaxTest is flaky
Key: IGNITE-12000
URL: https://issues.apache.org/jira/browse/IGNITE-12000
Project: Ignite
Issue Type: Bug
Ivan Pavlukhin created IGNITE-12001:
---
Summary: SchemaExchangeSelfTest.testServerRestartWithNewTypes is
flaky
Key: IGNITE-12001
URL: https://issues.apache.org/jira/browse/IGNITE-12001
Project
Ivan Pavlukhin created IGNITE-12003:
---
Summary: Java thin client fails to get object with compact footer
from cache
Key: IGNITE-12003
URL: https://issues.apache.org/jira/browse/IGNITE-12003
Project
401 - 500 of 540 matches
Mail list logo
