[jira] [Created] (IGNITE-6941) Add JDBC Thin Client security support.

Andrew Mashenkov created IGNITE-6941: Summary: Add JDBC Thin Client security support. Key: IGNITE-6941 URL: https://issues.apache.org/jira/browse/IGNITE-6941 Project: Ignite Issue Type:

[GitHub] ignite pull request #3049: IGNITE-6907 Check LINQ join tests for errors

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3049 IGNITE-6907 Check LINQ join tests for errors You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6907

[jira] [Created] (IGNITE-6939) Exclude false owners from the execution plan based on query response

Alexey Goncharuk created IGNITE-6939: Summary: Exclude false owners from the execution plan based on query response Key: IGNITE-6939 URL: https://issues.apache.org/jira/browse/IGNITE-6939

[GitHub] ignite pull request #3052: IGNITE-6931

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

[GitHub] ignite pull request #3054: Ignite-gg-12940

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3054 Ignite-gg-12940 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12940 Alternatively you can review and

[GitHub] ignite pull request #3051: IGNITE-6870 Added new JMX metric for cache topolo...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3051 IGNITE-6870 Added new JMX metric for cache topology validation monitoring You can merge this pull request into a Git repository by running: $ git pull

Re: Confusing slf4j error messages

It will utilize commons-logging (it is in dependency tree) according to https://spring.io/blog/2009/12/04/logging-dependencies-in-spring/ "The nice thing about commons-logging is that you don’t need anything else to make your application work. It has a runtime discovery algorithm that looks for

[GitHub] ignite pull request #3053: IGNITE-6869 Added new JMX metric: Total jobs exec...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3053 IGNITE-6869 Added new JMX metric: Total jobs execution time. Added new JMX metric: Total jobs execution time. Added MBean to monitor aggregated cluster metrics. You can merge this

Adding Persistent Memory Support for Ignite

Hi all, Ignite, when persistence mode is enabled, stores data and indexes on disk. To minimize the latency of disks, several tuning options can be applied. Setting the page size of a memory region to match the page size of the underlying storage, using a separate disk for the WAL, and using

[GitHub] ignite pull request #3050: Ignite-gg-12939

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3050 Ignite-gg-12939 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12939 Alternatively you can review and

[jira] [Created] (IGNITE-6940) Provide metric to monitor Thread Starvation

Andrey Kuznetsov created IGNITE-6940: Summary: Provide metric to monitor Thread Starvation Key: IGNITE-6940 URL: https://issues.apache.org/jira/browse/IGNITE-6940 Project: Ignite Issue

Meetup tonight in Santa Clara CA: "In-Memory Computing Essentials for Java Developers"

Igniters, those of you in the San Francisco Bay Area are invited to tonight's meetup in Santa Clara. It features Ignite PMC Chair Denis Magda who will deliver a 90-minute hands-on workshop titled : "In-Memory Computing Essentials for Java Developers " More info and RSVP

[jira] [Created] (IGNITE-6935) SQL TX: Locking protocol for simple queries

Vladimir Ozerov created IGNITE-6935: --- Summary: SQL TX: Locking protocol for simple queries Key: IGNITE-6935 URL: https://issues.apache.org/jira/browse/IGNITE-6935 Project: Ignite Issue

[jira] [Created] (IGNITE-6937) SQL TX: Support SELECT FOR UPDATE

Vladimir Ozerov created IGNITE-6937: --- Summary: SQL TX: Support SELECT FOR UPDATE Key: IGNITE-6937 URL: https://issues.apache.org/jira/browse/IGNITE-6937 Project: Ignite Issue Type: Task

Re: Confusing slf4j error messages

Hello Alexey! If we exclude this dependency, which logger will be used by spring framework? On Thu, Nov 16, 2017 at 2:35 PM, Alexey Popov wrote: > Hi Igniters, > > Ignite examples and Ignite itself with some configurations prints out > annoying messages related to slf4j:

[GitHub] ignite pull request #3045: IGN-8915

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/3045 IGN-8915 [IGNITE-6922] Class can not undeploy from grid in some specific cases You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6934) SQL: evaluate performance of onheap row caching

Vladimir Ozerov created IGNITE-6934: --- Summary: SQL: evaluate performance of onheap row caching Key: IGNITE-6934 URL: https://issues.apache.org/jira/browse/IGNITE-6934 Project: Ignite Issue

