Re: [SparkDataFrame] Query Optimization. Prototype

Hi Nikolay, Could you please clarify your question about scale and precision? Do you mean whether it is possible to read it from table metadata? If yes, it is not possible at the moment unfortunately - we do not store information about lengths, scales and precision, only actual data types are pass

[jira] [Created] (IGNITE-7511) FCM documentation

Yury Babak created IGNITE-7511: -- Summary: FCM documentation Key: IGNITE-7511 URL: https://issues.apache.org/jira/browse/IGNITE-7511 Project: Ignite Issue Type: Task Components: documen

[jira] [Created] (IGNITE-7512) Variable updated should be checked for null before invocation of ctx.validateKeyAndValue(entry.key(), updated) in GridDhtAtomicCache.updateWithBatch

Evgenii Zhuravlev created IGNITE-7512: - Summary: Variable updated should be checked for null before invocation of ctx.validateKeyAndValue(entry.key(), updated) in GridDhtAtomicCache.updateWithBatch Key: IGNITE-7512

Re: [SparkDataFrame] Query Optimization. Prototype

Hello, Vladimir. Thank you for an answer. > Do you mean whether it is possible to read it from table metadata? Yes, you are right. I want to read scale and precision of DECIMAL column from table metadata. > This will be fixed at some point in future, but I do not have any dates at > the mome

[jira] [Created] (IGNITE-7513) Get rid of org.jsr166.ConcurrentHashMap8

Andrey Kuznetsov created IGNITE-7513: Summary: Get rid of org.jsr166.ConcurrentHashMap8 Key: IGNITE-7513 URL: https://issues.apache.org/jira/browse/IGNITE-7513 Project: Ignite Issue Type:

Re: Ignite diagnostic (SQL system views)

Hi Alex, System views could be extremely valuable addition for Ignite. Ideally, user should be able to monitor and manage state of the whole cluster with a single SQL command line. We have plans to implement it for a very long time. However, this is very sensitive task which should take a lot of m

[GitHub] ignite pull request #3426: Ignite-2.4.2-p3

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3426 Ignite-2.4.2-p3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.2-p3 Alternatively you can review

[GitHub] ignite pull request #3427: Ignite-2.4.1-p8

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3427 Ignite-2.4.1-p8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p8 Alternatively you can review

[GitHub] ignite pull request #3428: Ignite 7513

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3428 Ignite 7513 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7513 Alternatively you can review and appl

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

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

[jira] [Created] (IGNITE-7514) Affinity assignment isn't recalculated if PRIMARY node isn't OWNER

Ilya Lantukh created IGNITE-7514: Summary: Affinity assignment isn't recalculated if PRIMARY node isn't OWNER Key: IGNITE-7514 URL: https://issues.apache.org/jira/browse/IGNITE-7514 Project: Ignite

[GitHub] ignite pull request #3429: IGNITE-7512: fixed NPE when entry processor remov...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/3429 IGNITE-7512: fixed NPE when entry processor removes entry and queries… … are enabled on cache. You can merge this pull request into a Git repository by running: $ git pull https://git

Re: Ignite diagnostic (SQL system views)

1) It’s not a principal point, I can change schema. The INFORMATION_SCHEMA was used because it’s already exists and usually used for metadata tables and views. Your proposal is to use schema “IGNITE”, am I understand you right? BTW, for now, we can’t query another (H2) meta tables from the INFORMAT

[jira] [Created] (IGNITE-7515) ODBC: Socket error messages may be missing on linux

Sergey Kalashnikov created IGNITE-7515: -- Summary: ODBC: Socket error messages may be missing on linux Key: IGNITE-7515 URL: https://issues.apache.org/jira/browse/IGNITE-7515 Project: Ignite

Weird FillFactor metric fluctuation.

Hi Ignites, I've tried to estimate in runtime how much free memory there are on a node. Looking at memory metrics API, I need a pageSize, number of allocated pages and a fillFactor of these pages. But it looks like FillFactor metric is broken or useless. A simple test where new entries are put t

Re: Ignite diagnostic (SQL system views)

Let's start with a single and the most simple view, e.g. LOCAL_TRANSACTIONS. We will review and merge it along with necessary infrastructure. Then will handle the rest view in separate tickets and separate focused discussions. On Wed, Jan 24, 2018 at 5:29 PM, Alex Plehanov wrote: > 1) It’s not a

[GitHub] ignite pull request #3394: IGNITE-6832 Proper handling LFS and WAL persisten...

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

TX SQL: SELECT FOR UPDATE implementation

Hello Igniters, I'd like to bring up the discussion about implementation details of https://issues.apache.org/jira/browse/IGNITE-6937 about support of SELECT FOR UPDATE statements as a part of overall activity on transactional SQL. That kind of statements allows the user proactively obtain row le

[jira] [Created] (IGNITE-7516) Get rid of org.jsr166.ConcurrentLinkedHashMap

Andrey Kuznetsov created IGNITE-7516: Summary: Get rid of org.jsr166.ConcurrentLinkedHashMap Key: IGNITE-7516 URL: https://issues.apache.org/jira/browse/IGNITE-7516 Project: Ignite Issue

[jira] [Created] (IGNITE-7517) Get rid of org.jsr166.ConcurrentLinkedDeque8

Andrey Kuznetsov created IGNITE-7517: Summary: Get rid of org.jsr166.ConcurrentLinkedDeque8 Key: IGNITE-7517 URL: https://issues.apache.org/jira/browse/IGNITE-7517 Project: Ignite Issue T

[GitHub] ignite pull request #3430: ignite-7502 : Disabled BLT for non-persistent cac...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3430 ignite-7502 : Disabled BLT for non-persistent caches. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7502 Alte

Re: Weird FillFactor metric fluctuation.

FillFactor metric is in fact FreeList utilization factor, so the name is definitely misleading. Currently we have no metric to estimate free space. And we should define what is 'free' in terms of Ignite page memory implementation. 2018-01-24 17:57 GMT+03:00 Andrey Mashenkov : > Hi Ignites, > > I'

[jira] [Created] (IGNITE-7518) Get rid of org.jsr166.LongAdder8, org.jsr166.ThreadLocalRandom

Andrey Kuznetsov created IGNITE-7518: Summary: Get rid of org.jsr166.LongAdder8, org.jsr166.ThreadLocalRandom Key: IGNITE-7518 URL: https://issues.apache.org/jira/browse/IGNITE-7518 Project: Ignit

[jira] [Created] (IGNITE-7519) DataStreamer suppresses exceptions in IsolatedUpdater

Ilya Kasnacheev created IGNITE-7519: --- Summary: DataStreamer suppresses exceptions in IsolatedUpdater Key: IGNITE-7519 URL: https://issues.apache.org/jira/browse/IGNITE-7519 Project: Ignite

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

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

Re: Ignite diagnostic (SQL system views)

I've created IEP-13 [1] to cover all cases. Feel free to create issues. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75962769 On Wed, Jan 24, 2018 at 6:10 PM, Vladimir Ozerov wrote: > Let's start with a single and the most simple view, e.g. > LOCAL_TRANSACTIONS. We will

[jira] [Created] (IGNITE-7520) Provide util-methods to get baseline from context

Eduard Shangareev created IGNITE-7520: - Summary: Provide util-methods to get baseline from context Key: IGNITE-7520 URL: https://issues.apache.org/jira/browse/IGNITE-7520 Project: Ignite

[GitHub] ignite pull request #3431: IGNITE-7520 Provide util-methods to get baseline ...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/3431 IGNITE-7520 Provide util-methods to get baseline from context You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7

[jira] [Created] (IGNITE-7521) Add new assertions to FilePageStore and provide page content if read page is broken

Eduard Shangareev created IGNITE-7521: - Summary: Add new assertions to FilePageStore and provide page content if read page is broken Key: IGNITE-7521 URL: https://issues.apache.org/jira/browse/IGNITE-7521

[GitHub] ignite pull request #3432: Ignite 7521

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/3432 Ignite 7521 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7521 Alternatively you can review and apply these

[jira] [Created] (IGNITE-7522) Web console: Wrong cluster active status after delete work folder

Dmitriy Shabalin created IGNITE-7522: Summary: Web console: Wrong cluster active status after delete work folder Key: IGNITE-7522 URL: https://issues.apache.org/jira/browse/IGNITE-7522 Project: Ig

[jira] [Created] (IGNITE-7523) Exception on data expiration after sharedRDD.saveValues call

Mikhail Cherkasov created IGNITE-7523: - Summary: Exception on data expiration after sharedRDD.saveValues call Key: IGNITE-7523 URL: https://issues.apache.org/jira/browse/IGNITE-7523 Project: Ignit

Re: Weird FillFactor metric fluctuation.

There will be a way to get used and free size in bytes in Ignite 2.4: https://issues.apache.org/jira/browse/IGNITE-7491 *Anton*, did we use fill factor parameter to calculate the used space for the new metrics? If it’s so then the issue reporte

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

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

Re: TX SQL: SELECT FOR UPDATE implementation

Alex, Thank you for detailed analysis. My 50 cents: 1) I would not allow GROUP BYs in the first place. These are good candidates for further iterations IMO 2) Same as p.1 3) In final TX SQL solution we woll lock rows, not keys (GridCacheMapEntry). Can we simply lock every row returned from the qu