date:20190816

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Павлухин Иван

Dmitriy,

I cherry-picked fix for
https://issues.apache.org/jira/browse/IGNITE-12068 to 2.7.6. Bot visa
seems good comparing to 2.7.6 but there are some reported blockers. It
would be great if someone can double-check it. If something is wrong
you may consider a revert.

пт, 16 авг. 2019 г. в 18:22, Dmitriy Pavlov :
>
> Hi Igniters,
>
> I also suggest adding newly created critical bug into scope
> https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned since
> it was discussed before in private communication).
>
> It is not a regression but can cause data corruption, so I'd rather wait
> for the fix.
>
> Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> during the weekend, so I would be grateful if fixes can be cherry-piked to
> the branch today. Also, since narrow time limit, please trigger Run All
> after each commit in 2.7.6. This will allow to immediately locate which
> commit caused test failure.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>
> > Hi Ivan,
> >
> > yes, sure.
> >
> > If it is cherry-picked without conflicts, just push it.
> >
> >  If it contains conflicts it is better to push to 2.7.6-based branch and
> > start additional run-all, example
> > https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> > base: 2.7.6
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> >
> >> Dmitriy,
> >>
> >> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
> >>
> >> Should I cherry-pick it to release branch?
> >>
> >> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >> >
> >> > Hi Igniters,
> >> >
> >> > Yesterday was a planned date of code freeze.
> >> >
> >> > So the scope (related both to features and to bugs) is final, we're
> >> > entering to stabilization phase. Nothing can be included into scope
> >> besides
> >> > blockers approved by the release manager.
> >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >> > 
> >> >
> >> > Unresolved tickets are:
> >> > IGNITE-12071  Eduard Shangareev
> >> > IGNITE-12068 Ivan Pavlukhin
> >> > IGNITE-9562 Eduard Shangareev
> >> > IGNITE-12057 Anton Kalashnikov
> >> > IGNITE-12061 Stanilovsky Evgeny
> >> >
> >> > Sincerely,
> >> > Dmitriy Pavlov
> >> >
> >> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
> >> >
> >> > > Dmitriy, review passed, plz proceed.
> >> > > thanks !
> >> > >
> >> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> >> > > > nobody
> >> > > > volunteer to complete the task.
> >> > > >
> >> > > > Evgeniy, please keep me updated about IGNITE-12061.
> >> > > >
> >> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >> > > >  >> > > >> :
> >> > > >
> >> > > >> yep, i`l try to call someone who probably familiar with this
> >> problem.
> >> > > >>
> >> > > >> >
> >> > > >> >
> >> > > >> >Ok, I've removed Spark from the scope.
> >> > > >> >
> >> > > >> >What about the unassigned issue related to ODBC? It is not
> >> looking like
> >> > > >> >somebody will fix it before release.
> >> > > >> >
> >> > > >> >Evgeniy Stanilovsky, what about
> >> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >> > > >> ><
> >> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >> > > >> >do you have someone to review the fix?
> >> > > >> >
> >> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >> > > >> >
> >> > > >> >> Dmitry,
> >> > > >> >>
> >> > > >> >> It would be better for us to put off the Spark upgrade until
> >> 2.8 as
> >> > > >> Nikolay
> >> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> >> roll out
> >> > > >> fixes
> >> > > >> >> for the critical issues from the scope.
> >> > > >> >>
> >> > > >> >>
> >> > > >> >> -
> >> > > >> >> Denis
> >> > > >> >>
> >> > > >> >>
> >> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> >> dpav...@apache.org
> >> > > >
> >> > > >> wrote:
> >> > > >> >>
> >> > > >> >> > Nikolay, how long does it take to update? I will be traveling
> >> > > from
> >> > > >> 28
> >> > > >> Aug
> >> > > >> >> > till 16 Sept. We can select new dates for release if the
> >> majority
> >> > > >> of
> >> > > >> >> fixes
> >> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
> >> share
> >> > > >> your
> >> > > >> >> > vision about selecting new dates.
> >> > > >> >> >
> >> > > >> >> > *Voting Date: *Sept 18, 2019
> >> > > >> >> >
> >> > > >> >> > *Release Date: *Sept 23, 2019
> >> > > >> >> >
> >> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> > > >> >> > <
> >> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >> > >
> >> > > >> >
> >> > > >> is
> >> > > >> >> > still
> >> > > >> >> > unassigned: Server node prints exception when ODBC driver
> >> > > >> disconnects
> >> > > >> >> > Igniters, who would like to pick

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Igniters,

I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned since
it was discussed before in private communication).

It is not a regression but can cause data corruption, so I'd rather wait
for the fix.

Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
during the weekend, so I would be grateful if fixes can be cherry-piked to
the branch today. Also, since narrow time limit, please trigger Run All
after each commit in 2.7.6. This will allow to immediately locate which
commit caused test failure.

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :

> Hi Ivan,
>
> yes, sure.
>
> If it is cherry-picked without conflicts, just push it.
>
>  If it contains conflicts it is better to push to 2.7.6-based branch and
> start additional run-all, example
> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> base: 2.7.6
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
>
>> Dmitriy,
>>
>> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
>>
>> Should I cherry-pick it to release branch?
>>
>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>> >
>> > Hi Igniters,
>> >
>> > Yesterday was a planned date of code freeze.
>> >
>> > So the scope (related both to features and to bugs) is final, we're
>> > entering to stabilization phase. Nothing can be included into scope
>> besides
>> > blockers approved by the release manager.
>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>> > 
>> >
>> > Unresolved tickets are:
>> > IGNITE-12071  Eduard Shangareev
>> > IGNITE-12068 Ivan Pavlukhin
>> > IGNITE-9562 Eduard Shangareev
>> > IGNITE-12057 Anton Kalashnikov
>> > IGNITE-12061 Stanilovsky Evgeny
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>> >
>> > > Dmitriy, review passed, plz proceed.
>> > > thanks !
>> > >
>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
>> > > > nobody
>> > > > volunteer to complete the task.
>> > > >
>> > > > Evgeniy, please keep me updated about IGNITE-12061.
>> > > >
>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>> > > > > > > >> :
>> > > >
>> > > >> yep, i`l try to call someone who probably familiar with this
>> problem.
>> > > >>
>> > > >> >
>> > > >> >
>> > > >> >Ok, I've removed Spark from the scope.
>> > > >> >
>> > > >> >What about the unassigned issue related to ODBC? It is not
>> looking like
>> > > >> >somebody will fix it before release.
>> > > >> >
>> > > >> >Evgeniy Stanilovsky, what about
>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
>> > > >> ><
>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>> > > >> >do you have someone to review the fix?
>> > > >> >
>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
>> > > >> >
>> > > >> >> Dmitry,
>> > > >> >>
>> > > >> >> It would be better for us to put off the Spark upgrade until
>> 2.8 as
>> > > >> Nikolay
>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
>> roll out
>> > > >> fixes
>> > > >> >> for the critical issues from the scope.
>> > > >> >>
>> > > >> >>
>> > > >> >> -
>> > > >> >> Denis
>> > > >> >>
>> > > >> >>
>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
>> dpav...@apache.org
>> > > >
>> > > >> wrote:
>> > > >> >>
>> > > >> >> > Nikolay, how long does it take to update? I will be traveling
>> > > from
>> > > >> 28
>> > > >> Aug
>> > > >> >> > till 16 Sept. We can select new dates for release if the
>> majority
>> > > >> of
>> > > >> >> fixes
>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
>> share
>> > > >> your
>> > > >> >> > vision about selecting new dates.
>> > > >> >> >
>> > > >> >> > *Voting Date: *Sept 18, 2019
>> > > >> >> >
>> > > >> >> > *Release Date: *Sept 23, 2019
>> > > >> >> >
>> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
>> > > >> >> > <
>> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
>> > >
>> > > >> >
>> > > >> is
>> > > >> >> > still
>> > > >> >> > unassigned: Server node prints exception when ODBC driver
>> > > >> disconnects
>> > > >> >> > Igniters, who would like to pick up it? By default, I'm going
>> to
>> > > >> remove
>> > > >> >> it
>> > > >> >> > from release
>> > > >> >> >
>> > > >> >> >
>> > > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
>> nizhi...@apache.org
>> > >
>> > > >> >:
>> > > >> >> >
>> > > >> >> > > Hello, Igniters.
>> > > >> >> > >
>> > > >> >> > > I try to upgrade Spark version but failed.
>> > > >> >> > >
>> > > >> >> > > Seems, internal Spark API(External Catalog, SQL planner)
>> that
>> > > we
>> > > >> use
>> > > >> >> > > changed a lot.
>> > > >> >> > > So it will take some time to upgrade version.
>> > > >> >> > >
>> > > >> >> >