[jira] [Created] (IGNITE-6936) SQL TX: Implement commit protocol

Vladimir Ozerov created IGNITE-6936: --- Summary: SQL TX: Implement commit protocol Key: IGNITE-6936 URL: https://issues.apache.org/jira/browse/IGNITE-6936 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3044: IGNITE-5755 change calculation of memory policy s...

GitHub user sergvolkov opened a pull request: https://github.com/apache/ignite/pull/3044 IGNITE-5755 change calculation of memory policy size You can merge this pull request into a Git repository by running: $ git pull https://github.com/sergvolkov/ignite ignite-2.1

[jira] [Created] (IGNITE-6938) SQL TX: Reads should see own's previous writes

Vladimir Ozerov created IGNITE-6938: --- Summary: SQL TX: Reads should see own's previous writes Key: IGNITE-6938 URL: https://issues.apache.org/jira/browse/IGNITE-6938 Project: Ignite Issue

[GitHub] ignite pull request #3046: IGNITE-6612: Wrap ack methods in their own class

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/3046 IGNITE-6612: Wrap ack methods in their own class You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite ignite-6612 Alternatively you

Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

Hello, I've added support of distributed OLS regression per IGNITE-5846 [1] and would want to push these to master. Changes impact "ml" module, more details of portion of code can be found in PR #3030 [2]. Yury Babak [3], Oleg Ignatenko[4] did review and sanity check. The main idea was to keep

request for contributors permissions

Hello! I need permissions to assign jira task to me My account: vv.timoshenko Thanks!

[GitHub] ignite pull request #3047: Ignite-gg-12943-1.9

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3047 Ignite-gg-12943-1.9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12943 Alternatively you can review

[GitHub] ignite pull request #3048: IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCa...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3048 IGNITE-6932 GridQueryProcessor.querySqlFieldsNoCache should check for… … cluster active/inactive state You can merge this pull request into a Git repository by running: $ git

[GitHub] ignite pull request #2896: IGNITE-6649: Add EvictionPolicy factory support i...

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

[GitHub] ignite pull request #2871: Ignite-gg-12960

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

[GitHub] ignite pull request #2853: gg-12957

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

[jira] [Created] (IGNITE-6942) Auto re-connect to other node in case of failure of current

Mikhail Cherkasov created IGNITE-6942: - Summary: Auto re-connect to other node in case of failure of current Key: IGNITE-6942 URL: https://issues.apache.org/jira/browse/IGNITE-6942 Project:

Re: request for contributors permissions

Hello Sergey, Granted the permissions. Please go ahead and pick ticket you like. Some extra info that might be useful for you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute

Re: Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

Hi Alex, Impressive, thanks for sharing this with us. Btw, do we need to tweak the existing OLS documentation to mention the contributed changes? https://apacheignite.readme.io/docs/ols-multiple-linear-regression — Denis > On Nov 16, 2017, at 5:55 AM, Alexey Zinoviev

Re: Meetup tonight in Santa Clara CA: "In-Memory Computing Essentials for Java Developers"

Tom, Thanks for promoting the workshop! Igniters, minor correction, that’s gonna be the first 2.5 hours advanced workshop on Ignite internals and capabilities. Join me at 6.30 PM today if you’re Silicon Valley. By the end of the workshop the you will learn how: • Configure and deploy Apache

Re: request for contributors permissions

Hi, Welcome to the community! Some extra info that might be useful for you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

IGNITE-6745. Status

Hi, igniters Why no one commented on the patch and pull request (https://github.com/apache/ignite/pull/2970) ? What should I do ? Regards, Cergey Chaulin

[jira] [Created] (IGNITE-6944) Fail to execute task with immutable list string

Edmond Tsang created IGNITE-6944: Summary: Fail to execute task with immutable list string Key: IGNITE-6944 URL: https://issues.apache.org/jira/browse/IGNITE-6944 Project: Ignite Issue Type:

[GitHub] ignite pull request #3043: Ignite 5938 master

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/3043 Ignite 5938 master PR for tests run. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5938-master Alternatively

[jira] [Created] (IGNITE-6930) Non-persistent free lists

Vladimir Ozerov created IGNITE-6930: --- Summary: Non-persistent free lists Key: IGNITE-6930 URL: https://issues.apache.org/jira/browse/IGNITE-6930 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6931) Avoid extra deserialization on index rebuild

Igor Seliverstov created IGNITE-6931: Summary: Avoid extra deserialization on index rebuild Key: IGNITE-6931 URL: https://issues.apache.org/jira/browse/IGNITE-6931 Project: Ignite Issue

[jira] [Created] (IGNITE-6932) GridQueryProcessorюquerySqlFieldsNoCache should check for cluster active/inactive state

Vladimir Ozerov created IGNITE-6932: --- Summary: GridQueryProcessorюquerySqlFieldsNoCache should check for cluster active/inactive state Key: IGNITE-6932 URL: https://issues.apache.org/jira/browse/IGNITE-6932

Confusing slf4j error messages

Hi Igniters, Ignite examples and Ignite itself with some configurations prints out annoying messages related to slf4j: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See

[jira] [Created] (IGNITE-6933) Consider executing updates in-place when SQL indexes are present or object size is smaller than the old object size

Alexey Goncharuk created IGNITE-6933: Summary: Consider executing updates in-place when SQL indexes are present or object size is smaller than the old object size Key: IGNITE-6933 URL:

Re: Adding Persistent Memory Support for Ignite

Hi Mulugeta, Where can I find documentation about LLPL to understand how memory and persistence are handled there? D. On Thu, Nov 16, 2017 at 7:16 AM, Mammo, Mulugeta wrote: > Hi all, > > > > Ignite, when persistence mode is enabled, stores data and indexes on disk.

Re: Should we enable write throttling by default?

I agree. Moreover, peak throughput after long idle period won't be decreased. Throttling works only during ongoing checkpoint (and probability of checkpoint running after idle period is very low). Best Regards, Ivan Rakov On 16.11.2017 10:52, Dmitry Pavlov wrote: Yes, it is correct. But

[GitHub] ignite pull request #3039: IGNITE-6911 .NET: Optionally disable Java console...

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

[GitHub] ignite pull request #3041: Ignite gg 13067

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3041 Ignite gg 13067 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13067 Alternatively you can review and

[jira] [Created] (IGNITE-6928) Web console: use redesigned context menus everywhere

Ilya Borisov created IGNITE-6928: Summary: Web console: use redesigned context menus everywhere Key: IGNITE-6928 URL: https://issues.apache.org/jira/browse/IGNITE-6928 Project: Ignite Issue

[GitHub] ignite pull request #2935: IGNITE-6336 .NET: Thin client: Create cache

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

Re: Should we enable write throttling by default?

Has anyone benchmarked the write-throttling? Would be nice to see the CPU and memory graphs. On Thu, Nov 16, 2017 at 12:03 AM, Ivan Rakov wrote: > I agree. > > Moreover, peak throughput after long idle period won't be decreased. > Throttling works only during ongoing

WEBINARS: Apache Ignite Essentials for Architects and Java Developers

Igniters, I’m pleased to invite all of you to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms such as Apache Ignite. That will be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply

[GitHub] ignite pull request #3042: IGNITE-6590: TCP port in bin/control.sh differs f...

GitHub user MikeZhur opened a pull request: https://github.com/apache/ignite/pull/3042 IGNITE-6590: TCP port in bin/control.sh differs from default You can merge this pull request into a Git repository by running: $ git pull https://github.com/MikeZhur/ignite ignite-2.2

[jira] [Created] (IGNITE-6943) Web console: LoadCahces method should activate cluster if persistent is configured, otherwise method doesn't work due to cluster is inactive

Pavel Konstantinov created IGNITE-6943: -- Summary: Web console: LoadCahces method should activate cluster if persistent is configured, otherwise method doesn't work due to cluster is inactive Key: IGNITE-6943

Re: Add support of distributed matrices for OLS regression. (PR #3030 / IGNITE-5846)

The documentation is corect, all changes are added for internals in reality, without changes in API. 17 нояб. 2017 г. 1:35 AM пользователь "Denis Magda" написал: > Hi Alex, > > Impressive, thanks for sharing this with us. Btw, do we need to tweak the > existing OLS

[jira] [Created] (IGNITE-6929) Preserve mvcc versions on index rebuild

Igor Seliverstov created IGNITE-6929: Summary: Preserve mvcc versions on index rebuild Key: IGNITE-6929 URL: https://issues.apache.org/jira/browse/IGNITE-6929 Project: Ignite Issue Type: