Pavel Tupitsyn created IGNITE-12754:
---
Summary: .NET: Thin Client: Service invocation
Key: IGNITE-12754
URL: https://issues.apache.org/jira/browse/IGNITE-12754
Project: Ignite
Issue Type
Zinoviev , how about you preparing several
> paragraphs for the blog highlighting the biggest changes in ML? The same
> highlighted content will be elaborated during the webinar.
>
> -
> Denis
>
>
> On Wed, Mar 4, 2020 at 2:29 AM Pavel Tupitsyn
> wrote:
>
> > Denis, I h
/
>- Architecture:
>
> https://lightconsole.dev/2020/03/04/distributing-dmx-compute-with-apache-ignite/
>
> You might be interested to see how the system relies on various
> capabilities of Ignite to make the things working at scale - compute,
> storage, service grid, etc.
&g
0 at 22:10, Maxim Muzafarov
> wrote:
> > > >
> > > > Dear community,
> > > >
> > > >
> > > > The vote for a new release candidate is closed, now.
> > > > Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two
> votes
&
Denis, I have a few blog posts on Ignite.NET planned:
* What's new in Ignite.NET 2.8 (Thin Client Partition Awareness, logging,
expiry policy, cluster API, .NET Core 3.x, Dockerfile)
* Ignite.NET performance improvements on .NET Core 3.x
* Ignite.NET Partition Awareness performance
* Fixing JNI
Igniters,
The release has already happened.
It is on our website [1], it is on Maven [2].
People are using it, so I don't think we can do anything at this point.
Bugs happen, we can't delay the release forever because of them. Let's fix
things in 2.8.1.
[1]
+1 (binding)
Started .NET nodes and examples, installed NuGet packages and started
Ignite from there
On Sat, Feb 29, 2020 at 11:28 PM Ilya Kasnacheev
wrote:
> Hello!
>
> 0 (binding)
>
> I have checked deb package, built and run C++, ran dotnet example and
> sqlline.
>
> It is unfortunate that
TC [3] Build & Upload Nuget Staging Packages
> >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=5085460=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildResultsDiv
> >
> > TC [2] Compare w/ Previous Release
> >
> >
> https://ci.ignite.ap
в 15:04, Igor Sapego :
> >
> > By the way, some ODBC tests became flaky about the same time as well.
> > May it be there is one root cause somewhere in SQL?
> >
> > Best Regards,
> > Igor
> >
> >
> > On Mon, Feb 17, 2020 at 9:36 PM Pavel Tupitsyn
Pavel Tupitsyn created IGNITE-12720:
---
Summary: .NET: CachePeekMode is not treated as Flags
Key: IGNITE-12720
URL: https://issues.apache.org/jira/browse/IGNITE-12720
Project: Ignite
Issue
PM Pavel Tupitsyn wrote:
> I'm running a final check in branch ignite-2.8-dotnet-build-fix, should be
> done soon.
> After that I'll merge the changes into ignite-2.8 (and backport to
> master), and we can proceed.
>
> I had to fix both TC project and the build script.
te.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
>
> On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn wrote:
> >
> > Maxim, I did a quick fix for the script, but it did not work.
> > Investigating further, will get back to you later today.
> >
> >
Maxim, I did a quick fix for the script, but it did not work.
Investigating further, will get back to you later today.
On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov wrote:
> Pavel,
>
>
> Can you assist me with preparing NuGet staging according to the
> release steps [1]? I've double-checked
on other
cache operations.
[1] https://github.com/apache/ignite/pull/7468
On Sat, Feb 22, 2020 at 7:07 PM Pavel Tupitsyn wrote:
> Sergey,
>
> Sure, I'll add you as a reviewer.
> And a thorough review will be the best contribution. The feature is rather
> complex and in the works
application .Net code, I assume it's OK to consume some resources upon
> such invocation. We can't expect new features to consume zero resources.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 18 февр. 2020 г. в 20:46, Pavel Tupitsyn :
>
> > Ilya, looks like t
Pavel Tupitsyn created IGNITE-12699:
---
Summary: .NET: Remove TypeCaster
Key: IGNITE-12699
URL: https://issues.apache.org/jira/browse/IGNITE-12699
Project: Ignite
Issue Type: New Feature
egards,
> --
> Ilya Kasnacheev
>
>
> вт, 18 февр. 2020 г. в 17:31, Pavel Tupitsyn :
>
> > Ilya, as noted above:
> >
> > > There are 2 kinds of Near Caches:
> > > - On client nodes: created per-node by calling ignite.CreateNearCache
> &
s so they
> will start near caches all right.
>
> Don't we have near cache start-up on per-node basis for clients, anyway?
>
> I'm not convinced why we need this flag. I have to admit my understanding
> of near caches is limited.
>
> Regards,
> --
> Ilya Kasnacheev
>
&
native cache
>
> available for a platform or just ignore the configuration.
>
> вт, 18 февр. 2020 г. в 15:05, Pavel Tupitsyn :
>
> > Igor,
> >
> > The problem is - we need to pass this flag around the cluster for Server
> > Near Caches,
> > so
Sapego wrote:
> Do you suggest to introduce it in general configuration? Why not introduce
> it only on platform side? Is there any .NET-specific configuration?
>
> Best Regards,
> Igor
>
>
> On Tue, Feb 18, 2020 at 1:10 AM Pavel Tupitsyn
> wrote:
>
> > Ignite
Igniters,
I'm working on .NET Near Cache feature [1]
(storing deserialized cache entries in CLR memory to improve performance).
Implementation is based on Java near cache, with some callbacks to .NET
side
for updating and invalidating cached entries.
However, I'd like to make this feature
Pavel Tupitsyn created IGNITE-12691:
---
Summary: .NET: Native Near Cache
Key: IGNITE-12691
URL: https://issues.apache.org/jira/browse/IGNITE-12691
Project: Ignite
Issue Type: New Feature
I did a quick look some time ago, no idea what is going on, honestly. Tests
became flaky for no apparent reason.
I have this on my list, will investigate more.
On Mon, Feb 17, 2020 at 8:43 PM Ivan Pavlukhin wrote:
> Looks like something broke .NET NuGet tests [1] in the end of January.
> Is
Hello Guru,
I'll have a look today, thank you!
On Sat, Feb 15, 2020 at 11:33 PM Guru Stron
wrote:
> Hello, Igniters
>
> I've been out for some time and wanted to stretch a little bit my
> contributor muscles with some newbie tasks. There some changes both to Java
> and .NET, can somebody take
Pavel Tupitsyn created IGNITE-12676:
---
Summary: .NET: Add partition-based AffinityCall and AffinityRun
overloads
Key: IGNITE-12676
URL: https://issues.apache.org/jira/browse/IGNITE-12676
Project
Pavel Tupitsyn created IGNITE-12670:
---
Summary: .NET: Calculate IAffinity.GetPartition locally for
default affinity
Key: IGNITE-12670
URL: https://issues.apache.org/jira/browse/IGNITE-12670
Project
-1 Prohibit
On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky
wrote:
>
> -1, sounds confusing, i wan`t use deprecated API
> and @IgniteExperimental it`s something unknown with undefined «time for
> support».
>
>
>
> >Dear Apache Ignite community,
> >
> >We would like to conduct a formal vote
Pavel Tupitsyn created IGNITE-12634:
---
Summary: .NET: Publish symbol packages
Key: IGNITE-12634
URL: https://issues.apache.org/jira/browse/IGNITE-12634
Project: Ignite
Issue Type: Bug
Agree with Andrey, let's remove deprecation for now and unblock the release.
On Thu, Jan 30, 2020 at 10:23 PM Andrey Gura wrote:
> I'll just repeat one thought with some changes.
>
> There are at least two groups of people in this discussion. One group
> sure that new API is complete and
It's done, only Squash mode is enabled in GitHub UI.
On Mon, Jan 27, 2020 at 5:05 PM Pavel Tupitsyn wrote:
> INFRA ticket filed:
> https://issues.apache.org/jira/browse/INFRA-19778
>
> On Mon, Jan 27, 2020 at 4:38 PM Alexey Zinoviev
> wrote:
>
>> I used squash for las
Pavel Tupitsyn created IGNITE-12604:
---
Summary: .NET: DotNetCore publish dir is not copied to bin dir
Key: IGNITE-12604
URL: https://issues.apache.org/jira/browse/IGNITE-12604
Project: Ignite
doing it I can keep
> > my
> > > >> Git's local state unmodified.
> > > >>
> > > >> So I suggest using squash and merge.
> > > >>
> > > >> пн, 27 янв. 2020 г. в 14:59, Maxim Muzafarov :
> > > >>
> >
Merging from GitHub is very convenient indeed, much faster and safer than
anything else.
And yes, GitHub provides a way to disable Merge and Rebase, leaving only
Squash option:
https://help.github.com/en/github/administering-a-repository/configuring-commit-squashing-for-pull-requests
However, I
Igor, great idea, I think this should be our priority for all thin clients.
Alexei, protocol version bump can be still required for major changes (e.g.
if we want to change handshake format).
But for simpler things like new features that don't affect existing ones,
feature masks allow us to keep
> desc.write(obj, this); // compactFooter here
>
> }
>
> ```
>
> чт, 23 янв. 2020 г., 14:15 Pavel Tupitsyn :
>
> > > If we support only strings it will be necessary to encode binary values
> > to
> > > something like BASE64 which is not sounds good from us
n you double check ?
>
> If we support only strings it will be necessary to encode binary values to
> something like BASE64 which is not sounds good from usability side.
>
>
>
> чт, 23 янв. 2020 г. в 13:26, Nikita Amelchev :
>
> > +1 for the hardcoded String t
, for
> > > > example, have DBMS_APPLICATION_INFO package, PostgreeSQL have
> > > > application_name connection property and application information
> > > available
> > > > later in system views).
> > > >
> > > > About allowed data ty
make sure they are usable from anywhere.
On Wed, Jan 22, 2020 at 9:21 PM Pavel Tupitsyn wrote:
> The approach with UserAttributes map looks dirty to me and raises
> questions:
>
> - Why is UserAttributes property related to authentication?
> - UserAttributes name implies tha
es single authentication factor is not enough. Attributes proposed
> > allow to add extra factors flexibly.
> >
> > ср, 22 янв. 2020 г., 17:39 Pavel Tupitsyn :
> >
> > > Token can be sent instead of a password (like git works with GitHub
> > > tok
Good idea about pre-release build of ignite-2.8 branch.
However, I would not name it `rc`, since it is not really a release
candidate. Make it `pre0` or something like that.
For Ignite.NET I've uploaded pre-release NuGet packages built from current
ignite-2.8 branch:
17:16 Igor Sapego :
> >
> > > Hi Dmitrii,
> > >
> > > Can you please explain your use case?
> > > I'm not sure I'm getting what is the motivation of this change.
> > >
> > > Best Regards,
> > > Igor
> > >
> > &g
Hi Dmitrii,
Honestly, I could not grasp the problem, can you explain it in more detail?
What do we solve by adding a map with arbitrary stuff to the client
protocol handshake?
On Wed, Jan 22, 2020 at 5:02 PM Dmitrii Ryabov
wrote:
> Hello, Igniters!
>
> I want to add the possibility of sending
uot;execute task with specified node filter" -
> simple
> > > and efficient.
> > > It's not simple: every compute or service request should contain
> complex
> > > node filtering logic, which duplicates the same logic for cluster API.
> > > It's not efficient: for exa
Pavel Tupitsyn created IGNITE-12555:
---
Summary: .NET: Thin Client: deserializing DateTime fields causes
BinaryTypeGet request for every value
Key: IGNITE-12555
URL: https://issues.apache.org/jira/browse/IGNITE
> Main question is "how this may happen in case fix got the Visa [2] ?".
This can happen because of other changes in master.
"Visa" truly works only when master is in the same state during the merge
as it was during TC run.
On Mon, Jan 20, 2020 at 1:50 PM Anton Vinogradov wrote:
> It seems,
Agree with Alexey, there should be an obvious public API to retrieve metrics
On Thu, Jan 16, 2020 at 8:23 PM Alexey Goncharuk
wrote:
> That's an option, I agree. Yet for me, from the usability point of view, it
> would be quite strange - to get an instance of the monitoring interface, I
> would
Pavel Tupitsyn created IGNITE-12532:
---
Summary: .NET: Recognize fields with KeyAttribute and set
QueryEntity.KeyFieldName
Key: IGNITE-12532
URL: https://issues.apache.org/jira/browse/IGNITE-12532
t;
>
> On Mon, Dec 23, 2019 at 12:21 AM Pavel Tupitsyn
> wrote:
>
> > Since there are no objections, I'm doing the rename:
> > https://issues.apache.org/jira/browse/IGNITE-12458
> >
> > On Fri, Dec 20, 2019 at 1:12 PM Igor Sapego wrote:
> >
> >
Since there are no objections, I'm doing the rename:
https://issues.apache.org/jira/browse/IGNITE-12458
On Fri, Dec 20, 2019 at 1:12 PM Igor Sapego wrote:
> +1, sounds reasonable to me.
>
> Best Regards,
> Igor
>
>
> On Fri, Dec 20, 2019 at 10:25 AM Pavel Tupitsyn
>
Hi Denis,
I've reviewed the list of newbie tickets for .NET, added some more there.
Also I've updated the page a little bit:
- Changed the wording of the first paragraph: "you need to sign up" ->
"please sign up"
To be honest, the mood on this whole page feels a bit off to me.
I'm not a native
Pavel Tupitsyn created IGNITE-12481:
---
Summary: .NET: NuGet verification script does not handle
multi-digit version parts
Key: IGNITE-12481
URL: https://issues.apache.org/jira/browse/IGNITE-12481
+1, let's rename while we have a chance before 2.8 is released.
ed Coding Guidelines [1].
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines
>
> On Thu, 19 Dec 2019 at 18:59, Pavel Tupitsyn wrote:
> >
> > Igniters,
> >
> > Does this rule bring any
Igniters,
Does this rule bring any value whatsoever for us?
Let's just disable it.
On Thu, Dec 19, 2019 at 6:25 PM Maxim Muzafarov wrote:
> Hello, Andrey
>
> Is it better to upgrade the checkstyle plugin version?
> It seems the issue has been fixed since 8.21 version (currently we have
> 8.19)
Pavel Tupitsyn created IGNITE-12473:
---
Summary: .NET: ClientServerCompatibilityTest fails on some agents
because of Maven error
Key: IGNITE-12473
URL: https://issues.apache.org/jira/browse/IGNITE-12473
Pavel Tupitsyn created IGNITE-12471:
---
Summary: .NET Thin Client: WithExpiryPolicy crashes client
connection on old servers
Key: IGNITE-12471
URL: https://issues.apache.org/jira/browse/IGNITE-12471
Pavel Tupitsyn created IGNITE-12458:
---
Summary: Rename Affinity Awareness to Partition Awareness
Key: IGNITE-12458
URL: https://issues.apache.org/jira/browse/IGNITE-12458
Project: Ignite
Pavel Tupitsyn created IGNITE-12437:
---
Summary: .NET: Run tests on macOS TeamCity agent
Key: IGNITE-12437
URL: https://issues.apache.org/jira/browse/IGNITE-12437
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-12427:
---
Summary: .NET: Ignite does not start under Mono on Linux because
of UnmanagedThread
Key: IGNITE-12427
URL: https://issues.apache.org/jira/browse/IGNITE-12427
Pavel Tupitsyn created IGNITE-12417:
---
Summary: .NET: ASP.NET Core Identity Store
Key: IGNITE-12417
URL: https://issues.apache.org/jira/browse/IGNITE-12417
Project: Ignite
Issue Type: New
Pavel Tupitsyn created IGNITE-12415:
---
Summary: .NET: Thin client does not connect to old server nodes
Key: IGNITE-12415
URL: https://issues.apache.org/jira/browse/IGNITE-12415
Project: Ignite
Oh wow, the next thread actually discusses this very issue about
discontinuation:
http://apache-ignite-developers.2346864.n4.nabble.com/Text-queries-indexes-GridLuceneIndex-QueryTextFiled-td43335.html
But the question stands - add to Thin Clients or not?
On Tue, Dec 3, 2019 at 5:43 PM Pavel
Igniters,
I'd like to discuss adding full-text queries (TextQuery, our Lucene-based
engine) to the Thin Client protocol.
In my opinion, this is a good addition, and rather easy to implement.
However, I vaguely remember in-person discussions with some community
members along the lines of
"Ignite
Pavel Tupitsyn created IGNITE-12414:
---
Summary: .NET: Performance: review
CopyOnWriteConcurrentDictionary.GetOrAdd usage and locking
Key: IGNITE-12414
URL: https://issues.apache.org/jira/browse/IGNITE-12414
Pavel Tupitsyn created IGNITE-12413:
---
Summary: .NET: XMLDoc does not work when using Ignite NuGet from
.NET Core
Key: IGNITE-12413
URL: https://issues.apache.org/jira/browse/IGNITE-12413
Project
Pavel Tupitsyn created IGNITE-12405:
---
Summary: .NET: WithReadRepair does not work
Key: IGNITE-12405
URL: https://issues.apache.org/jira/browse/IGNITE-12405
Project: Ignite
Issue Type: Bug
Pavel Tupitsyn created IGNITE-12404:
---
Summary: .NET: Adopt nullable reference types
Key: IGNITE-12404
URL: https://issues.apache.org/jira/browse/IGNITE-12404
Project: Ignite
Issue Type
nd 2 requests to server to execute the
> task. First - to get nodes by the filter, second - to actually execute the
> task. It seems like overhead. The same will be for services. Cluster group
> remains the same if the topology hasn't changed. We can use this fact and
> bind "execute task&qu
ed the cluster.
>
> In case of thick client: All server nodes will be used, tasks will be load
> balanced.
> In case of thin client: Only one server node will be used, client will
> detect topology change after an hour.
>
>
> вт, 26 нояб. 2019 г. в 11:50, Pavel Tupitsyn :
>
y version" field to the
> OP_COMPUTE_EXECUTE_TASK request to solve this problem.
>
>
> пн, 25 нояб. 2019 г. в 22:42, Pavel Tupitsyn :
>
> > Alex,
> >
> > > we will mix entities from different layers (transport layer and request
> > body)
>
will be sent from server to client only with
> a response when the task will be completed. Are we accept that?
>
> пн, 25 нояб. 2019 г. в 19:07, Pavel Tupitsyn :
>
> > Alex,
> >
> > I have a simpler idea. We already do request id handling in the protocol,
> > so:
> > -
er: [{Code = 1, Value= [“DotNet”, “MyAttribute”}, {Code=2,
> Value=1}]
> >
> > Where “1” stands for Attribute filtering and “2” – serverNodesOnly flag.
> >
> >
> >
> > As a result of request processing, a server sends nodeId UUIDs and a
> > current topVer.
Pavel Tupitsyn created IGNITE-12390:
---
Summary: .NET: Add automatic NuGet verification as part of the
release process
Key: IGNITE-12390
URL: https://issues.apache.org/jira/browse/IGNITE-12390
curityProcessor [2].
> >
> >
> >
> >1.
> >
> org.apache.ignite.internal.processors.security.client.ThinClientPermissionCheckTest
> >2.
> org.apache.ignite.internal.processors.security.GridSecurityProcessor
> >
> >
> > чт, 21 нояб. 2019 г. в 12:41, Pavel
Pavel Tupitsyn created IGNITE-12387:
---
Summary: .NET Thin Client: Handle unsupported features on older
server nodes gracefully
Key: IGNITE-12387
URL: https://issues.apache.org/jira/browse/IGNITE-12387
>
> > > But, compute support for a thin client requires some additional efforts
> > to
> > > get an appropriate SecurityContext on a remote node.
> > >
> > > The list of tasks allowed for subjects, including thin clients, is the
> > area
> > > of responsibility of GridSecurityProcessor
Good points, Sergey.
Maybe you are right, and Java-based compute without peer deployment is a
good first step for thin clients.
On Thu, Nov 21, 2019 at 12:32 PM Sergey Kozlov wrote:
> Hi Pavel
>
> On Thu, Nov 21, 2019 at 11:30 AM Pavel Tupitsyn
> wrote:
>
> > 1. I
1. I believe that Cluster operations for Thin Client protocol are already
in the works
by Alexandr Shapkin. Can't find the ticket though.
Alexandr, can you please confirm and attach the ticket number?
2. Proposed changes will work only for Java tasks that are already deployed
on server nodes.
Pavel Tupitsyn created IGNITE-12379:
---
Summary: .NET: Separate NuGet package for Thin Client
Key: IGNITE-12379
URL: https://issues.apache.org/jira/browse/IGNITE-12379
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-12378:
---
Summary: .NET: Fix NuGet package warnings
Key: IGNITE-12378
URL: https://issues.apache.org/jira/browse/IGNITE-12378
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-12377:
---
Summary: .NET: Add IBinaryObjectBuilder.SetField(name, val, type)
overload
Key: IGNITE-12377
URL: https://issues.apache.org/jira/browse/IGNITE-12377
Project
Pavel Tupitsyn created IGNITE-12368:
---
Summary: .NET: Make sure units are specified in documentation
where applicable
Key: IGNITE-12368
URL: https://issues.apache.org/jira/browse/IGNITE-12368
Replied in JIRA
Thanks
On Sat, Nov 9, 2019 at 3:13 AM Saikat Maitra
wrote:
> Pavel Tupitsyn, Igor Sapego
>
> I wanted to connect and confirm on changes for this PR.
>
> https://github.com/apache/ignite/pull/6490
>
> Do you think keeping the change for PlatformCo
Pavel Tupitsyn created IGNITE-12348:
---
Summary: .NET: Query cursors are not thread-safe
Key: IGNITE-12348
URL: https://issues.apache.org/jira/browse/IGNITE-12348
Project: Ignite
Issue Type
+1 for Dmitry Pavlov
On Tue, Oct 29, 2019 at 8:07 PM Ivan Rakov wrote:
> +1 for Dmitry Pavlov
>
> Best Regards,
> Ivan Rakov
>
> On 29.10.2019 10:50, Ilya Kasnacheev wrote:
> > +1 for Nikolay Izhikov (binding)
> >
> > Regards,
>
ng API in consistence with the thick client method and
> cacheConfiguration settings.
>
>
> From: Pavel Tupitsyn
> Sent: Saturday, October 19, 2019 9:20 PM
> To: dev
> Subject: Re: Thin clients: WithExpiryPolicy
>
> Alexandr,
>
> Sounds good to me.
>
> R
Pavel Tupitsyn created IGNITE-12306:
---
Summary: .NET: Java version is not taken into account when
detecting JAVA_HOME
Key: IGNITE-12306
URL: https://issues.apache.org/jira/browse/IGNITE-12306
> client with enabled KeepBinary mode.
>
> I think we could use the flags byte and write an expiration policy flag
> when required.
> Whenever the server sees that there is a request with expiration flag, we
> deserialize a policy and apply it to the request.
>
> From: Pavel T
Stateless approach looks a lot better to me.
We have a choice:
* Keep expiry policy on server and send an ID with every request (like a
query cursor ID - 8 bytes)
* Send full expiry policy with every expiry-enabled request (24 bytes - or
maybe less? We should think about the format)
Stateful
Ivan, great job, thanks for putting this together.
I think we also need a more formal description of the format, including
binary metadata exchange mechanics.
It was done (partially) for IEP-9 Thin Client Protocol, we should probably
copy from there:
the patch. Can anyone review the change?
>
>
> 1: https://issues.apache.org/jira/browse/IGNITE-11898
>
>
>
> ср, 13 мар. 2019 г. в 22:54, Pavel Tupitsyn :
>
> > Default value for boolean is false, and I though we'll have the feature
> > enabled by default.
Pavel Tupitsyn created IGNITE-12294:
---
Summary: .NET Inspections failure on TC
Key: IGNITE-12294
URL: https://issues.apache.org/jira/browse/IGNITE-12294
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-12258:
---
Summary: .NET: Add ContinuousQueryWithTransformer
Key: IGNITE-12258
URL: https://issues.apache.org/jira/browse/IGNITE-12258
Project: Ignite
Issue Type
> created in current dir.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 3 окт. 2019 г. в 20:05, Pavel Tupitsyn :
>
> > > Cannot tell about NuGet. Maven is typically used during development,
> > usually there is no Maven in production dep
> Cannot tell about NuGet. Maven is typically used during development,
usually there is no Maven in production deployments.
NuGet and Maven are very similar. Yes, both of them are build-time tools,
production is unrelated.
For production-ready deployments we can expect users to tweak Ignite to
ted
> > > by Ignite. So, I'm with Pavel here.
> > >
> > > Alex G, what's your thinking? Sounds like we need to change this one
> more
> > > time.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Wed, Oct 2, 2019 at 12:17 PM Pavel Tupi
owever, I think we should change .net to provide non-default workdir
> location when none is specified.
>
> Can you please clarify scenarios that are broken now?
>
> Regards,
>
> ср, 2 окт. 2019 г., 20:28 Pavel Tupitsyn :
>
> > Igniters,
> >
> > Looks like we
> > > > > > For ZIP installation %HOME% seems to be the best
> approach
> >> for
> >> > > > > > "2-click"
> >> > > > > > > > launch.
> >> > > > > > > > > Later user
Pavel Tupitsyn created IGNITE-12242:
---
Summary: .NET: Add tests for Thin Client async continuation
behavior
Key: IGNITE-12242
URL: https://issues.apache.org/jira/browse/IGNITE-12242
Project: Ignite
Pavel Tupitsyn created IGNITE-12234:
---
Summary: .NET: Fix flaky tests
Key: IGNITE-12234
URL: https://issues.apache.org/jira/browse/IGNITE-12234
Project: Ignite
Issue Type: Improvement
601 - 700 of 1759 matches
Mail list logo
