Dmitry,
yes, test attached to the ticket.
On Wed, Sep 16, 2015 at 12:04 AM, Dmitriy Setrakyan wrote:
> Andrey,
>
> Do we have instructions to reproduce this issue?
>
> D.
>
> On Tue, Sep 15, 2015 at 9:35 PM, Andrey Gura wrote:
>
> > Guys,
> >
> > I&#
ibed methods have asynchronous analogs." But there are no async
> operations in it's implemenation.
>
> Is this a bug in documentation of we forgot to implement them?
>
> Vladimir.
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
ly update the documentation to reflect
> the
> > reality?
> >
> > On Thu, Sep 17, 2015 at 3:30 PM, Andrey Gura wrote:
> >
> > > There is the same comment for the following interfaces:
> > >
> > > - IgniteAtomicReference
> > > - IgniteAto
ide
> > > > updates by the end of the day.
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-1516 - performance
> > offheap
> > > > query benchmark is not fully recovered. Semyon will be fixing it.
> > Sergi,
> > > > can you please assist?
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-973 - Semyon has fixed
> > race
> > > > in
> > > > cache logic, but issue is still reproducible due to possible issues
> in
> > > > indexing logic. Sergi, this is on you. Can you please take a look?
> > > >
> > > > --Yakov
> > > >
> > >
> >
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
for a given key.
> Essentially,
> > > what I want is a cluster group affinity that is not associated with any
> > > cache. How can I do it?
> > >
> >
> > Andrey, perhaps you could just take our affinity function and use it
> > directly, no?
> >
> >
> > >
> > > Thanks
> > > Andrey
> > >
>
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
tmail.com>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I have a user-defined cluster group and I'd like to be able to
> > > > > consistently pick the same node in the group for a given key.
> > > Essentially,
> > > > > what I want is a cluster group affinity that is not associated
> with any
> > > > > cache. How can I do it?
> > > > >
> > > >
> > > > Andrey, perhaps you could just take our affinity function and use it
> > > > directly, no?
> > > >
> > > >
> > > > >
> > > > > Thanks
> > > > > Andrey
> > > > >
> > >
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
>
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Could you please clarify?
> > > > >
> > > > > Thanks a lot
> > > > > Andrey
> > > > >
> > > > > > From: dsetrak...@apache.org
> > > > > > Date: Mon, 5 Oct 2015 09:53:25 -0700
> > > > > >
on
warning message. So I have two questions:
1. Is there any objections about it?
2. What message will be more informative than current one ("Local node's
java major version is different from remote node's one
[locJvmMajVer=, rmtJvmMajVer=]")?
--
Andrey Gura
G
has the same major version, but
> different vendors, it might be even more important concern, than different
> major versions of the same vendor.
>
> On Thu, Oct 8, 2015 at 8:48 PM, Dmitriy Setrakyan
> wrote:
>
> > On Thu, Oct 8, 2015 at 9:52 AM, Andrey Gura wrote:
>
o believe the current implementation of IgniteRDD is only good to be used
> from Scala, unless I am completely wrong and don't know what I am talking
> about. Which might be quite possible, of course.
>
> My question is very simple: is there a way to use IgniteRDD from
> Java-la
> http://docs.spring.io/spring-boot/docs/1.3.0.M1/reference/html/boot-features-caching.html
>
> If not, we should definitely add such integration.
>
> D.
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Oops, I didn't noticed.
Ok, it means we already have this integration.
On Thu, Nov 5, 2015 at 6:54 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Andrey, we already have this. See SpringCacheManager class.
>
> -Val
>
> On Thursday, November 5
e support all these?
>
> D.
>
> On Thu, Nov 5, 2015 at 8:00 AM, Andrey Gura wrote:
>
> > Oops, I didn't noticed.
> >
> > Ok, it means we already have this integration.
> >
> > On Thu, Nov 5, 2015 at 6:54 PM, Valentin Kulichenko <
> &
> > Also note that we have a documentation page for this feature:
> > https://apacheignite.readme.io/docs/spring-caching
> >
> > On Thu, Nov 5, 2015 at 10:10 AM, Andrey Gura wrote:
> >
> > > We should not support this annotations. All listed annotation
> (excludin
gt; behavior seems very confusing. And actually it means that our examples
> don't work out of the box with disabled multicast.
>
> This user seems to have the same issue:
>
> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
>
> -Val
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
7500
> for some reason. I can't do this with telnet either, which is confusing
> because the first one binds to 0.0.0.0 and therefore should be accessible
> via all interfaces.
>
> -Val
>
> On Thu, Nov 5, 2015 at 4:45 PM, Andrey Gura wrote:
>
> > Val,
> >
>
Guys,
>
> we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack.
> Does
> anyone here has/can share with us the interpreter.json content for Ignite,
> so
> we don't need to re-invent the wheel?
>
> Thanks in advance!
> --
> Take care,
> Cos
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> Cos' pubkey: http://people.apache.org/~cos/cos.asc
>
> Wisdom of the hour
>
> You will have domestic happiness and faithful friends.
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
issue occurs only for atomic caches with
> > writeSynchronizedMode=ASYNC|PRIMARY_SYNC
> > Eviction for TX caches and for ATOMIC with
> writeSynchronizedMode=FULL_SYNC
> > works fine (always evicted 10 entries)
> >
> > Could someone take a look and explain such behavior?
> >
> > --
> > Sergey Kozlov
> >
> >
>
>
> --
> Sergey Kozlov
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
ndler.java:524)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:87)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$6.apply(IgniteTxHandler.java:144)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$6.apply(IgniteTxHandler.java:142)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> > > at
> > >
> > >
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> > > at
> > >
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> > > at java.lang.Thread.run(Thread.java:745)
> > >
> > > -Val
> > >
> >
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
x27;s config via JDBC somehow?
> Or
> this is just a simple error in the doc, which needs to be fixed?
>
> Would appreciate the insight from the team. Thanks!
> Cos
>
> [1]
> https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
>
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
onfiguration under
> /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a bit dense,
> or
> the doc isn't written to a layman
>
> Thanks in advance!
> Cos
>
> On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > Cos,
> >
> > JDBC driver w
Done. I hope that is more clear now.
On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan
wrote:
> On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura wrote:
>
> > Cos,
> >
> > sepcifies configuration file for Ignite client node that
> will
> > be started during conne
Configuration sample added.
On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan
wrote:
> Thanks Andrey!
>
> In my view, we should also provide a sample XML configuration file,
> especially given that we refer to it in the sample URL.
>
> D.
>
> On Tue, Dec 8, 2015 at 10:1
?
>
> D.
>
> On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura wrote:
>
> > Configuration sample added.
> >
> > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Thanks Andrey!
> > >
>
fy it
> > > > either.
> > > > >
> > > > > It seems that the only properly required is clientMode=true, no?
> > > >
> > > > If this is the case, then _no_ config is really needed, perhaps?
> > > >
> > >
> >
al=?").setArgs(val));
Iterator> iter = qry.iterator();
// empty iterator
Is it known issue or I should create a ticket?
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Mon, Jan 11, 2016 at 11:57 AM, Yakov Zhdanov wrote:
> Andrey Gura, can you please clarify?
>
> --Yakov
>
> 2016-01-06 22:06 GMT+03:00 Konstantin Boudnik :
>
> > On Tue, Jan 05, 2016 at 10:40PM, Dmitriy Setrakyan wrote:
> > > On Tue, Jan 5, 2016 at 8:12
PM, Dmitriy Setrakyan
wrote:
> Andrey,
>
> Any chance we could upgrade Zeppelin to work with Ignite 1.5?
>
> D.
>
> On Mon, Jan 11, 2016 at 7:44 AM, Andrey Gura wrote:
>
> > Cos,
> >
> > the problem is that default config
> > (incubator-zeppelin/i
I'll just create new ticket and provide PR.
On Mon, Jan 11, 2016 at 9:11 PM, Dmitriy Setrakyan
wrote:
> Andrey, I think Cos won’t mind if you will provide a new PR.
>
> On Mon, Jan 11, 2016 at 10:08 AM, Andrey Gura wrote:
>
> > Dmitry,
> >
> > If I understan
Cos,
you have two options in order to create different notebooks for separate
caches:
1. You can create separate interpreter with cpecific configuration for each
notebook. Then you can bind interpreters to notebooks. You can also bind
many interpreters to oone notebook and use different interpret
hich will be used for node affinity
> > calculation.*
> > * */*
> > *public String getAffinityKeyField();*
> > *}*
> >
>
> It looks like we are over architecting here.
>
> Keys should not have many fields, and most likely will have one or two.
> Iterating through fields and generating hash-code or equals the standard
> way seems reasonable (as opposed to creating a whole architecture around
> how to get hash and equals fields).
>
> If it makes sense, we should cache the hash code value inside the key
> object after it has been generated once.
>
>
> >
> >
> > I need your feedback on these questions:
> > - is it ok to implement 'javax.json' API to support json for Ignite
> caches?
> >
>
> Can we get some existing implementation instead?
>
>
> > - if we implement 'javax.json' what is best way to add it in Ignite (see
> my
> > suggestion above: just add dependency for 'javax.json' API in 'core'
> > module, add special module or plugin)
> >
>
> Optional module?
>
>
> > - do we need to adde JsonConfiguration I described above?
> >
>
> Most likely not
>
>
> >
> > Thanks!
> >
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
> 3. Query data using JDBC driver - example code and, if needed,
> configuration to support it.
>
> Do you mind adding it?
>
> D.
>
> On Thu, Dec 10, 2015 at 7:50 AM, Andrey Gura wrote:
>
> > I didn't think that we should force client mode at moment of
> > im
Dima,
because notebook doesn't have any settings for it.
On Thu, Jan 14, 2016 at 11:30 PM, Dmitriy Setrakyan
wrote:
> Andrey, I am still a bit unclear. Why not have ability to specify a default
> cache per notebook, not per-interpreter?
>
> On Thu, Jan 14, 2016 at 8:42 AM, A
with what you call cross-cache queries?
>
> Cos
>
> On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote:
> > Cos,
> >
> > you have two options in order to create different notebooks for separate
> > caches:
> >
> > 1. You can create separate interpreter w
econd option sounds good, yet the interpreter still needs to have
> a
> > > particular cache name in the configuration, which now looks weird
> because
> > > I am
> > > working with multiple caches at once.
> > >
> > > It is possible to avoid spec
ppen to make it work?
>
> D.
>
> On Tue, Jan 19, 2016 at 11:22 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Andrey,
> >
> > My answers are inline...
> >
> > On Tue, Jan 19, 2016 at 4:14 AM, Andrey Gura wrote:
> >
mir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
CAL;
- warning about ignoring affinity function parameter should be moved from
validate() method to intialize() method.
I hope this will help you.
On Mon, Feb 1, 2016 at 12:12 PM, Ken Cheng wrote:
> Hi Andrey Gura,
>
> I am very new to Ignite, I am going to pick up
> https://issues.
ten!
>
> I am not working on this ticket and most probably will not have time to
> start in nearest future.
>
> I am CCing project's dev list. Andrey Gura, can you please respond -
> whether this issue is fixed or not with
> https://issues.apache.org/jira/browse/IGNITE-2080 fix?
Thorsten,
good news! I'll close IGNITE-1497 ticket.
Thanks a lot!
-- Forwarded message --
From: Thorsten Raff
Date: Wed, Feb 3, 2016 at 8:20 PM
Subject: Re: Ticket IGNITE-1497
To: Andrey Gura
Hi Andrey,
I have built ignite from source and connected one Raspberry Pi nod
gt; >
> > > The only option I see now is to create a separate query type,
> copy-paste
> > > everything from ScanQuery and add *mandatory* transformer. Something
> like
> > > this:
> > >
> > > ScanTransformQuery extends Query {
> > >
ers
> will work for example with SQL, but this API makes you think that
> transformers are supported for all the query types.
>
> Sergi
>
> 2016-02-04 16:46 GMT+03:00 Andrey Gura :
>
> > Val,
> >
> > can we introduce new method into IgnteCache API?
>
this
> work with SqlFieldsQuery? What you are going to transform remotely here? I
> believe all the transformations must happen at SQL level here.
>
> Sergi
>
>
>
> 2016-02-04 20:10 GMT+03:00 Andrey Gura :
>
> > SqlQuery, TextQuery and SpiQuery are similar to ScanQ
et [1]. Please provide any additional
> comments there.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-2546
>
> -Val
>
> On Thu, Feb 4, 2016 at 10:08 AM, Andrey Gura wrote:
>
> > Sergi,
> >
> >
> > > What you are going to transform remotely here?
&g
e() method and solve should caller thread execute
task or not.
Maybe I missed something and there is better way to solve this problem.
I will be grateful for any advice or idea.
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
> Andrey,
>
> I think we should keep it simple. From the API standpoint, I am not sure
> why not just always execute the task asynchronously every time when
> withAsync() API is invoked? Why add additional parameters to the API?
>
> D.
>
> On Wed, Feb 10, 2016
all the thoughts expressed in this thread into
> a
> > ticket?
> >
> > D.
> >
> > On Thu, Feb 4, 2016 at 4:14 PM, Andrey Gura wrote:
> >
> > > Val,
> > >
> > > From my point of view, special query class that allows transforming i
I've created ticket https://issues.apache.org/jira/browse/IGNITE-2646
On Thu, Feb 11, 2016 at 4:12 PM, Andrey Gura wrote:
> Dmitry,
>
> GridTaskProcessor does't know what kind of IgniteCompute implementation
> was used by client code. So we need some kind of
.
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Hi, Igniters!
Please take a look at the first phase of proposal for Apache ignite 3
Compute API: Simple remote job execution [1].
While most issues are already resolved due to simplicity of the proposal
any feedback and ideas will be really useful for the next phases.
Thanks!
[1]
https://cwiki.
n?
>
> Are other APIs like apply, async methods, map-reduce being considered in
> later phases?
>
> > On 15 May 2023, at 12:52, Andrey Gura wrote:
> >
> > Hi, Igniters!
> >
> > Please take a look at the first phase of proposal for Apache ignite 3
> &g
equivalent as it doesn’t take into account the possibility of
> partitions migrating during calculations.
>
> > On 15 May 2023, at 14:30, Andrey Gura wrote:
> >
> >> In Ignite 2, for bulk operations there’s an affinityRun method that takes
> >> a partition as a pa
Hi, Igniters!
Please take a look at the proposal for Code Deployment functionality
in Apache Ignite 3 [1].
Thanks for any feedback!
1. https://cwiki.apache.org/confluence/display/IGNITE/IEP-103%3A+Code+Deployment
Please, run benchmarks after fixing the problem. E.g. replacing HashMap to
ConcurrentHashMap can significantly affect performance.
See for example comments to IGNITE-2968 issue (
https://issues.apache.org/jira/browse/IGNITE-2968?focusedCommentId=15415170&page=com.atlassian.jira.plugin.system.issue
> node unit list [nodeId [--version version]] [--status ...] - same filters,
> but will show the node unit statuses rather than cluster statuses.
>
> WDYT?
>
> Thanks,
> Vadim
>
> On Tue, May 23, 2023 at 8:19 PM Andrey Gura wrote:
>
> > Hi, Igniters!
> >
> &g
odeId` parameter is not required for the `cluster unit list` because
> we will list only cluster statuses.
> Likewise, the `node unit list` command will list only node statuses so the
> `nodeId` is redundant because it will be called on the particular node
> endpoint.
>
> On Thu
der.
1.
https://cwiki.apache.org/confluence/display/IGNITE/IEP-103:+Code+Deployment#IEP103:CodeDeployment-Unitdeploymentprocess
On Tue, May 23, 2023 at 8:19 PM Andrey Gura wrote:
>
> Hi, Igniters!
>
> Please take a look at the proposal for Code Deployment functionality
> in Apache Ignite 3 [1
uring code
execution.
Corresponding changes have been made to the IEP.
1.
https://cwiki.apache.org/confluence/display/IGNITE/IEP-103%3A+Code+Deployment#IEP103:CodeDeployment-Dependencyresolvingandclassloading
On Tue, May 23, 2023 at 8:19 PM Andrey Gura wrote:
>
> Hi, Igniters!
>
> Please
Hi, Roman.
Thanks for IEP. Could you please also add tickets to the corresponding
section (see otghert IEP's for example).
On Mon, Jul 24, 2023 at 9:28 AM Roman Puchkovskiy
wrote:
>
> Hi Igniters!
>
> Please take a look at a proposal about the application of the Schema
> Synchronization framewor
Looks good to me. No objections at all.
Thanks a lot, Pavel!
On Fri, Aug 18, 2023 at 2:30 PM Pavel Tupitsyn wrote:
>
> Igniters,
>
> I've added another Dockerfile for ARM64 (to support native execution on
> Apple Silicon, AWS Graviton, etc).
>
> This will require another command in section 6.3.9
Igniters,
please, take a look at IEP-116: Metrics [1] which is a proposal for
Apache Ignite 3.
While we already implement metrics in the proposed way any comments
are still welcome.
1. https://cwiki.apache.org/confluence/display/IGNITE/IEP-116%3A+Metrics
Igniters,
please, take a look at IEP-117: Pluggable Storages Support [1] which
is a proposal for
Apache Ignite 3.
The main idea is to have the possibility to support various storages
for different tables in order to provide the best suitable storage
engine for a user's data.
1.
https://cwiki.ap
Hi, Anton
As I can see you already have contributor permissions. Do you
experience any access problems?
On Mon, Mar 18, 2024 at 7:45 PM Anton Potemkin
wrote:
>
> Hello, Everyone!
>
> My name is Anton. I have experience using Ignite as a client. We are
> building a distribution system at work, of
+1 (binding)
On Fri, Jan 31, 2025 at 1:02 PM Вячеслав Коптилин
wrote:
>
> +1 (binding)
>
> Thanks,
> S.
>
> пт, 31 янв. 2025 г. в 11:27, Aleksandr Polovtsev :
>
> > +1
> > Thank you, Pavel, for the great work of managing the release!
> >
> > On Thu, Jan 30, 2025 at 9:27 PM Pavel Tupitsyn
> > wro
Andrey Gura created IGNITE-11129:
Summary: Incorrect size calculation for SWITCH_SEGMENT_RECORD for
TDE
Key: IGNITE-11129
URL: https://issues.apache.org/jira/browse/IGNITE-11129
Project: Ignite
Andrey Gura created IGNITE-12028:
Summary: [IEP-35] HitRateMetric should provide rateTimeInterval
value to metrics exporter
Key: IGNITE-12028
URL: https://issues.apache.org/jira/browse/IGNITE-12028
Andrey Gura created IGNITE-12029:
Summary: [IEP-35] HistogramMetric should privde bounds' values to
metrics exporter
Key: IGNITE-12029
URL: https://issues.apache.org/jira/browse/IGNITE-12029
Pr
Andrey Gura created IGNITE-12044:
Summary: [IEP-35] JmxExporterSpi displays histogram values
incorrectly
Key: IGNITE-12044
URL: https://issues.apache.org/jira/browse/IGNITE-12044
Project: Ignite
Andrey Gura created IGNITE-12045:
Summary: [IEP-35] JmxExporterSpi has too broad name.
Key: IGNITE-12045
URL: https://issues.apache.org/jira/browse/IGNITE-12045
Project: Ignite
Issue Type
Andrey Gura created IGNITE-12046:
Summary: [IEP-35] LongMetric interface contains redundant methods.
Key: IGNITE-12046
URL: https://issues.apache.org/jira/browse/IGNITE-12046
Project: Ignite
Andrey Gura created IGNITE-12130:
Summary: Incorrect packages structure for OpenCensus metric
exporter and tracing SPIs
Key: IGNITE-12130
URL: https://issues.apache.org/jira/browse/IGNITE-12130
Andrey Gura created IGNITE-12131:
Summary: MMAP mode should be disabled by default for WAL manager
Key: IGNITE-12131
URL: https://issues.apache.org/jira/browse/IGNITE-12131
Project: Ignite
Andrey Gura created IGNITE-12172:
Summary: [IEP-35] OpenCensusMetricExporterSpiTest isn't added to
any test suite
Key: IGNITE-12172
URL: https://issues.apache.org/jira/browse/IGNITE-12172
Pr
Andrey Gura created IGNITE-12197:
Summary: Incorrect way for getting value of persistent enabled in
CacheGroupMetricsImpl
Key: IGNITE-12197
URL: https://issues.apache.org/jira/browse/IGNITE-12197
Andrey Gura created IGNITE-12199:
Summary: WAL record with data entries doesn't flushes on backups
for transactional cache
Key: IGNITE-12199
URL: https://issues.apache.org/jira/browse/IGNITE-
Andrey Gura created IGNITE-12231:
Summary: RollbackRecord's must be flushed after logging to WAL
Key: IGNITE-12231
URL: https://issues.apache.org/jira/browse/IGNITE-12231
Project: I
Andrey Gura created IGNITE-4797:
---
Summary: Need to expose offheap memory allocated size metric for
internal data structures
Key: IGNITE-4797
URL: https://issues.apache.org/jira/browse/IGNITE-4797
Andrey Gura created IGNITE-5041:
---
Summary: NPE during deadlock detection because cache isn't started
on node
Key: IGNITE-5041
URL: https://issues.apache.org/jira/browse/IGNITE-5041
Project: I
Andrey Gura created IGNITE-5203:
---
Summary: JDBC driver should support BLOB fields
Key: IGNITE-5203
URL: https://issues.apache.org/jira/browse/IGNITE-5203
Project: Ignite
Issue Type: Bug
Andrey Gura created IGNITE-5283:
---
Summary: Transaction recovery works incorrectly with cache store
and writeThrough enabled
Key: IGNITE-5283
URL: https://issues.apache.org/jira/browse/IGNITE-5283
Andrey Gura created IGNITE-5361:
---
Summary: Query for string field represented as CHAR SQL type in
underlying database doesn't retrieve entires that were loaded with
CacheJdbcPojoStore
Key: IGNITE-5361
URL:
Andrey Gura created IGNITE-5505:
---
Summary: @AffinityKeyMapped annotation is ignored if class names
are configured on BinaryConfiguration
Key: IGNITE-5505
URL: https://issues.apache.org/jira/browse/IGNITE-5505
Andrey Gura created IGNITE-5574:
---
Summary: Try to get rid of blocking synchronization on cache entry
for cache.localPeek operation
Key: IGNITE-5574
URL: https://issues.apache.org/jira/browse/IGNITE-5574
Andrey Gura created IGNITE-9903:
---
Summary: Copy only actual amount of data during archiving of WAL
segment
Key: IGNITE-9903
URL: https://issues.apache.org/jira/browse/IGNITE-9903
Project: Ignite
Andrey Gura created IGNITE-10352:
Summary: Cache get request can be mapped to node while partition
in MOVING state
Key: IGNITE-10352
URL: https://issues.apache.org/jira/browse/IGNITE-10352
Project
Andrey Gura created IGNITE-10412:
Summary: Transaction tries prepare after commit
Key: IGNITE-10412
URL: https://issues.apache.org/jira/browse/IGNITE-10412
Project: Ignite
Issue Type
Andrey Gura created IGNITE-10760:
Summary: Confusing message about system worker blocking
Key: IGNITE-10760
URL: https://issues.apache.org/jira/browse/IGNITE-10760
Project: Ignite
Issue
Andrey Gura created IGNITE-5685:
---
Summary: JDBC: Prepared statement shouldn't clear params after
query execution
Key: IGNITE-5685
URL: https://issues.apache.org/jira/browse/IGNITE-5685
Project: I
Andrey Gura created IGNITE-5722:
---
Summary: Cache entries stay in onheap after scan query execution
for OFFHEAP_TIRED cache with expiry policy
Key: IGNITE-5722
URL: https://issues.apache.org/jira/browse/IGNITE-5722
Andrey Gura created IGNITE-6290:
---
Summary: Data loss in case of manual rebalance
Key: IGNITE-6290
URL: https://issues.apache.org/jira/browse/IGNITE-6290
Project: Ignite
Issue Type: Bug
Andrey Gura created IGNITE-6339:
---
Summary: WAL: Avoid closed by interruption exception when user
thread is interrupted
Key: IGNITE-6339
URL: https://issues.apache.org/jira/browse/IGNITE-6339
Project
Andrey Gura created IGNITE-6341:
---
Summary: WAL: Use direct IO or libaio for writer thread
Key: IGNITE-6341
URL: https://issues.apache.org/jira/browse/IGNITE-6341
Project: Ignite
Issue Type
Andrey Gura created IGNITE-6429:
---
Summary: GridCachePreloadingEvictionsSelfTest.testEvictions test
fails periodically
Key: IGNITE-6429
URL: https://issues.apache.org/jira/browse/IGNITE-6429
Project
Andrey Gura created IGNITE-6430:
---
Summary:
CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails
periodically.
Key: IGNITE-6430
URL: https://issues.apache.org/jira/browse/IGNITE-6430
Andrey Gura created IGNITE-6443:
---
Summary: Test IgniteSourceConnectorTest has flaky fails
Key: IGNITE-6443
URL: https://issues.apache.org/jira/browse/IGNITE-6443
Project: Ignite
Issue Type
Andrey Gura created IGNITE-6470:
---
Summary: Wrong casting of long value to int leads to incorrect
results
Key: IGNITE-6470
URL: https://issues.apache.org/jira/browse/IGNITE-6470
Project: Ignite
Andrey Gura created IGNITE-6485:
---
Summary: Binary marshaller fails on deserialization of object with
writeReplace()
Key: IGNITE-6485
URL: https://issues.apache.org/jira/browse/IGNITE-6485
Project
Andrey Gura created IGNITE-2968:
---
Summary: Near cache support in transactions deadlock detection
Key: IGNITE-2968
URL: https://issues.apache.org/jira/browse/IGNITE-2968
Project: Ignite
Issue
Andrey Gura created IGNITE-2969:
---
Summary: Optimistic transactions support in deadlock detection
Key: IGNITE-2969
URL: https://issues.apache.org/jira/browse/IGNITE-2969
Project: Ignite
Issue
Andrey Gura created IGNITE-3136:
---
Summary: Cache initialization failed on client node in case of
dynamic cache start and not binary marshaller
Key: IGNITE-3136
URL: https://issues.apache.org/jira/browse/IGNITE-3136
401 - 500 of 564 matches
Mail list logo
