Sorry, Dmitiry, I meant Ignite, not GridGain (memories of pre-apache
coding). I am assuming that Alex Menshikov was referring to GridLongList
class in Ignite.
D.
On Mon, Mar 26, 2018 at 11:52 PM, Dmitry Pavlov
wrote:
> Hi Dmitriy, did you mean GridList?
>
> I don't
IGNITE-8034 done, I have added configuration flag.
However, I still have concerns about property naming:
Is this authentication going to be used for thin clients only, or for
classic client and server nodes as well?
On Tue, Mar 27, 2018 at 9:50 AM, Dmitry Pavlov
wrote:
>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3696
---
Hi Dmitriy, did you mean GridList?
I don't understand what does it mean GridGain compress.
вт, 27 мар. 2018 г. в 3:06, Dmitriy Setrakyan :
> Thanks, Alex.
>
> GridGain automatically compresses all the internal types. Somehow it looks
> like the GridLongList may have been
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3702
IGNITE-7884
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7884
Alternatively you can review and apply these
Sergey Kosarev created IGNITE-8053:
--
Summary: Exception during checkpoint concurrent changes in topology
Key: IGNITE-8053
URL: https://issues.apache.org/jira/browse/IGNITE-8053
Project: Ignite
Alexander Menshikov created IGNITE-8054:
---
Summary: Let serialize only valuable part of GridLongList
Key: IGNITE-8054
URL: https://issues.apache.org/jira/browse/IGNITE-8054
Project: Ignite
The ticket is created:
https://issues.apache.org/jira/browse/IGNITE-8054
2018-03-27 10:04 GMT+03:00 Dmitriy Setrakyan :
> Sorry, Dmitiry, I meant Ignite, not GridGain (memories of pre-apache
> coding). I am assuming that Alex Menshikov was referring to GridLongList
> class
>> page compression at rebalancing is a good idea even is we have problems
with storing on disc.
BTW, do we have or going to have rebalancing based on pages streaming
instead of entries streaming?
2018-03-27 3:03 GMT+03:00 Dmitriy Setrakyan :
> AG,
>
> I would also ask
Hi Folks,
Test is still failing on TC.
https://ci.ignite.apache.org/viewLog.html?buildId=1160178=buildResultsDiv=IgniteTests24Java8_IgnitePlatformNetCoreLinux
I suggest to mute it until fix is ready.Test is running in Basic Run All
subsets, so each commit will genereate TC failure email. What do
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/3703
IGNITE-7647
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7647
Alternatively you can review and apply these
GitHub user homich1991 opened a pull request:
https://github.com/apache/ignite/pull/3704
IGNITE-6879 and migration to spring-data 2.0.5.RELEASE
Fixed IGNITE-6879
Migrated to spring-data 2.0.5.RELEASE
Migrated to spring 5.0.4.RELEASE
Fixed overrided methods naming
Hi, Igniters!
Here are some news on our RPM packages initiative.
1. I’ve finished preliminary developing of Stage II version of RPM packages
[1]. Main “new feature” is — split design. Also I’ve added package.sh script
for automating package building process which will help organise
Andrey Aleksandrov created IGNITE-8055:
--
Summary: Sqline command !tables works incorrect for client node
Key: IGNITE-8055
URL: https://issues.apache.org/jira/browse/IGNITE-8055
Project: Ignite
Ivan Rakov created IGNITE-8057:
--
Summary: Execute WAL fsync preventively before checkpoint begin
Key: IGNITE-8057
URL: https://issues.apache.org/jira/browse/IGNITE-8057
Project: Ignite
Issue
I apologize for the previous message sent in hurry. It's imposible to
measure the difference between 'precise' and 'estimated' page memory usage
per cache unless we fully implement approach 2. Current model allows to
store objects from several caches in a single page.
2018-03-23 22:21 GMT+03:00
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2803
---
Igniters,
I've completed development of
https://issues.apache.org/jira/browse/IGNITE-7754. TeamCity state is ok.
Please, review my changes.
Please note that it will be possible to track time of WAL fsync on
checkpoint begin by *walCpRecordFsyncDuration *metric in "Checkpoint
started"
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/3705
ignite-8044: IgniteQueryGenerator.getOptions() method should properly
handle empty list of parameters.
You can merge this pull request into a Git repository by running:
$ git pull
Hi Igniters,
I’ve filtered report of master failures to find most failing tests.
Following is 5 failing suites and their frequently failed test with links
to TC.
Igniters, please reply who would like to pick up
- test failures context research,
- tickets creation
- and (the best option)
Github user homich1991 closed the pull request at:
https://github.com/apache/ignite/pull/3628
---
Bumping up.
Attached is my local inspections profile exported from Idea. Let's run the
first iteration and check if it differs significantly from other community
members.
--AG
2018-03-19 16:39 GMT+03:00 Petr Ivanov :
> Filed
Nick Jacobsen created IGNITE-8056:
-
Summary: Ignite Cassandra integration doesn't correctly handle
Inet4Address and Inet6Address objects
Key: IGNITE-8056
URL: https://issues.apache.org/jira/browse/IGNITE-8056
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3682
---
Petr,
I am confused. Do we already have Debian packages?
D.
On Tue, Mar 27, 2018 at 5:10 AM, Petr Ivanov wrote:
> Hi, Igniters!
>
>
> Here are some news on our RPM packages initiative.
>
> 1. I’ve finished preliminary developing of Stage II version of RPM
> packages [1].
Dmitriy,
I think it would make sense to create a ticket for every single one of
these, or at least try to group them in to several tickets. What do you
think?
D.
On Tue, Mar 27, 2018 at 5:17 AM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> I’ve filtered report of master
Dmitriy Pavlov created IGNITE-8058:
--
Summary:
GridMarshallerMappingConsistencyTest.testPersistedMappingsSharedOnJoin is
flaky in master
Key: IGNITE-8058
URL: https://issues.apache.org/jira/browse/IGNITE-8058
Hi Pavel,
.NET core tests are passing now.
Let me sincerely thank you for helping the community in keeping TC to be
green.
Best Regards,
Dmitriy Pavlov
вт, 27 мар. 2018 г. в 10:55, Pavel Tupitsyn :
> IGNITE-8034 done, I have added configuration flag.
>
> However, I still
Hi Vyacheslav,
Task is still actual. It is another question if it is a priority or not.
This is a task is about following case: a client node has near cache. Every
get operation is tracked and enlisted on server node. The server node must
trace the operation and accordingly store the results
Igniters,
I'm ready to take care of Apache Ignite 2.5 release.
I've started preparing wiki pages. There are many fixes in master
branch so I think that we should limit scope of the release soon (e.g.
next week) because stabilization and QA activities will also require
time.
I'll keep the
Andrey Aleksandrov created IGNITE-8060:
--
Summary: Sqline creating tables on client nodes works incorrect in
case if node shutdown
Key: IGNITE-8060
URL: https://issues.apache.org/jira/browse/IGNITE-8060
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/3706
Ignite 6807: validation of local queries on client
Added more meaningful handling of execution local queries on client node.
Local queries on client's local cache are still allowed.
Anton Dmitriev created IGNITE-8059:
--
Summary: Integrate decision tree with partition based dataset
Key: IGNITE-8059
URL: https://issues.apache.org/jira/browse/IGNITE-8059
Project: Ignite
Hello Ignite Community!
My name is Aleksey. I want to contribute to Apache Ignite and want to
start with this issue - IGNITE-8049 but I can't assign it to me, my JIRA
username astelmak. Any help on this will be appreciated.
Thanks!
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3567
---
Unfortunately, I don't have permission to create page for IEP on wiki.
Denis, can you grant it? My username is ilantukh.
On Mon, Mar 26, 2018 at 8:04 PM, Anton Vinogradov wrote:
> >> It is impossible to disable WAL only for certain partitions without
> >> completely overhauling
Denis, it seems noone is working.
чт, 22 мар. 2018 г. в 21:26, Denis Magda :
> Igniters,
>
> Is anybody working on this bug? There is a high chance we can add a fix to
> 2.5 if the community agrees to release it earlier.
>
> --
> Denis
>
> On Thu, Mar 15, 2018 at 11:04 AM,
Ivan, I have reviewed your changes, looks good.
On Tue, Mar 27, 2018 at 2:56 PM, Ivan Rakov wrote:
> Igniters,
>
> I've completed development of https://issues.apache.org/jira
> /browse/IGNITE-7754. TeamCity state is ok. Please, review my changes.
> Please note that it
Ivan, sure :)
Thank you for this contribution, merged to master.
вт, 27 мар. 2018 г. в 20:08, Ivan Rakov :
> Dmitry,
>
> Firstly PR contained dirty fix for performance measurement, but now it
> contains good fix. :) Sorry for inconvenience.
> I've renamed the PR.
>
> Best
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3707
IGNITE-8017
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8017
Alternatively you can review and apply these
Hi Igniters,
I've deleted this run config.
Sincerely,
Dmitriy Pavlov
пт, 23 мар. 2018 г. в 13:50, Petr Ivanov :
> No objections then.
>
>
>
> > On 23 Mar 2018, at 13:03, Dmitry Pavlov wrote:
> >
> > Hi Dmitriy,
> >
> > Thank you for this
Andrey, it's great to see you in a role of 2.5 release engineer! Thanks for
stepping in.
--
Denis
On Tue, Mar 27, 2018 at 8:42 AM, Andrey Gura wrote:
> Igniters,
>
> I'm ready to take care of Apache Ignite 2.5 release.
>
> I've started preparing wiki pages. There are many
Alexey, thank you for bring this topic to top.
What do you think about committing this inspections into Ignite code base?
What can be our next steps after demonstrating CI check is possible
Hi Petr,
Could you please take inspections and run it on AI code base in
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
?
Sincerely,
Dmitriy Pavlov
вт, 27 мар. 2018 г. в 19:27, Dmitry Pavlov
Ilya, granted you all the required permissions. Please let me know if you
still have troubles with the wiki.
--
Denis
On Tue, Mar 27, 2018 at 8:56 AM, Ilya Lantukh wrote:
> Unfortunately, I don't have permission to create page for IEP on wiki.
> Denis, can you grant it?
Hi Eduard, thank you for review.
Hi Ivan,
I'm confused on PR naming
https://github.com/apache/ignite/pull/3656
Could you rename?
Sincerely,
Dmitriy Pavlov
вт, 27 мар. 2018 г. в 19:38, Eduard Shangareev :
> Ivan, I have reviewed your changes, looks good.
>
> On
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3656
---
Hello Alexey,
Welcome to the Ignite community! I've added you to the contributors list,
you should be now able to assign the JIRA ticket.
--AG
2018-03-27 18:42 GMT+03:00 Spider (Alexey) :
> Hello Ignite Community!
>
> My name is Aleksey. I want to contribute to Apache
Dmitry,
Firstly PR contained dirty fix for performance measurement, but now it
contains good fix. :) Sorry for inconvenience.
I've renamed the PR.
Best Regards,
Ivan Rakov
On 27.03.2018 19:40, Dmitry Pavlov wrote:
Hi Eduard, thank you for review.
Hi Ivan,
I'm confused on PR naming
Hello all
Thank you, Alexey!
>Вторник, 27 марта 2018, 21:57 +06:00 от Alexey Goncharuk
>:
>
>Hello Alexey,
>
>Welcome to the Ignite community! I've added you to the contributors list,
>you should be now able to assign the JIRA ticket.
>
>--AG
>
>2018-03-27 18:42
Github user Mmuzaf closed the pull request at:
https://github.com/apache/ignite/pull/3618
---
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/3709
-
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5979
Alternatively you can review and apply these changes as the
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/3708
IGNITE-4193: Added transaction support for ODBC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4193
When client node performs get it stores information about itself on server
node, so-called 'reader'.
If another node updates cache entry, server node uses 'reader' info(because it
tracks client info) to find client and update cache entry in client's near
cache.
PS. obviously, there may be
Dmitry, thanks, but I'm not sure that I correctly understood you.
>> Every get operation is tracked and enlisted on server node.
What does it mean? Is it about metrics?
On Tue, Mar 27, 2018 at 6:29 PM, Dmitry Pavlov wrote:
> Hi Vyacheslav,
>
>
> Task is still actual. It
Hi, Denis Mekhanikov!
As far as I know, Ignite services are based on IgniteCache and we have
all its features. We can use listeners or continuous queries for
deployment synchronizations.
Why do you want using the discovery layer for that?
One more thing: we can use baseline approach for
Hi Alexey, thank you for stepping in and explaining.
вт, 27 мар. 2018 г. в 23:32, ALEKSEY KUZNETSOV :
> When client node performs get it stores information about itself on server
> node, so-called 'reader'.
> If another node updates cache entry, server node uses
Its kind of improvement. I'm not sure if it can reduce overall used memory,
but probably will decrease GC pauses.
ср, 28 мар. 2018 г. в 0:09, Vyacheslav Daradur :
> Aleksey, thank you, it's clear now.
>
> If this task is really about moving reader's information to off-heap:
Aleksey, thank you, it's clear now.
If this task is really about moving reader's information to off-heap:
do we have issues with the current implementation (e.g. at restarting)
or this task is kind of improvement?
On Tue, Mar 27, 2018 at 11:32 PM, ALEKSEY KUZNETSOV
59 matches
Mail list logo