Pavel Tupitsyn created IGNITE-12176:
---
Summary: .NET: Apache.Ignite.exe fails when config has custom
logger or plugins
Key: IGNITE-12176
URL: https://issues.apache.org/jira/browse/IGNITE-12176
Pavel Tupitsyn created IGNITE-12169:
---
Summary: Dockerfile: Thin Client and REST API ports are not exposed
Key: IGNITE-12169
URL: https://issues.apache.org/jira/browse/IGNITE-12169
Project: Ignite
+1 (binding)
On Fri, Sep 13, 2019 at 8:09 PM Denis Magda wrote:
> +1 (binding)
>
> -
> Denis
>
>
> On Fri, Sep 13, 2019 at 1:30 AM Alexey Goncharuk <
> alexey.goncha...@gmail.com>
> wrote:
>
> > Dear Community,
> >
> > We have uploaded release candidate to
> >
Pavel Tupitsyn created IGNITE-12166:
---
Summary: .NET: ExecutableTest fails with PathTooLong error
Key: IGNITE-12166
URL: https://issues.apache.org/jira/browse/IGNITE-12166
Project: Ignite
Pavel Tupitsyn created IGNITE-12140:
---
Summary: .NET: TestBaselineTopology pollutes environment variables
Key: IGNITE-12140
URL: https://issues.apache.org/jira/browse/IGNITE-12140
Project: Ignite
Andrey is right, dev list is our primary form of communication, and for
many good reasons.
Other forms of communications are fine, but all discussions/decisions
should be reflected on the dev list in one form or another.
- Had a chat in slack and agreed on something? Write a summary to the dev
Pavel Tupitsyn created IGNITE-12132:
---
Summary: .NET: StreamTransformer is not invoked for duplicate
entries
Key: IGNITE-12132
URL: https://issues.apache.org/jira/browse/IGNITE-12132
Project: Ignite
s not related to JDBC and ODBC, but I think it's redundant.
>
> ср, 28 авг. 2019 г. в 12:41, Pavel Tupitsyn :
>
> > ThinClientConfiguration name is very confusing in existing situation.
> > E.g. does it apply to JDBC Thin Client? No, it does not, but it is easy
> to
> > assu
BC connector configuration?
> > > > > > >
> > > > > > > I think this is a bad practice: For example, people often turn
> on
> > > SSL
> > > > > or
> > > > > > > auth on just a subset of connectors, think they ar
+1 for ~/.ignite/work
As Petr mentioned above, this translates well to Windows and MacOS too, we
can use "home directory" term in documentation and it works for any OS.
On Mon, Aug 26, 2019 at 4:03 PM Nikolay Izhikov wrote:
> AFAIK server admin expects software will store it's data in /var/
>
, Denis Magda :
> > >
> > >> +1 for the user.dir as a default one.
> > >>
> > >> Denis
> > >>
> > >> On Monday, August 12, 2019, Dmitriy Pavlov
> wrote:
> > >>
> > >> > +1 to user home directory. A numbe
y
> directly into ClientConnectorConfiguration, someone might think that it
> also affects JDBC and ODBC.
>
> пт, 23 авг. 2019 г. в 19:59, Pavel Tupitsyn :
>
> > Igor, Alex,
> >
> > Not sure I agree with this: ThinClientConfiguration inside
> > ClientConn
+1, checked .NET node start and examples
On Fri, Aug 23, 2019 at 6:49 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> +1
>
> пт, 23 авг. 2019 г. в 18:33, Alexey Goncharuk >:
>
> > +1
> > Checked the source compilation and release package build, node start,
> and a
> > few
Pavel Tupitsyn created IGNITE-12095:
---
Summary: .NET: Remove empty tracing-related interfaces from public
API
Key: IGNITE-12095
URL: https://issues.apache.org/jira/browse/IGNITE-12095
Project
t;
> > > On 17/08/2019, at 1:45 PM, Ilya Kasnacheev
> > wrote:
> > >
> > > Hello!
> > >
> > > Can we get back to this question? It rears its ugly head again:
> > >
> >
> https://stackoverflow.com/questions/57513576/apache-igni
gt; Can anyone review the patch?
> > >
> > > [1]: https://issues.apache.org/jira/browse/IGNITE-9410
> > > [2]:
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support
> > >
> >
Hi Ivan,
> fail Ignite node in case neither IGNITE_HOME
nor IgniteConfiguration#igniteWorkDir is set
I strongly disagree, this is bad usability.
Ignition.start() should work without any extra configuration as is it right
now.
Let's come up with reasonable defaults instead, user dir sounds good
back eventually?
>
> In case of Java futures with listeners, I think listeners should be invoked
> from public pool.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 9 авг. 2019 г. в 19:16, Pavel Tupitsyn :
>
> > Well, you can't just take any running thread and make i
futures out of striped
> pool,
> > > > while holding any cache logs (stripe thread counts as one).
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > ср, 7 авг. 2
gt; > I think we should definitely stop running futures out of striped pool,
> > while holding any cache logs (stripe thread counts as one).
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 7 авг. 2019 г. в 17:20, Pavel Tupitsyn :
>
I agree that attribute-based filtering is enough.
We should get rid of predicates in configuration as much as possible:
they introduce a lot of complexity for other platforms (.NET), among other
things mentioned above.
On Thu, Aug 8, 2019 at 2:04 PM Pavel Kovalenko wrote:
> Ivan,
>
> > And
TE-12033 could be used to track this work.
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 7 авг. 2019 г. в 01:47, Pavel Tupitsyn :
>
>> Sorry guys, I've completely missed this thread, and the topic is very
>>
Most probably - yes
On Fri, Jul 26, 2019 at 1:36 AM Raymond Wilson
wrote:
> Thanks Pavel!
>
> Does the priority on the Jira ticket suggest this will target IA 2.8?
>
> Thanks,
> Raymond.
>
> On Wed, Jul 24, 2019 at 8:21 PM Pavel Tupitsyn
> wrote:
>
>> D
Denis, I've just created one:
https://issues.apache.org/jira/browse/IGNITE-12012
Thanks
On Thu, Jul 25, 2019 at 2:25 AM Denis Magda wrote:
> Pavel,
>
> Do we already have a ticket or do you want me to create one?
>
> -
> Denis
>
>
> On Wed, Jul 24, 2019 at 1:21
Pavel Tupitsyn created IGNITE-12012:
---
Summary: .NET: ICompute.WithExecutor
Key: IGNITE-12012
URL: https://issues.apache.org/jira/browse/IGNITE-12012
Project: Ignite
Issue Type: Improvement
Denis, yes, looks like a simple thing to add.
On Tue, Jul 23, 2019 at 10:38 PM Denis Magda wrote:
> Looping in the dev list.
>
> Pavel, Igor and other C# maintainers, this looks like a valuable extension
> of our C# APIs. Shouldn't this be a quick addition to Ignite?
>
> -
> Denis
>
>
> On Mon,
Pavel Tupitsyn created IGNITE-11985:
---
Summary: .NET: CompiledQuery.Compile does not work with string
parameters
Key: IGNITE-11985
URL: https://issues.apache.org/jira/browse/IGNITE-11985
Project
Big changes for .NET:
* Remove legacy Entity Framework integration
* Remove legacy ASP.NET integration
* Move from .NET Framework 4.0 (released in 2010) to .NET Standard 2.0
(modern way to build libraries)
Thanks,
Pavel
On Mon, Jun 17, 2019 at 7:14 PM Igor Sapego wrote:
> For the C++ I propose
T Framework Cryptography Model
>
> href=https://dotnet.microsoft.com/download
>
> >>>>>>
>
>
>
> Open questions:
>
> 1) Declaring older versions of Ignite.
>
> 2) Is it correct to mention that Ignite uses .NET core controlled by .NET
>
>
/PKCS5Padding encryption from the Java libraries for
>transparent data encryption of data on disk (
>https://apacheignite.readme.io/docs/transparent-data-encryption)
>3. Libraries/vendors for .NET nodes security?* Pavel Tupitsyn*, could
>you check?
>4. Libraries/vendors
-1 (binding)
NuGet packages for Ingite.NET were not built as described in [1].
This is automated on TeamCity, but was not triggered [2]
[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
[2]
Alex,
> now we can only support one active transaction per connection
I totally understand server-side and protocol limitations that are causing
this.
But I have no idea how to support this in .NET Thin Client, for example.
It is thread-safe and can handle multiple async operations in parallel.
Pavel Tupitsyn created IGNITE-11659:
---
Summary: .NET: Add TcpDiscoveryKubernetesIpFinder
Key: IGNITE-11659
URL: https://issues.apache.org/jira/browse/IGNITE-11659
Project: Ignite
Issue Type
To avoid deadlocks you have to always take locks in the same order.
* That order is not always going to be "sorted with default comparer".
* Not every type has a default comparer
So Ignite can't sort the keys for you, nor can it check if they are sorted.
And even if it could, it would be making
s implement it for
> the
> > beginning and set this feature to "false" by default, as this feature
> looks
> > complex, probably error-prone, and should be considered in a "beta"
> > state for the first release.
> >
> > Best Regards,
>
t; Best Regards,
> Igor
>
>
> On Fri, Mar 8, 2019 at 11:37 AM Pavel Tupitsyn
> wrote:
>
> > > maxConnectionNumber parameter
> > What's the idea? Follow the Best Effor Affinity logic, but establish up
> to
> > N connections?
> >
> > On Thu, M
ast one
> connection. Other connections established in background by a separate
> thread. This one is harder to implement and maybe it makes sense to add
> it as a separate feature.
>
> Best Regards,
> Igor
>
>
> On Wed, Mar 6, 2019 at 9:43 PM Pavel Tupitsyn
> wrote:
&
> partition for a given key properly.
>
> [1] -
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
>
> Best Regards,
> Igor
>
>
> On Mon, Feb 4, 2019 at 8:24 PM Pavel Tupitsyn
> wrote:
>
> > Looks goo
> > append to the response *list of caches with the same
> >> distribution*.
> >> > > I.e.:
> >> > > > >
> >> > > > > class AffinityResponse {
> >> > > > > Object distribution;// Actual distribution
>
, 2019 at 1:05 PM Igor Sapego wrote:
>
> > Yeah, I'll add it.
> >
> > Best Regards,
> > Igor
> >
> >
> > On Wed, Jan 16, 2019 at 11:08 PM Pavel Tupitsyn
> > wrote:
> >
> >> > to every server
> >> I did not think of this
here defined and it's not clear
> for
> > users.
> >
> > чт, 24 янв. 2019 г. в 17:18, Pavel Tupitsyn :
> >
> >> Yes
> >>
> >> On Thu, Jan 24, 2019 at 5:15 PM Sergey Antonov <
> antonovserge...@gmail.com>
> >> wrote:
> >>
Yes
On Thu, Jan 24, 2019 at 5:15 PM Sergey Antonov
wrote:
> Pavel,
>
> "Leave it as is, use instanceof."
> You meant always use CacheInterceptor and in all methods
> check, that passed arguments is BinaryObject?
>
> чт, 24 янв. 2019 г. в 17:10, Pavel Tupitsyn
, Jan 24, 2019 at 2:16 PM Sergey Antonov
wrote:
> Pavel, how about marker interface DeserializedValueCacheInterceptor? We
> will deserialize data and pass it to cache interceptor, if CacheInterceptor
> implements marker interface.
>
> чт, 24 янв. 2019 г. в 13:41, Pavel Tupit
erceptors must have Object, Object parameters for supporting both
> modes: binary and deserialized. In this case parametrized class no sense.
>
> [1]
>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheInterceptor.html
>
> чт, 24 янв. 2019 г. в 13:06,
Hi Sergey,
I don't think this is a bug.
Thick or thin clients always work in binary mode on server side, because
you receive data in serialized form and there is no point in deserializing
it.
Moreover, in most cases you don't have classes on the server, so binary
mode is the only way.
Hi Lev, reviewed, please see my comment in JIRA
Thank you and welcome to the community!
On Wed, Jan 23, 2019 at 2:37 PM Лев Хенкин wrote:
> Thanks a lot, I've already submitted a patch and asked Pavel Tupitsyn to
> review it.
>
> 23.01.2019, 14:16, "Dmitriy Pavlov" :
&g
Igor,
> It is proposed to add flag to every response, that shows whether the
Affinity Topology Version of the cluster has changed since the last request
from the client.
I propose to keep this flag. So no need for periodic checks. Makes sense?
On Tue, Jan 15, 2019 at 4:45 PM Igor Sapego wrote:
GitHub has an option to disable non-squash commit in the repo settings.
Can we use that?
[image: image.png]
On Tue, Jan 15, 2019 at 6:30 PM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Please, note, Github merges without squashing by default.
> Use "squash and merge" option in drop down list.
Hi Igor,
Looks good to me in general, except changing the response message format so
much.
Can we use a separate message to retrieve affinity topology version?
Set a flag as you describe, but don't put the version data into standard
response?
Just to keep the protocol cleaner, follow SRP to
Pavel Tupitsyn created IGNITE-10795:
---
Summary: Create Ignite.NET Dockerfile
Key: IGNITE-10795
URL: https://issues.apache.org/jira/browse/IGNITE-10795
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-10702:
---
Summary: .NET: Ignite as Dotnet Core Global Tool
Key: IGNITE-10702
URL: https://issues.apache.org/jira/browse/IGNITE-10702
Project: Ignite
Issue Type
ther, let's solve real
> > > > problem:
> > > >
> > > > - help the community doing PR review.
> > > > - fixing failing tests.
> > > > - introducing new code inspections to make our code base
> clear.
&
Agree with Dmitriy.
We use GitHub PRs in our workflow, therefore we should keep them in order.
We can close PRs that refer to closed tickets, this can be done with a
simple script.
On Tue, Dec 11, 2018 at 9:15 AM Павлухин Иван wrote:
> Nikolay,
>
> I must say that when I first saw 1K+ open
Pavel Tupitsyn created IGNITE-10634:
---
Summary: .NET: EntityFramework Core Second Level Cache
Key: IGNITE-10634
URL: https://issues.apache.org/jira/browse/IGNITE-10634
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-10554:
---
Summary: .NET: Jars are not copied to target dir under .NET Core
Key: IGNITE-10554
URL: https://issues.apache.org/jira/browse/IGNITE-10554
Project: Ignite
+1
Downloaded sources, build Java and .NET parts, ran examples.
There is a minor issue with .NET Core examples, compiler warning is
displayed (certainly not a blocker) [1]
[1] https://issues.apache.org/jira/browse/IGNITE-10500
On Sat, Dec 1, 2018 at 12:47 AM Nikolay Izhikov wrote:
> Igniters,
Pavel Tupitsyn created IGNITE-10500:
---
Summary: .NET: Compiler warning when building examples
Key: IGNITE-10500
URL: https://issues.apache.org/jira/browse/IGNITE-10500
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-10451:
---
Summary: .NET: Persistence does not work with custom affinity
function
Key: IGNITE-10451
URL: https://issues.apache.org/jira/browse/IGNITE-10451
Project
Pavel Tupitsyn created IGNITE-10411:
---
Summary: .NET: Allow conditional serialization override
Key: IGNITE-10411
URL: https://issues.apache.org/jira/browse/IGNITE-10411
Project: Ignite
anything into binary object, but when it
> comes to real store, exception will be thrown.
>
> Makes sense?
>
> On Wed, Nov 21, 2018 at 3:21 PM Pavel Tupitsyn
> wrote:
>
> > Vladimir,
> >
> > IMO the issue is that we allow any type of data in the cache (put Person,
&
Vladimir,
IMO the issue is that we allow any type of data in the cache (put Person,
then put int to the same cache).
Are we going to address this in 3.0 and enforce key/value types according
to cache configuration?
This will provide more space for optimizations.
On Wed, Nov 21, 2018 at 3:14 PM
Personal emails for _watched_ JIRA tickets are very useful.
Emails to everyone are not.
+1 for separate mailing list for all automated emails.
I don't think we can avoid automated emails completely, but dev list should
be human-only.
So separate list is the only way.
On Thu, Nov 15, 2018 at
Thank you. Fix has been merged to master and cherry-picked to ignite-2.7.
On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov wrote:
> Pavel.
>
> Ok, I agree to include this ticket into 2.7
> Let's do it.
>
> В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет:
> > Nikola
Nikolay,
It completely breaks a major feature under certain conditions. I would
consider it a blocker.
On Wed, Oct 17, 2018 at 1:00 PM Nikolay Izhikov wrote:
> Hello, Pavel.
>
> Is it a blocker?
>
> В Ср, 17/10/2018 в 12:58 +0300, Pavel Tupitsyn пишет:
> > Hi Ignit
Hi Igniters,
I'd like to include IGNITE-9877 in 2.7, can we do that?
The fix is ready, I'm waiting for TC run.
Pavel
On Wed, Oct 17, 2018 at 11:45 AM Павлухин Иван wrote:
> Hi NIkolay,
>
> Thank you for keeping everybody focused! Regarding to my ticket
> IGNITE-5935.
> It is in final stage
Pavel Tupitsyn created IGNITE-9877:
--
Summary: .NET: AmbiguousMatchException under .NET Core 2.1
Key: IGNITE-9877
URL: https://issues.apache.org/jira/browse/IGNITE-9877
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-9876:
--
Summary: .NET: Thin Client: Implement Best Effort Affinity
Key: IGNITE-9876
URL: https://issues.apache.org/jira/browse/IGNITE-9876
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-9757:
--
Summary: С++: DetachCurrentThread is never called, causing Java
thread leak
Key: IGNITE-9757
URL: https://issues.apache.org/jira/browse/IGNITE-9757
Project
Denis,
Can't say for sure, did not investigate this yet. I'll try to find time
next week and get back to you.
On Sat, Sep 22, 2018 at 4:23 AM Denis Magda wrote:
> Pavel,
>
> Do you think we can get it fixed in 2.7 time frame?
>
> --
> Denis
>
> -- Forwarded message -
> From:
Hi,
Can you please elaborate, what does the plugin do?
On Mon, Sep 17, 2018 at 10:49 PM wt wrote:
> I have almost completed a plugin in java and was wondering if this plugin
> could be made available in .net. I have seen an example online (here -
>
>
{
> return ignite.SetDependencyResolver(new
> CastleWindsorDependencyResolver(kernel));
> }
> }
> }
>
> 8. Write test.
>
>
> *Usage*
>
> var grid = Ignition.Start();
>
> using (var container = new WindsorContainer())
> {
>
> Actually I did it on my personal branch and I would love to push it into
> Ignite git.
>
>
>
>
> Vào Th 3, 11 thg 9, 2018 lúc 2:47 SA Pavel Tupitsyn
> đã viết:
>
> > Hi,
> >
> > Text query should be easy to implement in thin client protocol, all the
>
Pavel Tupitsyn created IGNITE-9529:
--
Summary: .NET: Thin client: Implement TextQuery
Key: IGNITE-9529
URL: https://issues.apache.org/jira/browse/IGNITE-9529
Project: Ignite
Issue Type
Hi,
Text query should be easy to implement in thin client protocol, all the
plumbing is there for cursors and so on.
We just need a new operation similar to existing ones.
Are you going to add it to .NET Thin Client?
Pavel
On Mon, Sep 10, 2018 at 8:22 PM Dmitriy Pavlov
wrote:
> Hi, sure,
Hi Artyom,
Ticket already exists: https://issues.apache.org/jira/browse/IGNITE-9299
Feel free to grab it.
But before diving deep into coding, can you please provide a short overview
of the proposed implementation?
Either on dev list or in JIRA ticket directly.
Thanks,
Pavel
On Mon, Sep 10,
Can you provide a reproducer please?
On Mon, Sep 10, 2018 at 9:15 AM Tâm Nguyễn Mạnh
wrote:
> Hi Paven,
>
> This is not compile error, this is runtime error. I got this while i try to
> use linq to query name contains (.NET core)
>
> On Sun, Sep 9, 2018 at 5:29 PM Pavel
Hi,
Do you mean that you can't compile the code?
It certainly compiles (under full .NET, .NET Core, and Mono, on Windows and
Linux), so it seems like some issue with your environment.
Can you do a fresh git checkout, then run `build.bat`?
Pavel
On Fri, Sep 7, 2018 at 5:16 AM Tâm Nguyễn Mạnh
Pavel Tupitsyn created IGNITE-9299:
--
Summary: .NET: Support dependency injection for user-defined
classes that are instantiated by Ignite
Key: IGNITE-9299
URL: https://issues.apache.org/jira/browse/IGNITE-9299
schema name is constructed here:
> org.apache.ignite.internal.processors.query.QueryUtils#normalizeSchemaName
>
> On Mon, Aug 13, 2018 at 1:55 PM Pavel Tupitsyn
> wrote:
>
> > Igniters,
> >
> > For .NET LINQ provider[1] I need to be able to infer SQL schema name from
>
Igniters,
For .NET LINQ provider[1] I need to be able to infer SQL schema name from
CacheConfiguration.
Looks like value from CacheConfiguration gets uppercased when not quoted.
So my logic for now is:
* if config.SqlSchema == null, use config.name
* otherwise, if config.SqlSchema does not
Hi Denis,
I've updated NuGet package description and docs:
https://github.com/apache/ignite/commit/af03d8413defc992501ffc7246427df6a46c6840
On Mon, Aug 6, 2018 at 11:06 PM Pavel Tupitsyn wrote:
> Hi Denis,
>
> Sorry for the late reply. I'm on vacation with limited internet access.
&g
Hi Denis,
Sorry for the late reply. I'm on vacation with limited internet access.
I think I can do this next week.
Thanks,
Pavel
On Wed, Aug 1, 2018 at 12:17 AM Denis Magda wrote:
> Hey Pavel,
>
> Could you help to update Ignite definition in accordance to the website?
> .NET docs [1] and
Pavel Tupitsyn created IGNITE-9116:
--
Summary: .NET: LINQ: CacheConfiguration.SqlSchema is ignored
Key: IGNITE-9116
URL: https://issues.apache.org/jira/browse/IGNITE-9116
Project: Ignite
gt;
>
> > On 17 Jul 2018, at 18:21, Pavel Tupitsyn wrote:
> >
> > Oh sorry I missed the question.
> > * The build script '[Prepare Vote #3] Build NuGet packages' produces the
> > artifacts (.nupkg files).
> > * Then we have to manually upload them to NuGet
get push the packages will
> be deployed to some default host or host should be specified manually
> somehow?
>
>
> > On 17 Jul 2018, at 18:21, Pavel Tupitsyn wrote:
> >
> > Oh sorry I missed the question.
> > * The build script '[Prepare Vote #3] Build NuGet packages'
://cwiki.apache.org/confluence/display/IGNITE/Release+Process
On Tue, Jul 17, 2018 at 5:55 PM Petr Ivanov wrote:
> Just tell us please HOW it should be done, please.
>
> With what build or script or other procedure?
>
>
>
>
> > On 17 Jul 2018, at 17:44, Pavel Tupitsyn wrot
can be uploaded Nuget packages found?
>
> On Mon, 16 Jul 2018 at 23:37, Pavel Tupitsyn wrote:
>
> > Petr,
> >
> > This is the same build that I have linked. Is there anything I should pay
> > attention to?
> >
> > On Mon, Jul 16, 2018 at 11:05 PM Petr I
Log.html?buildId=1502954=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildLog&_focus=230#_state=230
> <
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildLog&_focus=230#_state=230
> >
>
>
>
>
>
ut
> if it the case, I can do it carefully.
>
>
> BTW, on the agent where all tests are passed the same file exists as
> aforementioned ones, no obvious differences.
>
>
>
>
>
> > On 6 Jul 2018, at 12:15, Pavel Tupitsyn wrote:
> >
> > Petr,
>
I see that some .NET Linux builds are now green.
Petr, have you done anything other than reboot?
On Fri, Jul 6, 2018 at 3:05 PM Petr Ivanov wrote:
> Agents rebooted
>
>
>
> > On 6 Jul 2018, at 14:09, kcheng.mvp wrote:
> >
> > In the console of TeamCity, I noticed some message
> >
> >
> > Some
an.
>
>
> Can you prepare reproduce steps so that I’ll be able to pinpoint the
> problem faster, please?
>
>
> > On 5 Jul 2018, at 11:25, Pavel Tupitsyn wrote:
> >
> > Igniters,
> >
> > I need help with TeamCity.
> > .NET Linux Te
Dmitry, see my reply above. I will provide steps to Petr in that other
thread.
On Fri, Jul 6, 2018 at 12:00 PM Dmitry Pavlov wrote:
> Hi,
>
> Unfortunately this problem also occurs in master, so for now everything we
> can do now it is to Ignore it for PR and handle it as part of Make TeamCity
Yes, this is being discussed in [1]
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/NET-tests-fail-on-Linux-need-help-with-TeamCity-td32235.html
On Fri, Jul 6, 2018 at 8:52 AM kcheng.mvp wrote:
> I have triggered my tests many times on TeamCity. every time I get the same
> result.
>
Igniters,
I need help with TeamCity.
.NET Linux Tests [1] fail for a very weird reason:
Newtonsoft.Json.dll seems to be corrupted or empty " *Image is too small.*
".
I tried adding a step to clean NuGet caches, but it does not help.
On my Ubuntu box tests pass. And there were no changes to .NET
Roman,
Thanks for the reproducer. I needed that to better understand the issue.
And, I'm afraid, we won't have support for this kind of queries anytime
soon.
Even Entity Framework does not support this kind of grouping.
On Fri, Jun 22, 2018 at 1:18 PM Roman Guseinov wrote:
> Hi Pavel,
>
>
Roman,
Can you try rephrasing the LINQ query as the SQL goes?
var q1 = queryable.GroupBy(o => o.Value.ContractId).Select(g => new
{ContractId = g.Key, MaxVer = g.Select(x=>x.Value.Version).Max()});
var q2 = q1.Select( ...)
At least this first part works for me. I did not try further.
Ideally
Hi Roman,
It is even hard to say what kind of SQL should we produce for such a query.
The general idea of Ignite LINQ provider is:
Do not try to support every LINQ expression (which is not possible, because
LINQ and SQL are quite different);
but try to make most SQL scenarios possible to express
Same thing with package manager for .NET (NuGet).
And same with Java, actually (Maven).
In my understanding, most people use package managers and don't download
ZIP archives.
Package managers are more convenient and easy to use. It is a modern way.
On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr
partition
> > is "hash(key) % partitions". This is all we need to make default affinity
> > work.
> >
> > On Thu, Jun 14, 2018 at 11:41 AM, Pavel Tupitsyn
> > wrote:
> >
> > > AffinityFunction interface has the following method:
> > >
or will
> >turn a special flag in the response suggesting the client do that
> > manually.
> >
> > Igor, is this what you're suggesting?
> >
> > --
> > Denis
> >
> > On Wed, Jun 13, 2018 at 11:31 AM Pavel Tupitsyn
> > wrote:
>
701 - 800 of 1756 matches
Mail list logo
