[jira] [Created] (IGNITE-7510) IgnitePdsClientNearCachePutGetTest fails flaky on TC

Alexey Goncharuk created IGNITE-7510: Summary: IgnitePdsClientNearCachePutGetTest fails flaky on TC Key: IGNITE-7510 URL: https://issues.apache.org/jira/browse/IGNITE-7510 Project: Ignite

RE: Obtaining metadata about items in the cache

I’d like to carry this conversation further, cross-posting to dev list: I now have possible production use cases for accessing cache key [metadata]. As an example, suppose I want to scan all keys from a cache that may contain large amounts of data and perform some operation on a few of them,

Re: Partition loss policy to disable cache completely

I'm still not sure on what Val has suggested. Dmitry, Val, Do you have any concrete API/algorithm in mind? --Yakov

Re: Partition loss policy to disable cache completely

Why not just add a new policy as Val suggested? ⁣D.​ On Jan 23, 2018, 4:44 PM, at 4:44 PM, Yakov Zhdanov wrote: >Val, your computation fails once it reaches the absent partition. Agree >with the point that any new computation should not start. Guys, any >ideas >on how to achieve that? I would th

Re: Partition loss policy to disable cache completely

Val, your computation fails once it reaches the absent partition. Agree with the point that any new computation should not start. Guys, any ideas on how to achieve that? I would think of scan/sql query checking that there is no data loss on current topology version prior to start. Val, please note

Re: Partition loss policy to disable cache completely

Yakov, I still think there are valid use cases. From the top of my head - what if one wants to iterate through multiple partitions and do some calculations? Locking and transactional semantics are not needed, but if some of the data is LOST, computation should fail, and new computations should not

[jira] [Created] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

Yury Babak created IGNITE-7509: -- Summary: Adjust "build" and "getting started" sections of documentation for ML module Key: IGNITE-7509 URL: https://issues.apache.org/jira/browse/IGNITE-7509 Project: Ign

Re: [SparkDataFrame] Query Optimization. Prototype

Agree. The unsupported functions should be mentioned on the page that will cover Ignite ANSI-99 compliance. We have first results available for CORE features of the specification: https://ggsystems.atlassian.net/wiki/spaces/GG/pages/45093646/ANSI+SQL+99

Re: Partition loss policy to disable cache completely

Alex, I am against reducing cluster operation. I tried to explain in the prev email that it is impossible to have consistent approach here. You can prohibit operations only after exchange completes. However, in this case plenty of transactions are committed on previous cache topology having nodes t

Re: [SparkDataFrame] Query Optimization. Prototype

I think we need a page listing the unsupported functions with explanation why, which is either it does not make sense in Ignite or is planned in future release. Sergey, do you think you will be able to do it? D. On Tue, Jan 23, 2018 at 12:05 AM, Serge Puchnin wrote: > yes, the Cust function is

[GitHub] ignite pull request #3425: IGNITE-7506 setting BaselineTopology in compatibi...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3425 IGNITE-7506 setting BaselineTopology in compatibilityMode …n old nodes left the cluster You can merge this pull request into a Git repository by running: $ git pull https://gith

Ignite diagnostic (SQL system views)

Hello, Igniters! For Ignite diagnostic usually it’s helpful to get some Ignite internals information. But currently, in my opinion, there are no convenient tools for this purpose: ·Some issues can be solved by analyzing log files. Log files are useful for dumps, but sometimes they are dif

Re: Partition loss policy to disable cache completely

Valentin, I am ok with having a policy which prohibits all cache operations, and this is not very hard to implement. Although, I agree with Yakov - I do not see any point in reducing cluster availability when operations can be safely completed. 2018-01-23 2:22 GMT+03:00 Yakov Zhdanov : > Val, >

Re: cache operation failed after transaction rolled back due to deadlock

Alex Goncharuk, can you please take a look and comment? Test seems to be valid from my standpoint. Yakov Zhdanov, www.gridgain.com 2018-01-22 23:14 GMT-08:00 ALEKSEY KUZNETSOV : > > created ticket with reproducer [1] > > I think the fix should be to clear context in tx.close() > > [1] https://is

[jira] [Created] (IGNITE-7508) GridKernalContextImpl::isDaemon creates contention on system properties access

Stanislav Lukyanov created IGNITE-7508: -- Summary: GridKernalContextImpl::isDaemon creates contention on system properties access Key: IGNITE-7508 URL: https://issues.apache.org/jira/browse/IGNITE-7508

[GitHub] ignite pull request #3423: IGNITE-7507: Ignite node performance drop during ...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3423 IGNITE-7507: Ignite node performance drop during checkpoint start Store metapage eviction causes long checkpoint lock hold time You can merge this pull request into a Git repository by running:

[GitHub] ignite pull request #3424: IGNITE-5571 with 4191

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/3424 IGNITE-5571 with 4191 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5571-with-4191 Alternatively you can

[jira] [Created] (IGNITE-7507) Ignite node performance drop during checkpoint start: store metapage eviction causes long checkpoint lock hold time

Dmitriy Pavlov created IGNITE-7507: -- Summary: Ignite node performance drop during checkpoint start: store metapage eviction causes long checkpoint lock hold time Key: IGNITE-7507 URL: https://issues.apache.org/ji

[jira] [Created] (IGNITE-7506) GridClusterStateProcessor#compatibilityMode flag never gets reset to false

Sergey Chugunov created IGNITE-7506: --- Summary: GridClusterStateProcessor#compatibilityMode flag never gets reset to false Key: IGNITE-7506 URL: https://issues.apache.org/jira/browse/IGNITE-7506 Proj

[GitHub] ignite pull request #3421: IGNITE-7500 Partition update counters hot fix

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3421 ---

[GitHub] ignite pull request #3422: IGNITE-7443: ODBC now use native batching capabil...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3422 IGNITE-7443: ODBC now use native batching capabilities on the server side You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignit

Re: Ignite Semaphore Bug 7090

Hi Tim, thanks for the update! I left you a comment on Jira. Best regards, Vladisav On Mon, Jan 22, 2018 at 6:17 PM, Tim Onyschak wrote: > Hey Vladisav, > > I implemented your requests. Take a look, specifically, i created an > interface to encapsulate the NodeUpdates and let > the DataStructu

[jira] [Created] (IGNITE-7505) Node not in baseline topology may initialize local partition

Alexey Goncharuk created IGNITE-7505: Summary: Node not in baseline topology may initialize local partition Key: IGNITE-7505 URL: https://issues.apache.org/jira/browse/IGNITE-7505 Project: Ignite

[jira] [Created] (IGNITE-7504) Decision tree documentation

Yury Babak created IGNITE-7504: -- Summary: Decision tree documentation Key: IGNITE-7504 URL: https://issues.apache.org/jira/browse/IGNITE-7504 Project: Ignite Issue Type: Task Component

[jira] [Created] (IGNITE-7503) MLP documentation

Yury Babak created IGNITE-7503: -- Summary: MLP documentation Key: IGNITE-7503 URL: https://issues.apache.org/jira/browse/IGNITE-7503 Project: Ignite Issue Type: Sub-task Components: doc

[jira] [Created] (IGNITE-7502) Baseline topology should affect only persistent caches

Ilya Lantukh created IGNITE-7502: Summary: Baseline topology should affect only persistent caches Key: IGNITE-7502 URL: https://issues.apache.org/jira/browse/IGNITE-7502 Project: Ignite Issue

[jira] [Created] (IGNITE-7501) Improve underlying iterators closing process for cache iterators.

Roman Kondakov created IGNITE-7501: -- Summary: Improve underlying iterators closing process for cache iterators. Key: IGNITE-7501 URL: https://issues.apache.org/jira/browse/IGNITE-7501 Project: Ignite

[GitHub] ignite pull request #3421: IGNITE-7500 Partition update counters hot fix

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3421 IGNITE-7500 Partition update counters hot fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7500 Alternatively

[jira] [Created] (IGNITE-7500) Partition update counters may be inconsistent after rebalancing

Pavel Kovalenko created IGNITE-7500: --- Summary: Partition update counters may be inconsistent after rebalancing Key: IGNITE-7500 URL: https://issues.apache.org/jira/browse/IGNITE-7500 Project: Ignite

[jira] [Created] (IGNITE-7499) DataRegionMetricsImpl#getPageSize returns ZERO for system data regions

Alexey Kuznetsov created IGNITE-7499: Summary: DataRegionMetricsImpl#getPageSize returns ZERO for system data regions Key: IGNITE-7499 URL: https://issues.apache.org/jira/browse/IGNITE-7499 Projec

[GitHub] ignite pull request #3398: IGNITE-7456: Fix wrong batch logic in distributed...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3398 ---

[jira] [Created] (IGNITE-7498) Crash on startup when DEBUG log level enabled under Java 9

Pavel Tupitsyn created IGNITE-7498: -- Summary: Crash on startup when DEBUG log level enabled under Java 9 Key: IGNITE-7498 URL: https://issues.apache.org/jira/browse/IGNITE-7498 Project: Ignite

[jira] [Created] (IGNITE-7497) Web console should check connection to cluster before sending any task

Pavel Konstantinov created IGNITE-7497: -- Summary: Web console should check connection to cluster before sending any task Key: IGNITE-7497 URL: https://issues.apache.org/jira/browse/IGNITE-7497 Pr

[GitHub] ignite pull request #3420: Fix test license header

GitHub user sunnychanwork opened a pull request: https://github.com/apache/ignite/pull/3420 Fix test license header Fix License header for CassandraSessionImplTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/sunnychanwork/igni

[GitHub] ignite pull request #3124: IGNITE-6425: Races during transaction finalizatio...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/3124 ---

Re: [SparkDataFrame] Query Optimization. Prototype

Serge, thank you! Vladimir, guys, can you take a look at another questions: * Can I know scale and precision of DECIMAL column? Example - [3] * Ignite have some limitation for a *distributed* join. For example, we can execute join only for indexed columns. Example - [4]. *

Re: [SparkDataFrame] Query Optimization. Prototype

yes, the Cust function is supporting both Ignite and H2. I've updated the documentation for next system functions: CASEWHEN Function, CAST, CONVERT, TABLE https://apacheignite-sql.readme.io/docs/system-functions And for my mind, next functions aren't applicable for Ignite: ARRAY_GET, ARRAY_LENGT

[jira] [Created] (IGNITE-7496) Review a SQL documentation

Sergey Puchnin created IGNITE-7496: -- Summary: Review a SQL documentation Key: IGNITE-7496 URL: https://issues.apache.org/jira/browse/IGNITE-7496 Project: Ignite Issue Type: Bug