Re: How a new index is built in runtime?

Denis, We iterate over the whole cache and build the index entry-by-entry. Control is returned back to the user when index is ready. On Fri, Aug 18, 2017 at 9:50 AM, Yakov Zhdanov wrote: > Of course, iteration should have an option to be run from more than 1 > thread. What

Re: Data compression in Ignite 2.0

Hi Vyacheslav, Yes, I would suggest you to do so. On Fri, Aug 25, 2017 at 2:51 PM, Vyacheslav Daradur wrote: > Hi, should I close the initial ticket [1] as "Won't Fix" and add link to > the new discusion about storage compression [2] in comments? > > [1]

Re: Ignite not friendly for Monitoring

IGNITE-5620 is about error codes thrown from drivers. This is completely different story, as every driver has specification with it's own specific error codes. There is no common denominator. On Thu, Aug 17, 2017 at 11:10 PM, Denis Magda wrote: > Vladimir, > > I would

[GitHub] ignite pull request #2523: IGNITE-6115: Ignore page eviction mode if Ignite ...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2523 IGNITE-6115: Ignore page eviction mode if Ignite persistence is enabled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite

[GitHub] ignite pull request #2525: IGNITE-5425 JDBC thin: don't throw unsupported ex...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2525 IGNITE-5425 JDBC thin: don't throw unsupported exception on ClientInf… …o methods You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2184: IGNITE-5425 JDBC thin: support client info

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2184 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] ignite pull request #2524: Ignite 5714

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2524 Ignite 5714 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5714 Alternatively you can review and apply these changes as

Re: [DISCUSSION] Urgent Ignite bug fix release

One more example of possible warning: - Excessive memory usage by Ignite node process (performance may drop) [requested=44613MB, available=15942MB]. Please tune the folowing settings as suggested: MemoryPolicyConfiguration.initialSize for

[GitHub] ignite pull request #2526: IGNITE-6184 Add checkClusterState() call to destr...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2526 IGNITE-6184 Add checkClusterState() call to destroyCachesAsync() and … …getOrCreateCaches() You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2527: IGNITE-5814 Remove non Ignite classes from marsha...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2527 IGNITE-5814 Remove non Ignite classes from marshaller exclusions You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: [DISCUSSION] Urgent Ignite bug fix release

Looks good, but why in the example provided are we suggesting 8GB? 2 nodes with 8GB will completely exhaust the available memory. I would suggest 6 or 7GB. Also, why 100MB for default policy. Anything under 1GB seems too small. Can you please comment? D. On Mon, Aug 28, 2017 at 3:31 AM,

Re: [DISCUSSION] Urgent Ignite bug fix release

The suggestion here is based on initial settings, and it's so because there is no other nodes on the host in the example. The algorithm tries to preserve the original ratio of memory policies keeping numbers reasonable (for example after some thresshold it will suggest not to use several memory

[jira] [Created] (IGNITE-6195) SQL: Do not allow JOINs on caches with different affinity functions

Vladimir Ozerov created IGNITE-6195: --- Summary: SQL: Do not allow JOINs on caches with different affinity functions Key: IGNITE-6195 URL: https://issues.apache.org/jira/browse/IGNITE-6195 Project:

[jira] [Created] (IGNITE-6200) org.dom4j.QName can't be serialized

Alexei Scherbakov created IGNITE-6200: - Summary: org.dom4j.QName can't be serialized Key: IGNITE-6200 URL: https://issues.apache.org/jira/browse/IGNITE-6200 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6201) SQL: support merge join

Vladimir Ozerov created IGNITE-6201: --- Summary: SQL: support merge join Key: IGNITE-6201 URL: https://issues.apache.org/jira/browse/IGNITE-6201 Project: Ignite Issue Type: Task

Re: [DISCUSSION] Urgent Ignite bug fix release

Ok, the check happens at the node start time or on NODE_JOIN event in general it looks like: 1) calculate expected used memory = heap max + system cache max + all custom policies max + default policy size and put it into a node attribute 2) get total physycal memory, calculate expected safe to

Re: Cluster auto activation design proposal

Dmitriy, It was my misunderstanding, I believe that setter is not enough and we need a full-fledged entity. We should also be able to check if BLTs are compatible. Interface looks like this and use case for this functionality is described below. interface BaselineTopology { Collection

Re: Cluster auto activation design proposal

Sergey, the interface you are suggesting is internal, not external. Why should user ever see it or care about it? D. On Mon, Aug 28, 2017 at 3:18 PM, Sergey Chugunov wrote: > Dmitriy, > > It was my misunderstanding, I believe that setter is not enough and we need > a

[GitHub] ignite pull request #1951: IGNITE-5226 Annotated fields compression

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1951 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Ignite not friendly for Monitoring

On Mon, Aug 28, 2017 at 1:22 AM, Vladimir Ozerov wrote: > IGNITE-5620 is about error codes thrown from drivers. This is completely > different story, as every driver has specification with it's own specific > error codes. There is no common denominator. > Vova, I am not

[jira] [Created] (IGNITE-6199) SQL: DML processor should send deltas instead of full values when possible

Vladimir Ozerov created IGNITE-6199: --- Summary: SQL: DML processor should send deltas instead of full values when possible Key: IGNITE-6199 URL: https://issues.apache.org/jira/browse/IGNITE-6199

Re: [DISCUSSION] Urgent Ignite bug fix release

Igniters, Seems 2.2 is a urgent bugfix release, so it should be based on 2.1, In this case all other issues with fixVersion = 2.2 should be moved to 2.3. Currently, I see 835 issues with fixVersion = 2.2 Seems we should have only 4 issues with fixVersion = 2.2: - Change default max memory size

Re: Ignite not friendly for Monitoring

Dima, Please see latest comments in the ticket [1]. There is special specification called SQLSTATE governing what errors code are thrown from SQL operations [2]. This is applicable to both JDBC and ODBC. Apart of from standard code, database vendor can add it's own codes as a separate field, or

[jira] [Created] (IGNITE-6198) SQL: Merge operation should group keys by affinity

Vladimir Ozerov created IGNITE-6198: --- Summary: SQL: Merge operation should group keys by affinity Key: IGNITE-6198 URL: https://issues.apache.org/jira/browse/IGNITE-6198 Project: Ignite

[jira] [Created] (IGNITE-6202) SQL: support hash join

Vladimir Ozerov created IGNITE-6202: --- Summary: SQL: support hash join Key: IGNITE-6202 URL: https://issues.apache.org/jira/browse/IGNITE-6202 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2528: IGNITE-2845-2.1.5 Get operation might ignore entr...

GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2528 IGNITE-2845-2.1.5 Get operation might ignore entry update from EntryProcessor. For CI purposes You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6194) SQL: implement lazy query execution for SQL with multiple map queries

Vladimir Ozerov created IGNITE-6194: --- Summary: SQL: implement lazy query execution for SQL with multiple map queries Key: IGNITE-6194 URL: https://issues.apache.org/jira/browse/IGNITE-6194 Project:

[jira] [Created] (IGNITE-6197) SQL: QueryIndex.setInlineSize should return this instead of void

Vladimir Ozerov created IGNITE-6197: --- Summary: SQL: QueryIndex.setInlineSize should return this instead of void Key: IGNITE-6197 URL: https://issues.apache.org/jira/browse/IGNITE-6197 Project:

Re: How a new index is built in runtime?

Should not be too hard. However, this will not change situation a lot. Instead, we need to implement more efficient algorithm of index filling. E.g. fill it with pre-sorted batches. We already have a ticket for that. On Mon, Aug 28, 2017 at 3:46 PM, wrote: > Vova, how

[jira] [Created] (IGNITE-6203) Valid query cannot be processed.

Alexei Scherbakov created IGNITE-6203: - Summary: Valid query cannot be processed. Key: IGNITE-6203 URL: https://issues.apache.org/jira/browse/IGNITE-6203 Project: Ignite Issue Type: Bug

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, can you please describe the algorithm with all the thresholds? On Mon, Aug 28, 2017 at 4:56 AM, Seliverstov Igor wrote: > The suggestion here is based on initial settings, and it's so because there > is no other nodes on the host in the example. > > The algorithm

Re: How a new index is built in runtime?

Vova, how hard is it to make it multi-threaded? ⁣D.​ On Aug 28, 2017, 10:05 AM, at 10:05 AM, Vladimir Ozerov wrote: >Denis, > >We iterate over the whole cache and build the index entry-by-entry. >Control >is returned back to the user when index is ready. > >On Fri, Aug

[GitHub] ignite pull request #1650: IGNITE-3592 Provide some kind of pluggable compre...

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1650 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [DISCUSSION] Urgent Ignite bug fix release

Denis, > BTW, who is considered to be the release manager of this release? I'll do it. On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor wrote: > Ok, the check happens at the node start time or on NODE_JOIN event > > in general it looks like: > > 1) calculate expected

[GitHub] ignite pull request #2529: UpdateSequence fix in ClientTopology.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2529 UpdateSequence fix in ClientTopology. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12688 Alternatively

Re: Resurrect FairAffinityFunction

Igniters, I created a ticket for SQL exception in case of invalid combination of affinity functions are used in query with JOINs: https://issues.apache.org/jira/browse/IGNITE-6195 On Wed, Aug 16, 2017 at 11:59 AM, Vladimir Ozerov wrote: > I am still not quite understand

[jira] [Created] (IGNITE-6196) SQL: verify usability of template-based CREATE TABLE operations

