[jira] [Created] (IGNITE-7040) Web console: Invalid user table height

Vasiliy Sisko created IGNITE-7040: - Summary: Web console: Invalid user table height Key: IGNITE-7040 URL: https://issues.apache.org/jira/browse/IGNITE-7040 Project: Ignite Issue Type: Bug

Re: Transport compression (not store compression)

Hi, I've filed a ticket [1]. I'll try to share design details in a couple of days. 1. https://issues.apache.org/jira/browse/IGNITE-7024 2017-11-23 18:31 GMT+03:00 Denis Magda : > Nikita, > > Sounds like a good plan. Please share the design details prior getting > down to the

Re: FOR UPDATE support in SELECT clause

Hi Denis, "FOR UPDATE" is not supported at the moment. We will add it's support for transactional case [1]. In non-transactional case it would behave in the same way as normal SELECT. [1] https://issues.apache.org/jira/browse/IGNITE-6937 On Thu, Oct 19, 2017 at 3:21 AM, Denis Magda

Re: IgniteJdbcDriver's usage of JavaLogger

Andrey, Agree, it is better to use JUL logger directly without Ignite wrapper. On Mon, Oct 23, 2017 at 10:05 PM, Andrey Kornev wrote: > Hey Vladimir, > > Maybe it'd be better to just use JUL logger directly? > > Or, better yet, just get rid of that nagging patronizing

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Dmitry, How these policies will be configured? Do you have any API in mind? On Thu, Nov 23, 2017 at 6:26 PM, Denis Magda wrote: > No objections here. Additional policies like EXEC might be added later > depending on user needs. > > — > Denis > > > On Nov 23, 2017, at 2:26

Re: Facility to detect long STW pauses and other system response degradations

Makes sense. On Wed, Nov 22, 2017 at 4:54 PM, Anton Vinogradov wrote: > Vova, > > Monitoring systems works not how you expected, they LOVE incremental > metrics :) > > > 1) When did these events appear? > > Monitoring gets metrics each N seconds. > > 01.00 got 0, 0 >

Re: Allow multiple caches use one SQL schema

Hi Denis, I do not see any section in docs mentioning that it is impossible to have several caches in the same schema. If this is so, there is no need to fix anything in docs. On Wed, Oct 25, 2017 at 6:35 PM, Denis Magda wrote: > Vladimir, > > Guess this has to be documented

[jira] [Created] (IGNITE-7039) SQL: local query should pin affected partitions

Vladimir Ozerov created IGNITE-7039: --- Summary: SQL: local query should pin affected partitions Key: IGNITE-7039 URL: https://issues.apache.org/jira/browse/IGNITE-7039 Project: Ignite Issue

Re: SQL warning for partitioned caches with setLocal

Hi Luqman, Required caches are already derived from SQL query through Ignite SQL internals. We should just re-use this code for local queries. I filed a ticket to fix this [1]. [1] https://issues.apache.org/jira/browse/IGNITE-7039 On Wed, Nov 22, 2017 at 12:05 AM, Luqman Ahmad

Re: affinity key syntax

Dima, I filed a ticket [1]. This is very promising approach which will allow us to replace regular joins with nested tables in many cases, thus boosting performance of JOINs and making Ignite's affinity configuration easier form UX perspecitve. But this is a big thing, as it would require

[jira] [Created] (IGNITE-7038) SQL: nested tables support

Vladimir Ozerov created IGNITE-7038: --- Summary: SQL: nested tables support Key: IGNITE-7038 URL: https://issues.apache.org/jira/browse/IGNITE-7038 Project: Ignite Issue Type: Bug

Re: Query duration metrics

Hi Andrey, You are right, current implementation of metrics is questionable. Please feel free to file a ticket if you have ideas on how to improve it. On Sun, Nov 5, 2017 at 11:17 PM, Andrey Kornev wrote: > Hi, > > It appears as if the query duration metric is a bit

[GitHub] ignite pull request #3100: IGNITE-5490 Ignite Continuous Query might not sen...

GitHub user sunnychanwork opened a pull request: https://github.com/apache/ignite/pull/3100 IGNITE-5490 Ignite Continuous Query might not send update request During continuous query setup, there are potential updates in flight that would potentially have a situation like this:

[jira] [Created] (IGNITE-7037) Web console: Wrong activities metrics

Vasiliy Sisko created IGNITE-7037: - Summary: Web console: Wrong activities metrics Key: IGNITE-7037 URL: https://issues.apache.org/jira/browse/IGNITE-7037 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7036) Web console: Wrong export of grouped users

Vasiliy Sisko created IGNITE-7036: - Summary: Web console: Wrong export of grouped users Key: IGNITE-7036 URL: https://issues.apache.org/jira/browse/IGNITE-7036 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7035) Web console: New user redirected on nonexistent page

Vasiliy Sisko created IGNITE-7035: - Summary: Web console: New user redirected on nonexistent page Key: IGNITE-7035 URL: https://issues.apache.org/jira/browse/IGNITE-7035 Project: Ignite

[jira] [Created] (IGNITE-7034) Web console: Wrong notebooks on become this user

Vasiliy Sisko created IGNITE-7034: - Summary: Web console: Wrong notebooks on become this user Key: IGNITE-7034 URL: https://issues.apache.org/jira/browse/IGNITE-7034 Project: Ignite Issue

[jira] [Created] (IGNITE-7033) Web console: Increase width of columns on admin page

Vasiliy Sisko created IGNITE-7033: - Summary: Web console: Increase width of columns on admin page Key: IGNITE-7033 URL: https://issues.apache.org/jira/browse/IGNITE-7033 Project: Ignite

[jira] [Created] (IGNITE-7032) Web console: Links in activiy details.

Vasiliy Sisko created IGNITE-7032: - Summary: Web console: Links in activiy details. Key: IGNITE-7032 URL: https://issues.apache.org/jira/browse/IGNITE-7032 Project: Ignite Issue Type: Bug

Re: Apache Ignite Wikipedia

This is awesome! I know that Wikipedia submissions are not easily approved, so great job on pushing this through. D. On Mon, Nov 27, 2017 at 5:47 PM, Denis Magda wrote: > Igniters, > > Finally, we got Ignite’s wiki page ready and approved: >

Re: Rework storage format to index-organized approach

Vladimir, I definitely like the overall direction. My comments are below... On Mon, Nov 27, 2017 at 12:46 PM, Vladimir Ozerov wrote: > > I propose to adopt this approach in two phases: > 1) Optionally add data to leaf pages. This should improve our ScanQuery >

[jira] [Created] (IGNITE-7031) Web console: Error on cancellation of comfirm dialog

Vasiliy Sisko created IGNITE-7031: - Summary: Web console: Error on cancellation of comfirm dialog Key: IGNITE-7031 URL: https://issues.apache.org/jira/browse/IGNITE-7031 Project: Ignite

[jira] [Created] (IGNITE-7030) Web console: (add) link not create new linked item

Vasiliy Sisko created IGNITE-7030: - Summary: Web console: (add) link not create new linked item Key: IGNITE-7030 URL: https://issues.apache.org/jira/browse/IGNITE-7030 Project: Ignite Issue

Re: Contribute ApacheIgnite

Hello Eugeniu, Thanks for showing an interest in Ignite and welcome aboard! I granted you required privileges in JIRA, so go ahead and take over the ticket. Yury, who is one of ML maintainers can answer on all the IGNITE-6878 related questions in a separate discussion. Please start it off.

Re: Rework storage format to index-organized approach

Vladimir, How the free lists will be affected by the indexed-organized architecture? From what I see they’re becoming optional. — Denis > On Nov 27, 2017, at 12:46 PM, Vladimir Ozerov wrote: > > Igniters, > > I'd like to start a discussion about new storage format for

Apache Ignite Wikipedia

Igniters, Finally, we got Ignite’s wiki page ready and approved: https://en.wikipedia.org/wiki/Apache_Ignite The page is rather technical and I kept it short from the beginning to get through a meticulous review process. Now, feel free to improve

[jira] [Created] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver

Valentin Kulichenko created IGNITE-7029: --- Summary: Add an ability to provide multiple connection addresses for thin JDBC driver Key: IGNITE-7029 URL: https://issues.apache.org/jira/browse/IGNITE-7029

Re: TC issues. IGNITE-3084. Spark Data Frame API

Hi Nikolay, Please see my responses inline. -Val On Fri, Nov 24, 2017 at 2:55 AM, Николай Ижиков wrote: > Hello, guys. > > I have some issues on TC with my PR [1] for IGNITE-3084(Spark Data Frame > API). > Can you, please, help me: > > > 1. `Ignite RDD spark 2_10` - >

Re: Request for Participation: The Right Metrics for the Right Project

Hi Daniel, Is there an easy way to hook Kibble with Ignite? We’re definitely interested in such capabilities. — Denis > On Nov 27, 2017, at 10:26 AM, Daniel Gruno wrote: > > Hi there, fellow Apache projects! > > The Apache Kibble project serves as a practical

Re: Integration of Spark and Ignite. Prototype.

Nikolay, Let's estimate the strategy implementation work, and then decide weather to merge the code in current state or not. If anything is unclear, please start a separate discussion. -Val On Fri, Nov 24, 2017 at 5:42 AM, Николай Ижиков wrote: > Hello, Val, Denis. > >

[GitHub] ignite pull request #3099: Ignite 6871

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3099 Ignite 6871 You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-6871 Alternatively you can review and apply

Contribute ApacheIgnite

Hello, My name is Semenciuc Eugeniu, i'm a Romanian software developer with 4 -5 years experience. I recently started working with Apache Ignite, and I'm very excited about his capabilities. I would like to contribute to the development of this platform. I think my good mathematical background

[jira] [Created] (IGNITE-7028) Memcached does not set type flags for response

Mikhail Cherkasov created IGNITE-7028: - Summary: Memcached does not set type flags for response Key: IGNITE-7028 URL: https://issues.apache.org/jira/browse/IGNITE-7028 Project: Ignite

Rework storage format to index-organized approach

Igniters, I'd like to start a discussion about new storage format for Ignite. Our current approach is so-called *heap-organized* storage with secondary index per partition. It has a number of drawbacks: 1) Slow scans (joins, OLAP workload) - data is writen in arbitrary manner, so iteration over

[jira] [Created] (IGNITE-7027) Single primary index instead of mulitple per-partition indexes

Vladimir Ozerov created IGNITE-7027: --- Summary: Single primary index instead of mulitple per-partition indexes Key: IGNITE-7027 URL: https://issues.apache.org/jira/browse/IGNITE-7027 Project: Ignite

[jira] [Created] (IGNITE-7026) Index-organized data storage format

Vladimir Ozerov created IGNITE-7026: --- Summary: Index-organized data storage format Key: IGNITE-7026 URL: https://issues.apache.org/jira/browse/IGNITE-7026 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3090: IGNITE-6929

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

[GitHub] ignite pull request #3098: Ignite: Batch cache destroy requests added

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3098 Ignite: Batch cache destroy requests added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12972

[GitHub] ignite pull request #3097: IGNITE-6992 FIX Ignite MR problem with accessing ...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/3097 IGNITE-6992 FIX Ignite MR problem with accessing hdfs with enabled Ke… …rberos You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7025) Implement different strategies to fill missed data in LabeledDataset during loading from file

Aleksey Zinoviev created IGNITE-7025: Summary: Implement different strategies to fill missed data in LabeledDataset during loading from file Key: IGNITE-7025 URL:

[jira] [Created] (IGNITE-7024) Introduce some kind of network compression

Amelchev Nikita created IGNITE-7024: --- Summary: Introduce some kind of network compression Key: IGNITE-7024 URL: https://issues.apache.org/jira/browse/IGNITE-7024 Project: Ignite Issue

Re: Thin Client Protocol documentation

Pavel Thanks for explanations! On Mon, Nov 27, 2017 at 2:46 PM, Pavel Tupitsyn wrote: > Sergey, > > 1. Code table size does not affect anything, as I understand, so there is > no reason to introduce an extra byte. > 2. We have object arrays (code 23), I forgot to mention

[jira] [Created] (IGNITE-7023) In visorcmd I cannot list certain cache contents located on certain node.

Galinger Vladimir created IGNITE-7023: - Summary: In visorcmd I cannot list certain cache contents located on certain node. Key: IGNITE-7023 URL: https://issues.apache.org/jira/browse/IGNITE-7023

[jira] [Created] (IGNITE-7022) Use QuadTree for kNN performance

Aleksey Zinoviev created IGNITE-7022: Summary: Use QuadTree for kNN performance Key: IGNITE-7022 URL: https://issues.apache.org/jira/browse/IGNITE-7022 Project: Ignite Issue Type:

Re: Thin Client Protocol documentation

Sergey, 1. Code table size does not affect anything, as I understand, so there is no reason to introduce an extra byte. 2. We have object arrays (code 23), I forgot to mention them, fixed. 3. Also forgot, see code 25 in the updated document. Also note that operation codes have been updated

[GitHub] ignite pull request #3096: IGNITE-7001

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/3096 IGNITE-7001 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7001 Alternatively you can review and apply

[jira] [Created] (IGNITE-7021) IgniteOOM is not propogated to client in case of implicit transaction

Mikhail Cherkasov created IGNITE-7021: - Summary: IgniteOOM is not propogated to client in case of implicit transaction Key: IGNITE-7021 URL: https://issues.apache.org/jira/browse/IGNITE-7021

[GitHub] ignite pull request #2816: IGNITE-2766 Opportunistically reopen cache after ...

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

[GitHub] ignite pull request #3077: IGNITE-2766 Ensure that cache is available after ...

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

[jira] [Created] (IGNITE-7020) Web Console: add column resizer to pinned columns

Dmitriy Shabalin created IGNITE-7020: Summary: Web Console: add column resizer to pinned columns Key: IGNITE-7020 URL: https://issues.apache.org/jira/browse/IGNITE-7020 Project: Ignite

[jira] [Created] (IGNITE-7019) Cluster can not survive after IgniteOOM

Mikhail Cherkasov created IGNITE-7019: - Summary: Cluster can not survive after IgniteOOM Key: IGNITE-7019 URL: https://issues.apache.org/jira/browse/IGNITE-7019 Project: Ignite Issue

[GitHub] ignite pull request #3085: ignite-6944 Fixed lookup of writeReplace and read...

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

[GitHub] ignite pull request #3095: IGNITE-6971 Ignite Logger type & logging file con...

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3095 IGNITE-6971 Ignite Logger type & logging file config indication You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite