Denis Garus,
It is forbidden to remove any public IGNITE attribute without proper
deprecation steps.
I have read the thread and still do not clearly see the problem. The subject id
is not required to be a node id.
The referenced in the thread ticket [1] do not provide any reproducers.
Can you
And what about non-java platforms?
Best regards,
Ivan Pavlukhin
пт, 21 февр. 2020 г. в 14:22, Ilya Kasnacheev :
>
> Hello!
>
> I don't see how we can force users to implement Comparable for BinaryObject
> keys, since BinaryObject implementation is not provided by users but by us.
>
> I think
Hello,
We are running Ignite cluster on bare metal on a relatively high core count
machine (4x10 cores 20 threads), and looking some of the thread pool
initialization code:
(IgnitionEx.java)
sysExecSvc = new IgniteThreadPoolExecutor(
"sys",
Hello!
I think they also should do that, but as phase II.
Regards,
--
Ilya Kasnacheev
ср, 26 февр. 2020 г. в 11:26, Ivan Pavlukhin :
> And what about non-java platforms?
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 21 февр. 2020 г. в 14:22, Ilya Kasnacheev :
> >
> > Hello!
> >
> > I don't see
Hi, Alexei.
The ticket [1] describes the general problem for all thin client
authorizations. Its particular case is described in the mentioned in [1]
ticket [2] on the example of a JDBC client with the reproducer attached.
[1] https://issues.apache.org/jira/browse/IGNITE-12589
[2]
Hello!
We recommend exposing IgniteConfiguration for user to modify. You never
know in advance what kind of tuning will be needed, and don't want to play
chinese whispers game with your users.
Regards,
--
Ilya Kasnacheev
ср, 26 февр. 2020 г. в 13:07, Sunny Chan, CLSA :
> Hello,
>
>
>
> We
Taras Ledkov created IGNITE-12717:
-
Summary: SQL: indexing DB object creation refactoring
Key: IGNITE-12717
URL: https://issues.apache.org/jira/browse/IGNITE-12717
Project: Ignite
Issue
Andrey Kuznetsov created IGNITE-12718:
-
Summary: Python Thin Client: add an ability to specify keyfile
password
Key: IGNITE-12718
URL: https://issues.apache.org/jira/browse/IGNITE-12718
Project:
Hello to everybody. I would like to be part of your community.
*My Areas of Expertise *
Core Java, Concurrent Programming, Performance Optimization, Distributed
System, SQL
*How Could I Help*
Fix bugs
Develop a new feature
Fix documentation
*My Jir Account *
j-alimohammadi
Duplicate message, responded in a similar thread.
-
Denis
On Wed, Feb 26, 2020 at 8:04 AM Javad Alimohammadi <
bs.alimohamm...@gmail.com> wrote:
> Hello to everybody. I would be glad to be part of your community.
>
> *My Areas of Expertise *
> Core Java, Concurrent Programming, Performance
Maxim,
Fixes are in ignite-2.8 now, and builds have passed [1].
I think we can proceed.
Thank you and sorry for the broken build.
[1]
https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/5083539?buildTab=overview
On Wed, Feb 26, 2020 at 8:46
Hello Javad,
Welcome to the community, and thanks for sharing your areas of expertise
with interests! You were added to the contributors' list in JIRA.
Please check the "Pick a Ticket" section on this page [1] selecting a task
you'd like to start with. Our community members have refreshed the
Hi Ilya,
For the IgniteConfiguration interface, do we prefer:
1) IgniteConfiguration.setSystemThreadPoolCoreSize(),
IgniteConfiguration.setSystemThreadPoolTimeOut(),IgniteConfiguration.setPublicThreadPoolCoreSize(),
etc.
2) IgniteConfiguration.setSystemThreadPool(ThreadPoolConfiguration),
Sunny Chan created IGNITE-12719:
---
Summary: Allow users to configuring Ignite Thread Pool's Core
thread count/max thread count/etc
Key: IGNITE-12719
URL: https://issues.apache.org/jira/browse/IGNITE-12719
Igor Sapego, Igniters,
I've been working on Ignite website improvements that will be introduced
and contributed later and found that we still don't generate API references
for Node.JS, PHP, Python. The APIs are not even shipped withing binary
packages.
Do our scripts for build/release generate
Hello to everybody. I would be glad to be part of your community.
*My Areas of Expertise *
Core Java, Concurrent Programming, Performance Optimization, Distributed
System, SQL
*How Could I Help*
Fix bugs
Develop a new feature
Fix documentation
*My Jir Account *
j-alimohammadi
Hello everyone. Task 12610 (https://issues.apache.org/jira/browse/IGNITE-12610)
is ready for review
Pavel,
Thank you for your help.
Please, let me know when I can proceed with a vote preparation.
Can you also provide some details - which exactly artefacts should I
check on staging resource after the [1] suite execution?
[1]
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.
There were a few regressions introduced by various recent
19 matches
Mail list logo
