Re: Ignite not friendly for Monitoring

re about how monitoring works - this is responsibility of customer's DevOps. Our responsibility is consistent event logging. Thank you! Best regards, Alexey On Tuesday, August 15, 2017, 6:16:25 PM GMT+3, Alexey Kuznetsov <akuznet...@apache.org> wrote: Alexey, How you are going to deal wi

Re: [jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

Hi Alex, Please specify "--port 11211" port when running "control.sh --activate". Also, add --host IGNITE_NODE if you run control.sh on a host where there are no ignite nodes. For example: ./bin/control.sh --host 127.0.0.1 --port 11211 --activate It looks we have an issue that default Ignite

Re: Ignite not friendly for Monitoring

s like DynaTrace or Nagios? Is this all we need? — Denis > On Aug 14, 2017, at 5:02 AM, Alexey Kukushkin > <alexeykukush...@yahoo.com.INVALID> wrote: > > Igniters, > While preparing some Ignite materials for Administrators I found Ignite is > not friendly for s

Ignite not friendly for Monitoring

Igniters, While preparing some Ignite materials for Administrators I found Ignite is not friendly for such a critical DevOps practice as monitoring.  TL;DRI think Ignite misses structured descriptions of abnormal events with references to event IDs in the logs not changing as new versions are

Re: [jira] [Created] (IGNITE-6026) init cluster for Ignite Ignite Persistence by xml

Hi Alex, The main idea from the API perspective is that Ignite Persistence is transparent for the API. After you enable persistence all your APIs including get/put, SQL, etc would work as before.  Enable Persistence with 1 line: And then activate cluster explicitly - With script:

IGNITE-4901 (Decrease logging level for DataStremer retry)

Hi, Presently when DataStreamer is flushing data and cluster topology changes, the DataStreamer would output an ERROR message to the console and retry flushing the data with the latest topology.  We have this IGNITE-4901 issue asking to decrease logging level since a topology change is normal

I am a new Ignite Development Community member

Dear Ignite Development Community, I am a software engineer and joined the community to contribute to the product. Could you please help with granting me proper Ignite Jira permissions? My Jira user ID is "kukushal". Thank you! Best regards, Alexey

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Ray, Yakov just pointed me to this thread where user had a problem with IP address changing between the cluster restarts. The persistent data directories inside work/db have names

Re: integrate with prestodb

Cross-sending to the DEV community. On Mon, Oct 16, 2017 at 12:14 PM, shawn.du wrote: > Hi community, > > I am trying to implement a connector for presto to connect ignite. > I think it will be a very interest thing to connect ignite and presto. > > In fact, currently

Re: Some questions regard Cache Query and performance

Aaron, let me forward this to DEV: Ignite DEV community, I tried to confirm setLocal(true) semantics for ContinuousQuery and I have got not what I expected. I found that executing a ContinuousQuery with setLocal(true): - Still executes initial query remotely - Listens for modifications

Re: Massive commit sizes for processes with local Ignite Grid servers

Raymond, So you see 3 "extra" GB that your server app takes. Is it possible your app really loads additional 3GB of referenced libraries and data besides Ignite? Did you try temporarily changing the code to NOT start Ignite and see how much memory such an app takes? On Thu, Sep 7, 2017 at 1:49

Re: Massive commit sizes for processes with local Ignite Grid servers

OK, please ignore - I see you might have found a cause in the other thread. On Thu, Sep 7, 2017 at 2:45 PM, Alexey Kukushkin <kukushkinale...@gmail.com> wrote: > Raymond, > > So you see 3 "extra" GB that your server app takes. Is it possible your > app really loads

Re: Ignite: configuration changes at runtime

I would vote for not automatically persisting runtime configuration changes. Still it makes sense to expose a "save(fileName)" method to allow explicitly saving changes to a different or same config file. On Mon, Aug 21, 2017 at 5:22 PM, Dmitriy Setrakyan wrote: > On Mon,

Re: Ignite node crashes after one query fetches many entries from cache

Ignite Developers, I know community is developing an "Internal Problems Detection" feature . Do you know if it addresses the problem Ray described below? May be we already have a setting to prevent

Re: Transport compression (not store compression)

Forwarding to DEV list: Ignite developers, could you please share your thoughts on how hard it is to extend Ignite to compress data on the network. On Wed, Nov 22, 2017 at 10:04 AM, Gordon Reid (Nine Mile) < gordon.r...@ninemilefinancial.com> wrote: > Hi Igniters, > > > > I see there is a lot of

Re: Ignite Events Remote Filter

Also, I ran our CacheEventsExample and I confirm the remote filter is NOT unsubscribed when it returns false. So it looks like a documentation bug only. On Fri, Oct 27, 2017 at 1:10 PM, Alexey Kukushkin <kukushkinale...@gmail.com > wrote: > Hi, > > I think it is a document

Re: Ignite Events Remote Filter

Hi, I think it is a documentation bug. I do not think remote listener will be unsubscribed if it returns false. Let's confirm with the developers community. *Ignite Developers*, We have this comment for the remoteListener argument of the IgniteEvents#remoteListen(...): rmtFilter - Filter

Thin client: Java bindings

Igniters, I am working on a project where users will use Ignite via a thin client protocol. The API will be Java and the client will have to support failover and encryption. I know community already developed the thin client protocol and .NET bindings and is going to develop failover and

Re: Adopting mock framework (ex. Mockito) for unit tests

Hi Jason, I heartily support unit testing practices and introducing a mocking framework into ignite development environment. Today I can hardly find a single unit test in Apache Ignite, which does not allow me to use the best TDD and CI/CD practices like running tests on every commit (or even on

Re: Thin client: Java bindings

Dmitriy, Although having invoke() was really important for us, implementing invoke() does not look trivial (need to think about real multi-lingual and cross-platform design) and we do not have time to implement it on the first phase. Currently thin client protocol does not support it so we would

Re: Thin client: Java bindings

We also need asynchronous versions of all the thin client APIs. I created JIRA-7623 to address async APIs. Proposed design: Async methods are named by appending "Async" to the corresponding syncMethod, e.g. putAsync, clearAsync. Async methods

Re: Ignite Thin clients for Node.js, Python, PHP

Alexey, Ekaterina, Pavel, These resources will be useful for you: - Thin client protocol spec - .NET thin client code

Re: Ignite Thin clients for Node.js, Python, PHP

Also, we could have a Hangouts call or something to share thin client development experience. You can reach me at kukushkinale...@gmail.com.

Re: Thin client: Java bindings

Igniters! Could you please help with the Java thin client code review: Documentation <https://apacheignite.readme.io/v2.3/docs/java-thin-client> Code <https://reviews.ignite.apache.org/apache-ignite/review/IG-CR-23> Thank you for the help. On Mon, Feb 5, 2018 at 5:45 PM, Alex

Re: Thin client / Binary protocol: questions

Will be available in several weeks. It is >> better to skip this part for now. > > > Let's give a reference to the branch where the guys can see those changes > at the protocol level. My guess they want to know what to expect and how it > can affect the design they've been worki

Re: IGNITE-6879

Dmitry, Roman, I can review the fix - send me a code review link when it is ready. On Wed, Mar 14, 2018 at 5:14 PM, Dmitry Pavlov <dpavlov@gmail.com> wrote: > Igniters, > > it is about spring-data integration support. > > Who has intereset about styding this technology?

Re: IGNITE-6879

Roman, Just two small comments from me: 1. I suggest renaming IgniteSpringDataTestSuite to IgniteSpringData2TestSuite: we must be able to test both spring-data and spring-data-2 JARs with single "mvn test" 2. Make sure "Ignite Spring Data" test job in TeamCity is extended to run

Re: IGNITE-6879

Roman, Just pay commiter's (Dmitry Pavlov will most likely commit your code) attention to include the new test suite to TeamCity configuration.

Re: IGNITE-6879

Roman, Dmitry, I also reviewed the fix and the code looks OK to me. But the fix has significant implication - Ignite no longer can be used with spring-data 1.0 due to no backward compatibility between spring 2.0 and 1.0 APIs. With this approach we must remember to add corresponding spring-data

Re: What's about releasing Ignite 2.5 a bit earlier?

Denis, Java thin client is in the final review stage - I expect it will go to master sometime next week. April 30 release date seems to have enough contingency for this component. Thanks!

Re: Lightweight profiling of messages processing

Hi Alexei, Did you consider general-purpose APM tools like free InspectIT or commercial DynaTrace or AppDynamics ? Java APM tools

Re: {DISCUSSION] Cluster read-only mode.

I agree with Ivan's concern - do we really need the "activation" concept in Ignite? Activation was introduced with Ignite persistence: we must prevent both the read and write operations on a cluster with persistence on until full data set is loaded (all the nodes are started). Cluster

Re: Replacing NodeFilter functionality with label approach

Pavel, Just a real example you asked for: we have a user attribute "ROLE_DC", which is a comma separated list like "wfe_a, as_a, db_a" (server role and data center designator) and we have node filters to deploy services and start caches on servers with specific role (like WFE) and sometimes

Re: Java thin client errors handling

Hi Guys, Most likely I just forgot to remove the "internal" ClientError and ClientProtocolError when I was implementing a review comment to merge the Java thin client into ignite-core (originally I developed the Java thin client as a separate module). I see that the ClientProtocolError is not

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Denis,I like your idea. It would be like native "OKVM" (Object-KeyValue Mapper) allowing Ignite to natively operate on domain entities. It also means no key and value data duplication and thus addressing the original SQL DML problem when only key field is modified.We could add a

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

> «Why SQL sets both fields? I just want to set the key object field!» The solution from IGNITE-12807 has backward compatible API: you have to explicitly specify fields having same name inside the Key and Value. Otherwise the semantics is as is. Denis's solution (that I like) is a new API not

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Nikolay, I think you and I agree here: there is no problem at all if the user uses K/Vs in domain model OR developed a domain-to-K/V mapper OR does not use SQL DML. I think we just have different experience as to how "popular" is the user's unwillingness to use one of the three existing

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Denis, I like your proposal and will be glad to participate in developing a solution in that way. In additional to Nikolay's opinion about your ideas I think it is important to get Dmitry Frolov's (who started the discussion) and Alexey Sasov's (who also voted for the having this enhancement)

Re: [DISCUSSION] Consistency across java thin/thick APIs

I am wrong Alex but let me provide some history: when I originally developed the Java thin client 3 years ago I suggested to take all public API out of ignite-core.jar into a separate ignite-api.jar and develop Java thin client implementing the common API from the ignite-api.jar. So the

Re: [DISCUSSION] Ignite.C++ and CMake

+1. I recently completed a cross-IDE (MS Visual Studio & GCC/GDB) Ignite C++ project and CMake in Ignite C++ would save me a day of effort. вт, 26 мая 2020 г. в 12:09, Pavel Tupitsyn : > +1 > > On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky > wrote: > > > > > Ivan huge +1 with your

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

I vote for implementing this enhancement: having key information separated from value means either cluttering domain model with KeyValue/CacheEntry-like structures or developing an Ignite data access layer to insert key info into domain entity after getting it from Ignite. Although both the

Interoperable Ignite.NET Dates

Igniters, What do you think about changing .NET API to read/write portable dates by default and making that really portable? *The Problem* Presently .NET API writes dates as composite Ignite objects. Only .NET clients can read such dates: any other client (JDBC, Java, etc) does not understand it

Re: Interoperable Ignite.NET Dates

Val, absolutely - our proposal affects .NET API only. вт, 3 нояб. 2020 г. в 15:00, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Got it. So it only affects the .NET side, correct? > > -Val > > On Tue, Nov 3, 2020 at 3:52 AM Alexey Kukushkin > > wrote

Re: Interoperable Ignite.NET Dates

te 3.0, correct? > > Pavel > > On Tue, Nov 3, 2020 at 12:13 AM Alexey Kukushkin < > kukushkinale...@gmail.com> > wrote: > > > Igniters, > > > > What do you think about changing .NET API to read/write portable dates by > > default and making that really p

Re: Interoperable Ignite.NET Dates

https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach > > -Val > > On Tue, Nov 3, 2020 at 12:05 AM Alexey Kukushkin < > kukushkinale...@gmail.com> > wrote: > > > Pavel, > > > > We propose changing public API so this is fo

Re: Interoperable Ignite.NET Dates

t;: > Cool, makes sense to me then. Please feel free to create a ticket and mark > it with the "ignite-3" label. > > -Val > > On Tue, Nov 3, 2020 at 4:03 AM Alexey Kukushkin > > wrote: > > > Val, absolutely - our proposal affects .NET API o

Re: Interoperable Ignite.NET Dates

> > Would you like to prepare an IEP? > > Thanks, > Pavel > > > > On Tue, Nov 3, 2020 at 3:15 PM Alexey Kukushkin > > wrote: > > > We already created tickets and tested the proposed solution with our > > applications (already in PROD) and an internal fork

Re: [DISCUSSION] IgniteFuture class future in Ignite-3.0.

I do not like Java's CompletableFuture and prefer our own Future (revised IgniteFuture). My understanding of the Future (or Promise) pattern in general is having two separate APIs: 1. Server-side: create, set result, raise error, cancel from server. 2. Client-side: get result, handle

Re: IEP-70: Async Continuation Executor

Hi Pavel, Extending Java async API with additional Executor parameters looks OK to me. It is not clear from the IEP how you are going to do that for .NET async API. My understanding is in .NET we do not add any Executors. Instead, the Ignite Async API should use (SynchronizationContext.Current

Re: IEP-70: Async Continuation Executor

he.GetAsync()' to allow the calling > context to optimise the calling model dynamically? > > Thanks, > Raymond. > > > On Wed, Mar 17, 2021 at 6:14 AM Alexey Kukushkin < > kukushkinale...@gmail.com> > wrote: > > > Pavel, > > > > My underst

Re: IEP-70: Async Continuation Executor

Pavel, So what you are saying is submitting a continuation to .NET Thread Pool already respects current SynchronizationContext and ConfigureAwait. In this case the IEP looks complete (for some reason I thought that we should take care about the SynchronizationContext inside the Ignite.NET

Re: IEP-70: Async Continuation Executor

s with a > > timeout? > > I think that implicit using java pools to run a code that can be hung is > a > > questionable solution. > > > > вт, 16 мар. 2021 г. в 23:30, Alexey Kukushkin >: > > > > > Pavel, > > > > > > So what y

Re: IEP-70: Async Continuation Executor

steners will be invoked on > ForkJoinPool#commonPool (instead of striped pool). > So .NET continuations will end up in commonPool as well, which solves the > problem for .NET automatically, no changes required. > > Does that make sense? > > On Tue, Mar 16, 2021 at 1:52 PM Alexey

Re: [DISCUSSION] Javadoc style requirements and checks in Ignite-3.

I personally do not understand why we need mandatory javadoc even in public modules. I think javadoc is needed only when the code is not self-descriptive. What value does a javadoc like this bring

Re: [DISCUSSION] Error handling in Ignite 3

Just some points looking questionable to me, although I realize the error handling style may be very opinionated: - Would it make sense splitting the proposed composite error code (TBL-0001) into separate numeric code (0001) and scope/category ("TBL") to avoid parsing the code when an

[DISCUSSION] IgniteOutOfMemoryException may not be a critical failure

Hi Igniters, Currently Ignite treats the "not enough data region capacity" case as a critical failure and does not allow configuring any of the default critical failure handlers to ignore that error. In our company we have different teams using Apache Ignite and none of them wants to apply a

[jira] [Created] (IGNITE-5966) IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

Alexey Kukushkin created IGNITE-5966: Summary: IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory Key: IGNITE-5966

[jira] [Created] (IGNITE-6879) Support Spring 2.0

Alexey Kukushkin created IGNITE-6879: Summary: Support Spring 2.0 Key: IGNITE-6879 URL: https://issues.apache.org/jira/browse/IGNITE-6879 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7065) Cannot use multiple Ignite Kafka Sink Connectors

Alexey Kukushkin created IGNITE-7065: Summary: Cannot use multiple Ignite Kafka Sink Connectors Key: IGNITE-7065 URL: https://issues.apache.org/jira/browse/IGNITE-7065 Project: Ignite

[jira] [Created] (IGNITE-7248) "Schema not found" error when setting streaming mode for JDBC driver

Alexey Kukushkin created IGNITE-7248: Summary: "Schema not found" error when setting streaming mode for JDBC driver Key: IGNITE-7248 URL: https://issues.apache.org/jira/browse/IGNITE-7248

[jira] [Created] (IGNITE-7215) Documentation bug: "Cross-cache Query" page is dead

Alexey Kukushkin created IGNITE-7215: Summary: Documentation bug: "Cross-cache Query" page is dead Key: IGNITE-7215 URL: https://issues.apache.org/jira/browse/IGNITE-7215 Proje

[jira] [Created] (IGNITE-6889) ignite.queue() returns null when queue configuration is null

Alexey Kukushkin created IGNITE-6889: Summary: ignite.queue() returns null when queue configuration is null Key: IGNITE-6889 URL: https://issues.apache.org/jira/browse/IGNITE-6889 Project: Ignite

[jira] [Created] (IGNITE-6802) NullPointerException when WAL store and WAL archive paths are same

Alexey Kukushkin created IGNITE-6802: Summary: NullPointerException when WAL store and WAL archive paths are same Key: IGNITE-6802 URL: https://issues.apache.org/jira/browse/IGNITE-6802 Project

[jira] [Created] (IGNITE-6801) Ignite Kafka Connector certification with Confluent

Alexey Kukushkin created IGNITE-6801: Summary: Ignite Kafka Connector certification with Confluent Key: IGNITE-6801 URL: https://issues.apache.org/jira/browse/IGNITE-6801 Project: Ignite

[jira] [Created] (IGNITE-7422) Thin client Java API - startClient

Alexey Kukushkin created IGNITE-7422: Summary: Thin client Java API - startClient Key: IGNITE-7422 URL: https://issues.apache.org/jira/browse/IGNITE-7422 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-7421) Thin client Java API - data grid API

Alexey Kukushkin created IGNITE-7421: Summary: Thin client Java API - data grid API Key: IGNITE-7421 URL: https://issues.apache.org/jira/browse/IGNITE-7421 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7423) Thin client Java API - cache management

Alexey Kukushkin created IGNITE-7423: Summary: Thin client Java API - cache management Key: IGNITE-7423 URL: https://issues.apache.org/jira/browse/IGNITE-7423 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7424) Thin client Java API - cache enumeration

Alexey Kukushkin created IGNITE-7424: Summary: Thin client Java API - cache enumeration Key: IGNITE-7424 URL: https://issues.apache.org/jira/browse/IGNITE-7424 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7426) Thin client Java API - encryption

Alexey Kukushkin created IGNITE-7426: Summary: Thin client Java API - encryption Key: IGNITE-7426 URL: https://issues.apache.org/jira/browse/IGNITE-7426 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-7427) Thin client Java API - failover

Alexey Kukushkin created IGNITE-7427: Summary: Thin client Java API - failover Key: IGNITE-7427 URL: https://issues.apache.org/jira/browse/IGNITE-7427 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-7430) Thin client Java API - cache putAll/getAll

Alexey Kukushkin created IGNITE-7430: Summary: Thin client Java API - cache putAll/getAll Key: IGNITE-7430 URL: https://issues.apache.org/jira/browse/IGNITE-7430 Project: Ignite Issue

[jira] [Created] (IGNITE-7429) Thin client Java API - cache put/get/contains

Alexey Kukushkin created IGNITE-7429: Summary: Thin client Java API - cache put/get/contains Key: IGNITE-7429 URL: https://issues.apache.org/jira/browse/IGNITE-7429 Project: Ignite Issue

[jira] [Created] (IGNITE-7433) Thin client Java API - cache clear

Alexey Kukushkin created IGNITE-7433: Summary: Thin client Java API - cache clear Key: IGNITE-7433 URL: https://issues.apache.org/jira/browse/IGNITE-7433 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-7432) Thin client Java API - cache atomic get/put/replace/remove

Alexey Kukushkin created IGNITE-7432: Summary: Thin client Java API - cache atomic get/put/replace/remove Key: IGNITE-7432 URL: https://issues.apache.org/jira/browse/IGNITE-7432 Project: Ignite

[jira] [Created] (IGNITE-7434) Thin client Java API - cache query API

Alexey Kukushkin created IGNITE-7434: Summary: Thin client Java API - cache query API Key: IGNITE-7434 URL: https://issues.apache.org/jira/browse/IGNITE-7434 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7435) Thin client Java API - fields query API

Alexey Kukushkin created IGNITE-7435: Summary: Thin client Java API - fields query API Key: IGNITE-7435 URL: https://issues.apache.org/jira/browse/IGNITE-7435 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7425) Thin client Java API - binary objects

Alexey Kukushkin created IGNITE-7425: Summary: Thin client Java API - binary objects Key: IGNITE-7425 URL: https://issues.apache.org/jira/browse/IGNITE-7425 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7431) Thin client Java API - cache replace/remove API

Alexey Kukushkin created IGNITE-7431: Summary: Thin client Java API - cache replace/remove API Key: IGNITE-7431 URL: https://issues.apache.org/jira/browse/IGNITE-7431 Project: Ignite

[jira] [Created] (IGNITE-7411) JDBC thin client selects NULL cache ID values of entries added with Java API

Alexey Kukushkin created IGNITE-7411: Summary: JDBC thin client selects NULL cache ID values of entries added with Java API Key: IGNITE-7411 URL: https://issues.apache.org/jira/browse/IGNITE-7411

[jira] [Created] (IGNITE-7623) Thin client Java API - async API

Alexey Kukushkin created IGNITE-7623: Summary: Thin client Java API - async API Key: IGNITE-7623 URL: https://issues.apache.org/jira/browse/IGNITE-7623 Project: Ignite Issue Type: Sub

[jira] [Created] (IGNITE-9197) Java thin client querying empty table results in NoSuchElementException

Alexey Kukushkin created IGNITE-9197: Summary: Java thin client querying empty table results in NoSuchElementException Key: IGNITE-9197 URL: https://issues.apache.org/jira/browse/IGNITE-9197

[jira] [Created] (IGNITE-9204) Test org.apache.ignite.client.ReliabilityTest@testFailover fails intermittently

Alexey Kukushkin created IGNITE-9204: Summary: Test org.apache.ignite.client.ReliabilityTest@testFailover fails intermittently Key: IGNITE-9204 URL: https://issues.apache.org/jira/browse/IGNITE-9204

[jira] [Created] (IGNITE-9357) Spark Structured Streaming with Ignite as data source and sink

Alexey Kukushkin created IGNITE-9357: Summary: Spark Structured Streaming with Ignite as data source and sink Key: IGNITE-9357 URL: https://issues.apache.org/jira/browse/IGNITE-9357 Project

[jira] [Created] (IGNITE-7858) "Cannot find cache" error for existing cache on unstable topology

Alexey Kukushkin created IGNITE-7858: Summary: "Cannot find cache" error for existing cache on unstable topology Key: IGNITE-7858 URL: https://issues.apache.org/jira/browse/IGNITE-7858

[jira] [Created] (IGNITE-8135) Missing SQL-DDL Authorization

Alexey Kukushkin created IGNITE-8135: Summary: Missing SQL-DDL Authorization Key: IGNITE-8135 URL: https://issues.apache.org/jira/browse/IGNITE-8135 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-8221) Cache management and server node authorisation

Alexey Kukushkin created IGNITE-8221: Summary: Cache management and server node authorisation Key: IGNITE-8221 URL: https://issues.apache.org/jira/browse/IGNITE-8221 Project: Ignite

[jira] [Created] (IGNITE-8237) Ignite blocks on SecurityException in exchange-worker due to unauthorised off-heap cache configuration

Alexey Kukushkin created IGNITE-8237: Summary: Ignite blocks on SecurityException in exchange-worker due to unauthorised off-heap cache configuration Key: IGNITE-8237 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-8076) Java Thin Client Authentication

Alexey Kukushkin created IGNITE-8076: Summary: Java Thin Client Authentication Key: IGNITE-8076 URL: https://issues.apache.org/jira/browse/IGNITE-8076 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-8067) Java thin client code review: move parsing from TcpClientCache to ClientMessageParser

Alexey Kukushkin created IGNITE-8067: Summary: Java thin client code review: move parsing from TcpClientCache to ClientMessageParser Key: IGNITE-8067 URL: https://issues.apache.org/jira/browse/IGNITE-8067

[jira] [Created] (IGNITE-10100) No public Java API to call Ignite.NET service

Alexey Kukushkin created IGNITE-10100: - Summary: No public Java API to call Ignite.NET service Key: IGNITE-10100 URL: https://issues.apache.org/jira/browse/IGNITE-10100 Project: Ignite

[jira] [Created] (IGNITE-10072) Apache.Ignite NuGet package removes existing post-build actions

Alexey Kukushkin created IGNITE-10072: - Summary: Apache.Ignite NuGet package removes existing post-build actions Key: IGNITE-10072 URL: https://issues.apache.org/jira/browse/IGNITE-10072 Project

[jira] [Created] (IGNITE-10074) Structured Exception information is lost when Ignite .NET client calls Ignite Java service

Alexey Kukushkin created IGNITE-10074: - Summary: Structured Exception information is lost when Ignite .NET client calls Ignite Java service Key: IGNITE-10074 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-10075) Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET

Alexey Kukushkin created IGNITE-10075: - Summary: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET Key: IGNITE-10075 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-10073) Ignite NuGet package without embedded Ignite JARs

Alexey Kukushkin created IGNITE-10073: - Summary: Ignite NuGet package without embedded Ignite JARs Key: IGNITE-10073 URL: https://issues.apache.org/jira/browse/IGNITE-10073 Project: Ignite

[jira] [Created] (IGNITE-9454) SecurityPermissionSetBuilder fails to append system permission CACHE_CREATE

Alexey Kukushkin created IGNITE-9454: Summary: SecurityPermissionSetBuilder fails to append system permission CACHE_CREATE Key: IGNITE-9454 URL: https://issues.apache.org/jira/browse/IGNITE-9454

[jira] [Created] (IGNITE-10430) Ignite.NET Data Region Metrics: PagesRead, PagesWritten, PagesReplaced, OffHeapSize, OffheapUsedSize

Alexey Kukushkin created IGNITE-10430: - Summary: Ignite.NET Data Region Metrics: PagesRead, PagesWritten, PagesReplaced, OffHeapSize, OffheapUsedSize Key: IGNITE-10430 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-10874) JDBC thin driver metadata misses caches with queryEntities and names containing underscores

Alexey Kukushkin created IGNITE-10874: - Summary: JDBC thin driver metadata misses caches with queryEntities and names containing underscores Key: IGNITE-10874 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-12898) Server node with CacheStore fails to re-join the cluster: IgniteCheckedException: Cannot enable read-through (loader or store is not provided) for cache

Alexey Kukushkin created IGNITE-12898: - Summary: Server node with CacheStore fails to re-join the cluster: IgniteCheckedException: Cannot enable read-through (loader or store is not provided) for cache Key: IGNITE-12898

[jira] [Created] (IGNITE-12894) Cannot use IgniteAtomicSequence in Ignite services

Alexey Kukushkin created IGNITE-12894: - Summary: Cannot use IgniteAtomicSequence in Ignite services Key: IGNITE-12894 URL: https://issues.apache.org/jira/browse/IGNITE-12894 Project: Ignite

[jira] [Created] (IGNITE-12901) SQL: Uncorrelated subquery should run only once.

Alexey Kukushkin created IGNITE-12901: - Summary: SQL: Uncorrelated subquery should run only once. Key: IGNITE-12901 URL: https://issues.apache.org/jira/browse/IGNITE-12901 Project: Ignite

  1   2   >