Vladimir Ozerov created IGNITE-6196: --- Summary: SQL: verify usability of template-based CREATE TABLE operations Key: IGNITE-6196 URL: https://issues.apache.org/jira/browse/IGNITE-6196 Project:

[GitHub] ignite pull request #2530: Ignite 6204 - Backport optimizations of checkpoin...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2530 Ignite 6204 - Backport optimizations of checkpointing algorithm into 2.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Testing Ignite Applications Locally

Sergey, can you please elaborate? --Yakov 2017-08-26 23:51 GMT+03:00 Sergey Kozlov : > The idea is great! > > Also I would suggest an ability to run new (modified) tests 100 times in > loop on the CI server to make sure that they don't cause no sporadic > failures (we can

Re: [DISCUSSION] Urgent Ignite bug fix release

Backport issue: https://issues.apache.org/jira/browse/IGNITE-6204 Best Regards, Ivan Rakov On 28.08.2017 17:19, Anton Vinogradov wrote: Igniters, Seems 2.2 is a urgent bugfix release, so it should be based on 2.1, In this case all other issues with fixVersion = 2.2 should be moved to 2.3.

[GitHub] ignite pull request #2531: IGNITE-5838: Unclear exception from BinaryObjectB...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2531 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: How a new index is built in runtime?

Vladimir, Is this a sync or async operation? — Denis > On Aug 28, 2017, at 1:05 AM, Vladimir Ozerov wrote: > > Denis, > > We iterate over the whole cache and build the index entry-by-entry. Control > is returned back to the user when index is ready. > > On Fri, Aug 18,

Re: How to add new build-plan in the TeamCity?

Hi, Aleksey! I'd like to add a new build configuration to the exist project "ignite-2.0". I'm talking about a module which is contained only in my PR [1] at current time. Path to the module: "ignite/modules/compatibility" Path to a test-suite:

Re: Testing Ignite Applications Locally

>As far as Maven archetype, Yakov, is the only purpose of it to load a project, so users can add tests to it? Yes, but not just add. We will also be providing test examples, data loading application sample, shell scripts, etc. This can be pretty handy thing to create project with all dependencies

[GitHub] ignite pull request #2531: IGNITE-5838: Unclear exception from BinaryObjectB...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2531 IGNITE-5838: Unclear exception from BinaryObjectBuilder::build call when builder is reused Fix BinaryObjectBuilder reusage issue. You can merge this pull request into a Git repository by

[GitHub] ignite pull request #2532: IGNITE-5839: Unclear exception from BinaryObjectB...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2532 IGNITE-5839: Unclear exception from BinaryObjectBuilder::build call when builder is reused. Fix BinaryObjectBuilder reusage issue. You can merge this pull request into a Git repository by

Re: [DISCUSSION] Urgent Ignite bug fix release

Anton, thanks for stepping in! The tickets set looks complete for me! Let’s start the vote once the fixes are merged and tests pass. — Denis > On Aug 28, 2017, at 7:19 AM, Anton Vinogradov > wrote: > > Igniters, > > Seems 2.2 is a urgent bugfix release, so it

Re: Testing Ignite Applications Locally

Yakov, ok. I'll do that On Mon, Aug 28, 2017 at 6:19 PM, Yakov Zhdanov wrote: > >As far as Maven archetype, Yakov, is the only purpose of it to load a > project, so users can add tests to it? > > Yes, but not just add. We will also be providing test examples, data > loading

Re: How a new index is built in runtime?

Sync. пн, 28 авг. 2017 г. в 19:34, Denis Magda : > Vladimir, > > Is this a sync or async operation? > > — > Denis > > > On Aug 28, 2017, at 1:05 AM, Vladimir Ozerov > wrote: > > > > Denis, > > > > We iterate over the whole cache and build the index

[GitHub] ignite pull request #2534: For testing

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2534 For testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.4-hotfix Alternatively you can review and

[GitHub] ignite pull request #2533: IGNITE-6122: Propagate SqlFieldsQuery.lazy proper...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2533 IGNITE-6122: Propagate SqlFieldsQuery.lazy property for C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6122

[jira] [Created] (IGNITE-6205) Stability testing on CI server

Sergey Kozlov created IGNITE-6205: - Summary: Stability testing on CI server Key: IGNITE-6205 URL: https://issues.apache.org/jira/browse/IGNITE-6205 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6207) Low GC inserting of new entries

Pranas Baliuka created IGNITE-6207: -- Summary: Low GC inserting of new entries Key: IGNITE-6207 URL: https://issues.apache.org/jira/browse/IGNITE-6207 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-6206) IgniteDataStreamer flush() is not working

Pranas Baliuka created IGNITE-6206: -- Summary: IgniteDataStreamer flush() is not working Key: IGNITE-6206 URL: https://issues.apache.org/jira/browse/IGNITE-6206 Project: Ignite Issue Type: