Pavel Tupitsyn created IGNITE-7109:
--
Summary: .NET: Thin client: Async cache operations
Key: IGNITE-7109
URL: https://issues.apache.org/jira/browse/IGNITE-7109
Project: Ignite
Issue Type
17 at 11:47 PM, Raymond Wilson
wrote:
> Hi Pavel,
>
>
>
> Is there a document that captures all the current gaps?
>
>
>
> Thanks,
>
> Raymond.
>
>
>
>
>
> *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
> *Sent:* Monday, December
Pavel Tupitsyn created IGNITE-7105:
--
Summary: .NET: IIgnite.ReentrantLock
Key: IGNITE-7105
URL: https://issues.apache.org/jira/browse/IGNITE-7105
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7104:
--
Summary: .NET: IIgnite.AtomicStamped
Key: IGNITE-7104
URL: https://issues.apache.org/jira/browse/IGNITE-7104
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7103:
--
Summary: .NET: IIgnite.Semaphore
Key: IGNITE-7103
URL: https://issues.apache.org/jira/browse/IGNITE-7103
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7102:
--
Summary: .NET: IIgnite.AddCacheConfiguration
Key: IGNITE-7102
URL: https://issues.apache.org/jira/browse/IGNITE-7102
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-7101:
--
Summary: .NET: IIgnite.GetVersion
Key: IGNITE-7101
URL: https://issues.apache.org/jira/browse/IGNITE-7101
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7100:
--
Summary: .NET: IIgnite CreateCaches, DestroyCaches
Key: IGNITE-7100
URL: https://issues.apache.org/jira/browse/IGNITE-7100
Project: Ignite
Issue Type
Hi Raymond,
There is no exact schedule, but we always strive to keep .NET API up to
speed with Java.
Usually new features are added right in the same release (persistence in
2.1, for example).
Pavel
On Sat, Dec 2, 2017 at 9:51 AM, Raymond Wilson
wrote:
> Hi Alexey,
>
>
>
> I think I need to be
Hi Andrey,
Compute and other APIs are certainly planned, cache is just a start.
We intentionally limit the scope to actually release something in 2.4 and
not delay it further.
Adding operations to existing protocol is relatively easy.
Current focus is to make sure that the protocol itself is soli
Pavel Tupitsyn created IGNITE-7089:
--
Summary: .NET: Thin client: LINQPad example
Key: IGNITE-7089
URL: https://issues.apache.org/jira/browse/IGNITE-7089
Project: Ignite
Issue Type
should have no
> exceptions for message formats.
>
> Thank you,
> Alexey
>
> From: Pavel Tupitsyn
> Sent: Thursday, November 30, 2017 12:11 PM
> To: dev@ignite.apache.org
> Subject: Re: Thin Client Protocol documentation
>
> Hi Alexey,
>
> 1,2,3 are related
Pavel Tupitsyn created IGNITE-7082:
--
Summary: .NET: Cross-platform standalone executable
Key: IGNITE-7082
URL: https://issues.apache.org/jira/browse/IGNITE-7082
Project: Ignite
Issue Type
hers don't? Let's
> simplify parser work )
>
> 4. The same comments for success flag (1 byte) and status code (4 bytes)
> in responses. Let's leave only status code.
>
> Thank you,
> Alexey
>
> From: Pavel Tupitsyn
> Sent: Wednesday, November 22, 2017 4:04
When I try to fail the handshake, I get 32 as the message
> length. Is this expected?
>
> -Prachi
>
> On Wed, Nov 29, 2017 at 8:20 AM, Pavel Tupitsyn
> wrote:
>
>> Hi Prachi,
>>
>> Flags parameter in all cache operations is reserved for things like
>
t; In the operation request, what does the 'flags' parameter mean?
>
>
> Thanks,
> -Prachi
>
> On Wed, Nov 29, 2017 at 5:27 AM, Pavel Tupitsyn
> wrote:
>
>> Sergey, good point, done.
>>
>> On Wed, Nov 29, 2017 at 2:30 PM, Sergey Kozlov
>> wr
Pavel Tupitsyn created IGNITE-7072:
--
Summary: IgniteCache.replace(k, v, nv) does not work in binary
mode without classes
Key: IGNITE-7072
URL: https://issues.apache.org/jira/browse/IGNITE-7072
e:
>
> > 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
>
tionaries without changes in type code
> table!
> Of course for the appoach above we get significat overhead for key
> storing. But I think it is acceptable for some cases and definitely ok for
> Python
>
>
>
>
> On Wed, Nov 22, 2017 at 9:14 PM, Prachi Garg wrote:
>
&g
Pavel Tupitsyn created IGNITE-7013:
--
Summary: .NET: Ignite does not start on macOS
Key: IGNITE-7013
URL: https://issues.apache.org/jira/browse/IGNITE-7013
Project: Ignite
Issue Type: Bug
Pavel Tupitsyn created IGNITE-7002:
--
Summary: .NET: Add cross-platform examples on .NET Core
Key: IGNITE-7002
URL: https://issues.apache.org/jira/browse/IGNITE-7002
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-7000:
--
Summary: .NET: Document .NET Core support and running on Linux
Key: IGNITE-7000
URL: https://issues.apache.org/jira/browse/IGNITE-7000
Project: Ignite
Pavel Tupitsyn created IGNITE-6997:
--
Summary: .NET: Thin client: Move ClientStatus to public API
Key: IGNITE-6997
URL: https://issues.apache.org/jira/browse/IGNITE-6997
Project: Ignite
Igniters,
I've put together a detailed description of our Thin Client protocol
in form of IEP on wiki:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol
To clarify:
- Protocol implementation is in master (see ClientMessageParser class)
- Protocol has not been released
Pavel Tupitsyn created IGNITE-6990:
--
Summary: .NET: Thin client: Remove OP_SQL_QUERY
Key: IGNITE-6990
URL: https://issues.apache.org/jira/browse/IGNITE-6990
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6989:
--
Summary: .NET: Thin client: Group operation codes by purpose
Key: IGNITE-6989
URL: https://issues.apache.org/jira/browse/IGNITE-6989
Project: Ignite
Pavel Tupitsyn created IGNITE-6988:
--
Summary: .NET: Thin client: OP_DESTROY_CACHE should take cacheId
instead of name
Key: IGNITE-6988
URL: https://issues.apache.org/jira/browse/IGNITE-6988
Project
Pavel Tupitsyn created IGNITE-6986:
--
Summary: .NET: Some exceptions can't be serialized
Key: IGNITE-6986
URL: https://issues.apache.org/jira/browse/IGNITE-6986
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6982:
--
Summary: .NET: Migrate to latest NUnit
Key: IGNITE-6982
URL: https://issues.apache.org/jira/browse/IGNITE-6982
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6975:
--
Summary: .NET: Create cross-platform examples on .NET Core
Key: IGNITE-6975
URL: https://issues.apache.org/jira/browse/IGNITE-6975
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6951:
--
Summary: .NET: BinaryWriter should throw exception on pointer
fields
Key: IGNITE-6951
URL: https://issues.apache.org/jira/browse/IGNITE-6951
Project: Ignite
Pavel Tupitsyn created IGNITE-6912:
--
Summary: .NET: Thin client: Cache iterator
Key: IGNITE-6912
URL: https://issues.apache.org/jira/browse/IGNITE-6912
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6911:
--
Summary: .NET: Optionally disable Java console redirect
Key: IGNITE-6911
URL: https://issues.apache.org/jira/browse/IGNITE-6911
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6900:
--
Summary: .NET: QuerySqlEntity attribute
Key: IGNITE-6900
URL: https://issues.apache.org/jira/browse/IGNITE-6900
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6887:
--
Summary: .NET: Binary serialization performance: eliminate
delegate allocations
Key: IGNITE-6887
URL: https://issues.apache.org/jira/browse/IGNITE-6887
Project
Pavel Tupitsyn created IGNITE-6886:
--
Summary: .NET: Performance: Pre-calculate fieldId in reflective
serializer
Key: IGNITE-6886
URL: https://issues.apache.org/jira/browse/IGNITE-6886
Project
Pavel Tupitsyn created IGNITE-6885:
--
Summary: .NET: Binary serialization performance: eliminate virtual
calls on hot path
Key: IGNITE-6885
URL: https://issues.apache.org/jira/browse/IGNITE-6885
Pavel Tupitsyn created IGNITE-6834:
--
Summary: .NET: Distributed Set
Key: IGNITE-6834
URL: https://issues.apache.org/jira/browse/IGNITE-6834
Project: Ignite
Issue Type: New Feature
Sure, done.
On Thu, Nov 2, 2017 at 10:10 AM, Dmitry Pavlov
wrote:
> Hi Pavel, thank you. Could you please do the same for this modules?
> I can remove gitter but I am not sure about CI server links correctness.
>
> чт, 2 нояб. 2017 г. в 9:38, Pavel Tupitsyn :
>
> > Denis,
Denis, Dmitry,
Looks like you forgot
https://github.com/apache/ignite/tree/master/modules/platforms/dotnet
and
https://github.com/apache/ignite/tree/master/modules/platforms/cpp
Thanks,
Pavel
On Thu, Nov 2, 2017 at 9:16 AM, Dmitry Pavlov wrote:
> Denis, thank you for review and merge!
> Link w
> >
> > Yakov,
> >
> > > having docs under separate git repository
> > We should not use separate git repo, Apache Ignite repo should be used.
> > Documentation should be a part of pull request.
> >
> > On Wed, Nov 1, 2017 at 10:08 AM, Pavel Tupitsyn
Denis,
> Could you show me any example of such a documentation where docs are
stored in git and can be visualized by GitHub (dev stage) and 3rd party
engine (release on the site)?
1) Apache Spark
Source: https://github.com/apache/spark/tree/master/docs
Docs: https://spark.apache.org/documentation
-party site, so the docs won’t be hosted on ASF
> infrastructure anyway.
>
> As a the one who prepares docs frequently, I can live with readme.io <
> http://readme.io/>.
>
> —
> Denis
>
> > On Oct 31, 2017, at 2:35 AM, Pavel Tupitsyn
> wrote:
> >
> > Hi
+1 to this.
Should we go even further and change Ignite configuration defaults to vm ip
finder?
Starting a standalone node with default config never works for me,
multicast stuff hangs on my network for some reason.
Pavel
On Tue, Oct 31, 2017 at 12:00 PM, Evgeniy Ignatiev <
yevgeniy.ignat...@gma
Hi Denis,
Are there plans to move away from readme.io?
* It is not properly versioned, which is very painful
* Documentation should be in Apache git, not on some third party site
Thoughts?
On Mon, Oct 30, 2017 at 11:24 PM, Denis Magda wrote:
> Good point. Renamed:
> https://cwiki.apache.org/c
Pavel Tupitsyn created IGNITE-6791:
--
Summary: .NET: Thin client: batch SQL
Key: IGNITE-6791
URL: https://issues.apache.org/jira/browse/IGNITE-6791
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6790:
--
Summary: .NET: Thin client: Multiple SQL statements
Key: IGNITE-6790
URL: https://issues.apache.org/jira/browse/IGNITE-6790
Project: Ignite
Issue Type
+1 (binding)
Checked .NET:
* Build from source
* Build and run examples
* Binary distribution
* NuGet package
Release notes for .NET are not correct: local collection joins were added
in 2.1
I would include the following tickets instead:
https://issues.apache.org/jira/browse/IGNITE-5615
https://
Pavel Tupitsyn created IGNITE-6776:
--
Summary: .NET: Thin client: SQL query example
Key: IGNITE-6776
URL: https://issues.apache.org/jira/browse/IGNITE-6776
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6773:
--
Summary: SQL: Support TIMESTAMP_WITH_TIMEZONE data type
Key: IGNITE-6773
URL: https://issues.apache.org/jira/browse/IGNITE-6773
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6772:
--
Summary: SQL exception messages are not descriptive
Key: IGNITE-6772
URL: https://issues.apache.org/jira/browse/IGNITE-6772
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6770:
--
Summary: Service proxy call should not require service class on
the node
Key: IGNITE-6770
URL: https://issues.apache.org/jira/browse/IGNITE-6770
Project: Ignite
Pavel Tupitsyn created IGNITE-6768:
--
Summary: .NET: Thin client: Cache id is calculated incorrectly
Key: IGNITE-6768
URL: https://issues.apache.org/jira/browse/IGNITE-6768
Project: Ignite
Hi Nikita,
Sorry for the late reply.
See my comments in JIRA.
Thanks,
Pavel
On Fri, Oct 20, 2017 at 12:10 PM, Nikita Amelchev
wrote:
> Hello, Pavel, Igor, Igniters.
>
> I have implemented javax.sql.Date type for a binary protocol [1,2].
> According to TC tests [3] we need to add support for sq
hrough some API call or SQL
> > command, and then start loading.
> >
> > On Wed, Oct 25, 2017 at 2:41 PM, Pavel Tupitsyn
> > wrote:
> >
> > > IMO IgniteCache.disableWal() should be enough.
> > >
> > > Also what about an option to disable WAL
IMO IgniteCache.disableWal() should be enough.
Also what about an option to disable WAL when IgniteDataStreamer is active?
On Wed, Oct 25, 2017 at 2:38 PM, Vladimir Ozerov
wrote:
> One more idea - ability to create a cache with initially disabled WAL.
> Might be useful.
>
> On Wed, Oct 25, 2017
Pavel Tupitsyn created IGNITE-6715:
--
Summary: .NET:
DataStorageConfiguration.WalAutoArchiveAfterInactivity
Key: IGNITE-6715
URL: https://issues.apache.org/jira/browse/IGNITE-6715
Project: Ignite
Pavel Tupitsyn created IGNITE-6714:
--
Summary: .NET: IgniteConfiguration missing properties
Key: IGNITE-6714
URL: https://issues.apache.org/jira/browse/IGNITE-6714
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6707:
--
Summary: .NET: Machine learning APIs
Key: IGNITE-6707
URL: https://issues.apache.org/jira/browse/IGNITE-6707
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6705:
--
Summary: .NET: CacheConfiguration missing properties
Key: IGNITE-6705
URL: https://issues.apache.org/jira/browse/IGNITE-6705
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6704:
--
Summary: .NET: CacheConfiguration.KeyConfiguration
Key: IGNITE-6704
URL: https://issues.apache.org/jira/browse/IGNITE-6704
Project: Ignite
Issue Type
> that all the SQL related pages will be hidden
Denis, please make sure to update all references to these pages.
It should be obvious from Java/.NET/C++ docs that SQL features are present
and did not disappear from the docs.
Consider scenario:
As a user, I go to apacheignite-net.readme.io and sea
Pavel Tupitsyn created IGNITE-6681:
--
Summary: .NET: QueryMetrics
Key: IGNITE-6681
URL: https://issues.apache.org/jira/browse/IGNITE-6681
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6680:
--
Summary: .NET: QueryDetailMetrics
Key: IGNITE-6680
URL: https://issues.apache.org/jira/browse/IGNITE-6680
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6676:
--
Summary: .NET: Use FsCheck for tests
Key: IGNITE-6676
URL: https://issues.apache.org/jira/browse/IGNITE-6676
Project: Ignite
Issue Type: Improvement
Igniters, another thing to consider:
DataRegionConfiguration.SwapFilePath should be SwapPath,
since this is actually not a single file, but a directory path.
On Fri, Oct 13, 2017 at 7:53 PM, Denis Magda wrote:
> Seems I've got what you’re talking about.
>
> I’ve tried to change the root directo
Pavel Tupitsyn created IGNITE-6621:
--
Summary: .NET: Disable thin client for 2.3 release
Key: IGNITE-6621
URL: https://issues.apache.org/jira/browse/IGNITE-6621
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6619:
--
Summary: .NET: Ignite Demo Application
Key: IGNITE-6619
URL: https://issues.apache.org/jira/browse/IGNITE-6619
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-6615:
--
Summary: .NET: Thin client: XML configuration
Key: IGNITE-6615
URL: https://issues.apache.org/jira/browse/IGNITE-6615
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6614:
--
Summary: .NET: DotNetCore examples
Key: IGNITE-6614
URL: https://issues.apache.org/jira/browse/IGNITE-6614
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6613:
--
Summary: .NET: Thin client: Create dotnet core unit test project,
run on Linux
Key: IGNITE-6613
URL: https://issues.apache.org/jira/browse/IGNITE-6613
Project
Pavel Tupitsyn created IGNITE-6608:
--
Summary: .NET: Thin client documentation
Key: IGNITE-6608
URL: https://issues.apache.org/jira/browse/IGNITE-6608
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-6607:
--
Summary: Thin client: protocol documentation
Key: IGNITE-6607
URL: https://issues.apache.org/jira/browse/IGNITE-6607
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-6603:
--
Summary: .NET: EntityFramework Core Data Provider
Key: IGNITE-6603
URL: https://issues.apache.org/jira/browse/IGNITE-6603
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6602:
--
Summary: .NET: Improve LINQ documentation
Key: IGNITE-6602
URL: https://issues.apache.org/jira/browse/IGNITE-6602
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-6599:
--
Summary: .NET: IgniteConfiguration.ClusterName
Key: IGNITE-6599
URL: https://issues.apache.org/jira/browse/IGNITE-6599
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6598:
--
Summary: .NET: IIgnite.AddCacheConfiguration
Key: IGNITE-6598
URL: https://issues.apache.org/jira/browse/IGNITE-6598
Project: Ignite
Issue Type
Definitely useful, I've seen user requests about this a number of times.
On Wed, Oct 11, 2017 at 1:03 PM, Vladimir Ozerov
wrote:
> Alex,
>
> Agree. Looks like a useful feature, especially for testing purposes.
>
> On Wed, Oct 11, 2017 at 12:38 PM, Alexey Kuznetsov
> wrote:
>
> > Hi,
> >
> > I'd
Pavel Tupitsyn created IGNITE-6584:
--
Summary: .NET: Propagate new cache metrics
Key: IGNITE-6584
URL: https://issues.apache.org/jira/browse/IGNITE-6584
Project: Ignite
Issue Type
onfigurations
>
> Best Regards,
> Ivan Rakov
>
>
> On 09.10.2017 10:51, Pavel Tupitsyn wrote:
>
>> Sorry that I'm late to the party, but this looks inconsistent:
>>
>> DataStorageConfiguration defaultRegionConfiguration
>> DataRegionCon
Sorry that I'm late to the party, but this looks inconsistent:
DataStorageConfiguration defaultRegionConfiguration
DataRegionConfiguration[] getDataRegions
defaultRegionConfiguration + getRegionConfigurations
- or -
defaultDataRegion + getDataRegions
Thoughts?
On Mon, Oct 2, 2017 at 9:10 PM, Iv
Pavel Tupitsyn created IGNITE-6566:
--
Summary: .NET: IgniteConfiguration.ExecutorConfiguration
Key: IGNITE-6566
URL: https://issues.apache.org/jira/browse/IGNITE-6566
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6563:
--
Summary: .NET: ICache.GetLongSize
Key: IGNITE-6563
URL: https://issues.apache.org/jira/browse/IGNITE-6563
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6551:
--
Summary: .NET: NPE in PlatformDotNetCacheStore on Java-only nodes
Key: IGNITE-6551
URL: https://issues.apache.org/jira/browse/IGNITE-6551
Project: Ignite
Pavel Tupitsyn created IGNITE-6541:
--
Summary: .NET: Refactor DataStreamer configuration
Key: IGNITE-6541
URL: https://issues.apache.org/jira/browse/IGNITE-6541
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6534:
--
Summary: Configure NotNull fields with annotations
Key: IGNITE-6534
URL: https://issues.apache.org/jira/browse/IGNITE-6534
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6525:
--
Summary: .NET: BinaryObject.Deserialize to custom type
Key: IGNITE-6525
URL: https://issues.apache.org/jira/browse/IGNITE-6525
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-6524:
--
Summary: .NET: Explicit dynamic type registration
Key: IGNITE-6524
URL: https://issues.apache.org/jira/browse/IGNITE-6524
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6523:
--
Summary: .NET: QueryField.NotNull
Key: IGNITE-6523
URL: https://issues.apache.org/jira/browse/IGNITE-6523
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6517:
--
Summary: .NET: DataStreamer DefaultPerNodeBufferSize,
DefaultParallelOpsMultiplier
Key: IGNITE-6517
URL: https://issues.apache.org/jira/browse/IGNITE-6517
Pavel Tupitsyn created IGNITE-6516:
--
Summary: .NET: PersistentStoreConfiguration.WriteThrottlingEnabled
Key: IGNITE-6516
URL: https://issues.apache.org/jira/browse/IGNITE-6516
Project: Ignite
Pavel Tupitsyn created IGNITE-6515:
--
Summary: .NET: Enable persistence on per-cache basis
Key: IGNITE-6515
URL: https://issues.apache.org/jira/browse/IGNITE-6515
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6505:
--
Summary: .NET: Verify output in ExamplesTest
Key: IGNITE-6505
URL: https://issues.apache.org/jira/browse/IGNITE-6505
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-6494:
--
Summary: .NET: CacheConfiguration.WriteSynchronizationMode
incorrect default value
Key: IGNITE-6494
URL: https://issues.apache.org/jira/browse/IGNITE-6494
Pavel Tupitsyn created IGNITE-6492:
--
Summary: .NET: Tests: Task.Wait should always include a timeout
Key: IGNITE-6492
URL: https://issues.apache.org/jira/browse/IGNITE-6492
Project: Ignite
Hi,
For Ignite.NET I would like to include at least these two:
https://issues.apache.org/jira/browse/IGNITE-5615 .NET:
IgniteConfiguration.LocalEventListeners
https://issues.apache.org/jira/browse/IGNITE-4070 .NET: Introduce
transformers to SCAN queries
Also users are asking for .NET Core and L
We could even add a configuration switch to throw an exception in such case.
I guess that in majority of use cases there is a single type per cache,
and we should have a way to enforce that.
On Fri, Sep 22, 2017 at 7:47 PM, Mikhail Cherkasov
wrote:
> Hi all,
>
> I've seen several times that due
Pavel Tupitsyn created IGNITE-6486:
--
Summary: .NET: ActiveOnStart does not work
Key: IGNITE-6486
URL: https://issues.apache.org/jira/browse/IGNITE-6486
Project: Ignite
Issue Type: Bug
Pavel Tupitsyn created IGNITE-6471:
--
Summary: .NET: Flags should have plural names
Key: IGNITE-6471
URL: https://issues.apache.org/jira/browse/IGNITE-6471
Project: Ignite
Issue Type
Hi Sergey,
Done. Welcome to the Apache Ignite community!
Pavel
On Thu, Sep 21, 2017 at 5:19 PM, wrote:
> Hi Pavel!
>
> Could you please provide me a contributor permissions?
> My jira account is schernolyas
>
> A lot of thanks!
>
> _
> Sent from http://apach
1001 - 1100 of 1892 matches
Mail list logo