[jira] [Created] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

2019-08-16 Thread Dmitriy Govorukhin (JIRA)

Dmitriy Govorukhin created IGNITE-12081:
---

 Summary: Page replacement can reload invalid page during checkpoint
 Key: IGNITE-12081
 URL: https://issues.apache.org/jira/browse/IGNITE-12081
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin


There is a race between {{writeCheckpointPages}} and page replacement process:
 * Checkpointer thread begins a checkpoint
 * Checkpointer thread calls {{getPageForCheckpoint()}}, which will copy page 
content *and clear dirty flag*
 * Page replacement tries to find a page for replacement and chooses this page, 
the page is thrown away
 * Before the page is written back to the store, the page is acquired again.

As a result, an older copy of the page is brought back to memory, which causes 
all kinds of corruption exceptions and assertions.

The attached unit test demonstrates the issue. It is likely that all baselines 
are affected starting from 2.4

As a part of this ticket, we must add more unit-tests for checkpointing 
protocol invariants we rely on.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (IGNITE-12080) Add extended logging for rebalance

2019-08-16 Thread Kirill Tkalenko (JIRA)

Kirill Tkalenko created IGNITE-12080:


 Summary: Add extended logging for rebalance
 Key: IGNITE-12080
 URL: https://issues.apache.org/jira/browse/IGNITE-12080
 Project: Ignite
  Issue Type: Improvement
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko


We should log all information about finished rebalance on demander node.
I'd have in log:
h3. Total information:
# Rebalance duration, rebalance start time/rebalance finish time
# How many partitions were processed in each topic (number of paritions, number 
of entries, number of bytes)
# How many nodes were suppliers in rebalance (nodeId, number of supplied 
paritions, number of supplied entries, number of bytes, duraton of getting and 
processing partitions from supplier)

h3. Information per cache group:
# Rebalance duration, rebalance start time/rebalance finish time
# How many partitions were processed in each topic (number of paritions, number 
of entries, number of bytes)
# How many nodes were suppliers in rebalance (nodeId, number of supplied 
paritions, list of partition ids with PRIMARY/BACKUP flag, number of supplied 
entries, number of bytes, duraton of getting and processing partitions from 
supplier)
# Information about each partition distribution (list of nodeIds with 
primary/backup flag and marked supplier nodeId)

h3. Information per supplier node:
# How many paritions were requested: 
#* Total number
#* Primary/backup distribution (number of primary partitions, number of backup 
partitions)
#* Total number of entries
#* Total size partitions in bytes
# How many paritions were requested per cache group:
#* Number of requested partitions
#* Number of entries in partitions
#* Total size of partitions in bytes
#* List of requested partitions with size in bytes, count entries, primary or 
backup partition flag



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Ivan,

yes, sure.

If it is cherry-picked without conflicts, just push it.

 If it contains conflicts it is better to push to 2.7.6-based branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562, base:
2.7.6

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :

> Dmitriy,
>
> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
>
> Should I cherry-pick it to release branch?
>
> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >
> > Hi Igniters,
> >
> > Yesterday was a planned date of code freeze.
> >
> > So the scope (related both to features and to bugs) is final, we're
> > entering to stabilization phase. Nothing can be included into scope
> besides
> > blockers approved by the release manager.
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > 
> >
> > Unresolved tickets are:
> > IGNITE-12071  Eduard Shangareev
> > IGNITE-12068 Ivan Pavlukhin
> > IGNITE-9562 Eduard Shangareev
> > IGNITE-12057 Anton Kalashnikov
> > IGNITE-12061 Stanilovsky Evgeny
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
> >
> > > Dmitriy, review passed, plz proceed.
> > > thanks !
> > >
> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > > > nobody
> > > > volunteer to complete the task.
> > > >
> > > > Evgeniy, please keep me updated about IGNITE-12061.
> > > >
> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > > >  > > >> :
> > > >
> > > >> yep, i`l try to call someone who probably familiar with this
> problem.
> > > >>
> > > >> >
> > > >> >
> > > >> >Ok, I've removed Spark from the scope.
> > > >> >
> > > >> >What about the unassigned issue related to ODBC? It is not looking
> like
> > > >> >somebody will fix it before release.
> > > >> >
> > > >> >Evgeniy Stanilovsky, what about
> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > > >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro
> >
> > > >> >do you have someone to review the fix?
> > > >> >
> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > > >> >
> > > >> >> Dmitry,
> > > >> >>
> > > >> >> It would be better for us to put off the Spark upgrade until 2.8
> as
> > > >> Nikolay
> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> roll out
> > > >> fixes
> > > >> >> for the critical issues from the scope.
> > > >> >>
> > > >> >>
> > > >> >> -
> > > >> >> Denis
> > > >> >>
> > > >> >>
> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> dpav...@apache.org
> > > >
> > > >> wrote:
> > > >> >>
> > > >> >> > Nikolay, how long does it take to update? I will be traveling
> > > from
> > > >> 28
> > > >> Aug
> > > >> >> > till 16 Sept. We can select new dates for release if the
> majority
> > > >> of
> > > >> >> fixes
> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
> share
> > > >> your
> > > >> >> > vision about selecting new dates.
> > > >> >> >
> > > >> >> > *Voting Date: *Sept 18, 2019
> > > >> >> >
> > > >> >> > *Release Date: *Sept 23, 2019
> > > >> >> >
> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > > >> >> > <
> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> > >
> > > >> >
> > > >> is
> > > >> >> > still
> > > >> >> > unassigned: Server node prints exception when ODBC driver
> > > >> disconnects
> > > >> >> > Igniters, who would like to pick up it? By default, I'm going
> to
> > > >> remove
> > > >> >> it
> > > >> >> > from release
> > > >> >> >
> > > >> >> >
> > > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
> nizhi...@apache.org
> > >
> > > >> >:
> > > >> >> >
> > > >> >> > > Hello, Igniters.
> > > >> >> > >
> > > >> >> > > I try to upgrade Spark version but failed.
> > > >> >> > >
> > > >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> > > we
> > > >> use
> > > >> >> > > changed a lot.
> > > >> >> > > So it will take some time to upgrade version.
> > > >> >> > >
> > > >> >> > > For now, I work hard to complete the second phase of IEP-35
> so I
> > > >> >> postpone
> > > >> >> > > upgrade Spark version to Ignite 2.8.
> > > >> >> > >
> > > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > > >> >> > > > Hi Denis,
> > > >> >> > > >
> > > >> >> > > > Sure, since code freeze is planned for today, I don't mind
> to
> > > >> include
> > > >> >> > > this
> > > >> >> > > > bug.
> > > >> >> > > >
> > > >> >> > > > Ivan, could you complete this issue by 20 August?
> > > >> >> > > >
> > > >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> > > >> >> > > >
> > > >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> > > >> >> > > >
> > > >> >> > > > BTW #2, FYI, release page is now available here
> > > >> >> > > >
> > > >> >>
> > > >>
>

[jira] [Created] (IGNITE-12079) [ML][Umbrella] Add advanced preprocessing techniques

2019-08-16 Thread Aleksey Zinoviev (JIRA)

Aleksey Zinoviev created IGNITE-12079:
-

 Summary: [ML][Umbrella] Add advanced preprocessing techniques
 Key: IGNITE-12079
 URL: https://issues.apache.org/jira/browse/IGNITE-12079
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Affects Versions: 2.8
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev
 Fix For: 2.8


*Main goal:*

To reduce the gap between Apache Spark and Apache Ignite in preprocessing 
operations. The reducing of the gap could help with loading Spark ML Pipelines 
to Ignite ML.

 

Next steps:
 # Add Frequency Encoder
 # Add two Imputing Strategies (MIN, MAX, COUNT, MOST_FREQUENT, LEAST_FREQUENT)
 # Add RobustScaler (will be added in Spark 3.0)
 # Add CountVectorizer
 # Add FeatureHasher
 # Add QuantileDiscretizer
 # Add Locality Sensitive Hashing (LSH)
 # Add LabelEncoder
 # Add RevertStringIndexing
 # Add multi-column preprocessor



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Павлухин Иван

Dmitriy,

We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068

Should I cherry-pick it to release branch?

пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>
> Hi Igniters,
>
> Yesterday was a planned date of code freeze.
>
> So the scope (related both to features and to bugs) is final, we're
> entering to stabilization phase. Nothing can be included into scope besides
> blockers approved by the release manager.
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> 
>
> Unresolved tickets are:
> IGNITE-12071  Eduard Shangareev
> IGNITE-12068 Ivan Pavlukhin
> IGNITE-9562 Eduard Shangareev
> IGNITE-12057 Anton Kalashnikov
> IGNITE-12061 Stanilovsky Evgeny
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>
> > Dmitriy, review passed, plz proceed.
> > thanks !
> >
> > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > > nobody
> > > volunteer to complete the task.
> > >
> > > Evgeniy, please keep me updated about IGNITE-12061.
> > >
> > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >  > >> :
> > >
> > >> yep, i`l try to call someone who probably familiar with this problem.
> > >>
> > >> >
> > >> >
> > >> >Ok, I've removed Spark from the scope.
> > >> >
> > >> >What about the unassigned issue related to ODBC? It is not looking like
> > >> >somebody will fix it before release.
> > >> >
> > >> >Evgeniy Stanilovsky, what about
> > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> >do you have someone to review the fix?
> > >> >
> > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > >> >
> > >> >> Dmitry,
> > >> >>
> > >> >> It would be better for us to put off the Spark upgrade until 2.8 as
> > >> Nikolay
> > >> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> > >> fixes
> > >> >> for the critical issues from the scope.
> > >> >>
> > >> >>
> > >> >> -
> > >> >> Denis
> > >> >>
> > >> >>
> > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org
> > >
> > >> wrote:
> > >> >>
> > >> >> > Nikolay, how long does it take to update? I will be traveling
> > from
> > >> 28
> > >> Aug
> > >> >> > till 16 Sept. We can select new dates for release if the majority
> > >> of
> > >> >> fixes
> > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> > >> your
> > >> >> > vision about selecting new dates.
> > >> >> >
> > >> >> > *Voting Date: *Sept 18, 2019
> > >> >> >
> > >> >> > *Release Date: *Sept 23, 2019
> > >> >> >
> > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > >> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >
> > >> >
> > >> is
> > >> >> > still
> > >> >> > unassigned: Server node prints exception when ODBC driver
> > >> disconnects
> > >> >> > Igniters, who would like to pick up it? By default, I'm going to
> > >> remove
> > >> >> it
> > >> >> > from release
> > >> >> >
> > >> >> >
> > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
> >
> > >> >:
> > >> >> >
> > >> >> > > Hello, Igniters.
> > >> >> > >
> > >> >> > > I try to upgrade Spark version but failed.
> > >> >> > >
> > >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> > we
> > >> use
> > >> >> > > changed a lot.
> > >> >> > > So it will take some time to upgrade version.
> > >> >> > >
> > >> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> > >> >> postpone
> > >> >> > > upgrade Spark version to Ignite 2.8.
> > >> >> > >
> > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > >> >> > > > Hi Denis,
> > >> >> > > >
> > >> >> > > > Sure, since code freeze is planned for today, I don't mind to
> > >> include
> > >> >> > > this
> > >> >> > > > bug.
> > >> >> > > >
> > >> >> > > > Ivan, could you complete this issue by 20 August?
> > >> >> > > >
> > >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> > >> >> > > >
> > >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> > >> >> > > >
> > >> >> > > > BTW #2, FYI, release page is now available here
> > >> >> > > >
> > >> >>
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> > >> >> > > >
> > >> >> > > > BTW #3, FYI, release related test PR is here
> > >> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> > >> report is
> > >> >> > > here:
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> > https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org
> > >:
> > >> >> > > >
> > >> >> > > > > An Ignite user just reported a silly issue that needs to be
> > >> fixed
> > >> >> in
> > >> >>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Igniters,

Yesterday was a planned date of code freeze.

So the scope (related both to features and to bugs) is final, we're
entering to stabilization phase. Nothing can be included into scope besides
blockers approved by the release manager.
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process


Unresolved tickets are:
IGNITE-12071  Eduard Shangareev
IGNITE-12068 Ivan Pavlukhin
IGNITE-9562 Eduard Shangareev
IGNITE-12057 Anton Kalashnikov
IGNITE-12061 Stanilovsky Evgeny

Sincerely,
Dmitriy Pavlov

чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :

> Dmitriy, review passed, plz proceed.
> thanks !
>
> > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > nobody
> > volunteer to complete the task.
> >
> > Evgeniy, please keep me updated about IGNITE-12061.
> >
> > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >  >> :
> >
> >> yep, i`l try to call someone who probably familiar with this problem.
> >>
> >> >
> >> >
> >> >Ok, I've removed Spark from the scope.
> >> >
> >> >What about the unassigned issue related to ODBC? It is not looking like
> >> >somebody will fix it before release.
> >> >
> >> >Evgeniy Stanilovsky, what about
> >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >> >do you have someone to review the fix?
> >> >
> >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >> >
> >> >> Dmitry,
> >> >>
> >> >> It would be better for us to put off the Spark upgrade until 2.8 as
> >> Nikolay
> >> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> >> fixes
> >> >> for the critical issues from the scope.
> >> >>
> >> >>
> >> >> -
> >> >> Denis
> >> >>
> >> >>
> >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org
> >
> >> wrote:
> >> >>
> >> >> > Nikolay, how long does it take to update? I will be traveling
> from
> >> 28
> >> Aug
> >> >> > till 16 Sept. We can select new dates for release if the majority
> >> of
> >> >> fixes
> >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> >> your
> >> >> > vision about selecting new dates.
> >> >> >
> >> >> > *Voting Date: *Sept 18, 2019
> >> >> >
> >> >> > *Release Date: *Sept 23, 2019
> >> >> >
> >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
>
> >> >
> >> is
> >> >> > still
> >> >> > unassigned: Server node prints exception when ODBC driver
> >> disconnects
> >> >> > Igniters, who would like to pick up it? By default, I'm going to
> >> remove
> >> >> it
> >> >> > from release
> >> >> >
> >> >> >
> >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
>
> >> >:
> >> >> >
> >> >> > > Hello, Igniters.
> >> >> > >
> >> >> > > I try to upgrade Spark version but failed.
> >> >> > >
> >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> we
> >> use
> >> >> > > changed a lot.
> >> >> > > So it will take some time to upgrade version.
> >> >> > >
> >> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> >> >> postpone
> >> >> > > upgrade Spark version to Ignite 2.8.
> >> >> > >
> >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> >> >> > > > Hi Denis,
> >> >> > > >
> >> >> > > > Sure, since code freeze is planned for today, I don't mind to
> >> include
> >> >> > > this
> >> >> > > > bug.
> >> >> > > >
> >> >> > > > Ivan, could you complete this issue by 20 August?
> >> >> > > >
> >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> >> >> > > >
> >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> >> >> > > >
> >> >> > > > BTW #2, FYI, release page is now available here
> >> >> > > >
> >> >>
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> >> >> > > >
> >> >> > > > BTW #3, FYI, release related test PR is here
> >> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> >> report is
> >> >> > > here:
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> >> >> > > >
> >> >> > > >
> >> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org
> >:
> >> >> > > >
> >> >> > > > > An Ignite user just reported a silly issue that needs to be
> >> fixed
> >> >> in
> >> >> > > 2.7.6:
> >> >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
> >> >> > > > >
> >> >> > > > > More details and context:
> >> >> > > > >
> >> >> > > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
> >> >> > > > >
> >> >> > > > > Ivan, please help us to make it to the release.
> >> >> > > > >
> >> >> > > > > -
> >> >> > > > > Denis
> >> >> > > > >
> >> >> > > > >
> >> >> > >

[jira] [Created] (IGNITE-12078) implement loadCache on CacheJdbcBlobStore

2019-08-16 Thread Luca (JIRA)

Luca created IGNITE-12078:
-

 Summary: implement loadCache on CacheJdbcBlobStore
 Key: IGNITE-12078
 URL: https://issues.apache.org/jira/browse/IGNITE-12078
 Project: Ignite
  Issue Type: Task
Reporter: Luca


When store a cache persistent in a 3rd Party Storage as Blob the 
CacheJdbcBlobStoreFactory is used. According to the documentation 
([https://apacheignite.readme.io/v1.9/docs/persistent-store#section-loadcache-] 
/ [https://apacheignite.readme.io/docs/data-loading#ignitecacheloadcache]) the 
method loadCache() should be used to load the data from the persistent storage 
back to the cache.

Unfortunately the loadCache() method is only implemented in the 
CacheJdbcPojoStore but not in the CacheJdbcBlobStore.

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[jira] [Created] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

[jira] [Created] (IGNITE-12080) Add extended logging for rebalance

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[jira] [Created] (IGNITE-12079) [ML][Umbrella] Add advanced preprocessing techniques

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[jira] [Created] (IGNITE-12078) implement loadCache on CacheJdbcBlobStore

9 matches

Site Navigation

Mail list logo

Footer information