Alexey Kuznetsov created IGNITE-8505:
Summary: Web Console: Add optional description for SQL Notebook
Key: IGNITE-8505
URL: https://issues.apache.org/jira/browse/IGNITE-8505
Project: Ignite
Ilya Borisov created IGNITE-8504:
Summary: Web console: minor update webpack tweaks
Key: IGNITE-8504
URL: https://issues.apache.org/jira/browse/IGNITE-8504
Project: Ignite
Issue Type: Improve
Andrey,
I think the main idea of that not about how to unify writing content to
file. It's about creating peristence files and folders. For other
persistence components (WAL, Checkpoint, etc.) it should be like
FileFactory object with methods like "public File
getOrCreatePartitionFile(...), public
Guys,
Spring is IoC and you can't offer any format that can replace Spring. It
will just limited DSL.
Once again. We have enough problems with main functionality. Why do you
want to focus on minor features?
вт, 15 мая 2018 г., 23:26 Andrey Kuznetsov :
> Pavel,
>
> One can use json-schema if n
Hi,
I understand you idea but it just increases dependencies of different
component from one that is in general bad practice.
We have different components where each one can use different approach for
file management. For example page store and WAL have different file IO
implementations due to pe
Pavel,
One can use json-schema if necessary. Of course, XML is more powerful in
many aspects, but produces more eye fatigue for humans. Of course, we are
to stay with XML if switching to another configuration format requires
significant effort.
BTW, first time I heard about JSON from [1] : " JSON
Hi Igor,
Thanks for creating this!
One question: what is `Multithreading` feature?
Pavel
On Tue, May 15, 2018 at 9:45 PM, Denis Magda wrote:
> Igor,
>
> That's a valid point. Will see how it goes. As for the new documentation
> engine, there are no more arguments. We will try to migrate within
JSON sucks for config files anyway, there are no comments, no schemas,
quotes are required around keys, etc
Just answer one question: what issue are we trying to solve?
XML is not a problem IMO, complexity of our config is.
On Tue, May 15, 2018 at 8:00 PM, Igor Sapego wrote:
> How are you going
Hi Dmitriy,
My question regarding cache interceptor availability in .Net is still
outstanding.
I have working code using a continuous query, but am interested in cache
interceptor if this is a better solution.
Thanks.
Raymond.
*From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]
*Sent:
Alexey,
Any updates?
On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Alexey,
>
> Could you please add more description information for this task? [1]
> Perhaps, base steps for implementation.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8475
Igor,
That's a valid point. Will see how it goes. As for the new documentation
engine, there are no more arguments. We will try to migrate within 2.6.
Just need to find more contributors who would help with this.
--
Denis
On Tue, May 15, 2018 at 2:11 AM, Igor Sapego wrote:
> Thanks for proposa
The scenario is
1- Data is loaded from cassandra to a lookup cache -> replicated cache
2- Data is fetched from kafka input topic to a map
3- the map is inserted - using putall method - to another cache ->
partitioned cache
4- a complex join is done between both caches
5- The result set is process
Github user irudyak closed the pull request at:
https://github.com/apache/ignite/pull/3940
---
Hi Maxim,
FileWriteAheadLogManager & FsyncModeFileWriteAheadLogManager were
intentionally copy-pasted in hope we will soon delete FsyncManager.
But it is still shows this tool works good. Probably we could integrate
this tool to our processes.
Sincerely,
Dmitriy Pavlov
вт, 15 мая 2018 г. в
+1 also for something like "resource manager".
Recently, I've found for myself sonarcloud.io tool for code analisys. It's
free for open source project and I've made Ignite project initial run [1].
I've prepeared analisys for mysefl and found a lot of duplicated code
blocks [1]. Of course it's not
How are you going to translate this YAML config to Spring config?
How would you deal with something like [1]?
[1] -
https://github.com/apache/ignite/blob/master/modules/platforms/cpp/odbc-test/config/queries-ssl-32.xml
Best Regards,
Igor
On Tue, May 15, 2018 at 7:10 PM, Pavel Kovalenko wrote:
Dmitriy Pavlov created IGNITE-8503:
--
Summary: IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has
flaky failure: Entry which should be expired by TTL policy is available after
grid restart
Key: IGNITE-8503
URL
+1 to this approach,
It can be also very helpful in failover scenarios when something wrong
happened with disk. In this case we're reducing the number of points of
failure.
2018-05-15 18:37 GMT+03:00 Dmitriy Govorukhin
:
> Hi Ignite,
>
> Do we have a general approach to work with a file and dir
Mikhail Cherkasov created IGNITE-8502:
-
Summary: Ignite client can hang during a rejoin
Key: IGNITE-8502
URL: https://issues.apache.org/jira/browse/IGNITE-8502
Project: Ignite
Issue Type:
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4004
IGNITE-8501: Retry on GridServiceNotFoundException in GridServiceProxy
needs to be fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grid
Igor,
Just get one of the config samples and translate it directly to YAML:
XML - https://pastebin.com/wtQXXq8f
YAML - https://pastebin.com/akGu3e81
2018-05-15 18:49 GMT+03:00 Igor Sapego :
> Guys, if you think the YAML or JSON would be better, how about
> you provide us a brief example of how s
Guys, if you think the YAML or JSON would be better, how about
you provide us a brief example of how such configs are going to
look, so we can compare and see, if this ever have any sense.
Best Regards,
Igor
On Tue, May 15, 2018 at 4:20 PM, Ilya Kasnacheev
wrote:
> Hello!
>
> Maybe we should ta
Hi Andrei,
Actually I did not understood this issue. What do you mean by tasks?
Probably visor experts may provide feedback.
Would you like to contribute fix with providing some new events? Could you
mention ticket?
Sincerely,
Dmitriy Pavlov
пт, 27 апр. 2018 г. в 16:40, Andrei Aleksandrov :
>
Hi Raymond,
Was this question answered?
Sincerely,
Dmitriy Pavlov
вт, 1 мая 2018 г. в 0:20, Raymond Wilson :
> Cross posting to dev list for comment on cache interceptor availability on
> Ignite .Net client.
>
> -Original Message-
> From: Raymond Wilson [mailto:raymond_wil...@trimble.co
Hi Ignite,
Do we have a general approach to work with a file and directories?
I see many duplication logic for write through .tmp file.
For example,
GridCacheDatabaseSharedManager.writeCheckpointEntry();
GridCacheDatabaseSharedManage.nodeStart();
FileWriteAheadLogManager.FileArchiver.archiveSegm
I've updated the table.
Best Regards,
Igor
On Tue, May 15, 2018 at 12:11 PM, Igor Sapego wrote:
> Thanks for proposals, guys, I will do this.
>
> Denis,
> Readme.io is not very convenient for some big tables. They look OK,
> while they have 3-4 columns, but if we are going to add more clients
>
Stanislav Lukyanov created IGNITE-8501:
--
Summary: Retry on GridServiceNotFoundException in GridServiceProxy
needs to be fixed
Key: IGNITE-8501
URL: https://issues.apache.org/jira/browse/IGNITE-8501
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4003
IGNITE-8500 - Dynamic Cassandra cache creation test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8500
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3959
---
Dmitry Karachentsev created IGNITE-8500:
---
Summary: [Cassandra] Allow dynamic cache creation with Cassandra
Store
Key: IGNITE-8500
URL: https://issues.apache.org/jira/browse/IGNITE-8500
Project:
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4002
IGNITE-8498 JDBC: fix unordered stream compatibility check
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4001
IGNITE-8499 validate_indexes command doesn't detect absent rows in caâ¦
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Ivan Rakov created IGNITE-8499:
--
Summary: validate_indexes command doesn't detect absent rows in
cache data tree
Key: IGNITE-8499
URL: https://issues.apache.org/jira/browse/IGNITE-8499
Project: Ignite
Taras Ledkov created IGNITE-8498:
Summary: JDBC: fix unordered stream comatibility check
Key: IGNITE-8498
URL: https://issues.apache.org/jira/browse/IGNITE-8498
Project: Ignite
Issue Type: Ta
Ilya,
adding of message that will be sent to all other nodes still doesn't
make mentioned task easier. You still should understand where to find
problem description and what exactly.
Only helpful case here is using NoOpFailureHandler because node can
just hang but still be in topology so any diag
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4000
tickTime was tuned in attempt to fix tests instability on TC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Hello!
Maybe we should take .Net configuration as a standard, extend it to JSON
and YAML?
https://apacheignite-net.readme.io/docs/configuration
It should be fairly robust, and there's much less boilerplate.
Regards,
--
Ilya Kasnacheev
2018-05-15 16:09 GMT+03:00 Pavel Kovalenko :
> +1 to
HI Ivan R. ,
I understand now, thank you. Probably we could use title "Ignite triggers
checkpoint upon receiving a SIGINT even if it not required"
вт, 15 мая 2018 г. в 16:08, Ivan Rakov :
> It's a regular priority bug and should be fixed.
> Issue doesn't cause any kind of data loss. It's harmles
+1 to Dmitriy G. proposal.
Since we're moving Ignite towards outside of Java world, we should
definitely care about config usability for users who are not familiar with
Java/Spring.
If we take a look at any of our XML-configs, we can see a lot of
boilerplate like "", "" - terms which say
nothing t
It's a regular priority bug and should be fixed.
Issue doesn't cause any kind of data loss. It's harmless, but still
undesirable: even if checkpoint wasn't running, it will be triggered and
then immediately interrupted by Ignition.stop(true). Such behavior
increases time of following node start
Hi Igor,
Could you please help with answering to this question?
Sincerely,
Dmitriy Pavlov
вт, 15 мая 2018 г. в 5:18, Sunny Chan, CLSA :
> Hello,
>
>
>
> In Ignite-5779 patch, CassandraSessionImpl.java line 289 a null check for row
> has been removed (before the change:
> https://github.com/ap
Hi Igniters, Ivan,
To my mind it is not a bug. Ignite would be able to restore memory state
without waiting checkpoint to be completed. Note checkpoint may be very
long running operation.
Sincerely,
Dmitriy Pavlov
вт, 15 мая 2018 г. в 15:35, Ivan Artukhov (JIRA) :
> Ivan Artukhov created IGNITE
Ivan Artukhov created IGNITE-8497:
-
Summary: Ignite stops the node in the middle of checkpointing upon
receiving a SIGINT
Key: IGNITE-8497
URL: https://issues.apache.org/jira/browse/IGNITE-8497
Projec
Done. Alexander, Alexey, Dmitriy, thank you.
вт, 15 мая 2018 г. в 13:29, Dmitriy Govorukhin :
> Dmitriy,
>
> Looks good for me please merge.
>
> On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com> wrote:
>
>> Dmitriy,
>>
>> Ok, I will do it soon.
>>
>> On Mon, M
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3914
---
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/3999
IGNITE-8493: refactor arrayToString, decrease heap pressure.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8493
I am not the author of the Java checks in this scripts.
To say more about necessity / absence of necessity of Java checks, I will have
to hold an investigation.
I have filed the issue [1] and add it to backlog for next release (approx. 2.6).
[1] https://issues.apache.org/jira/browse/IGNITE-8496
Peter Ivanov created IGNITE-8496:
Summary: Check necessity of JDK check in SqlLine script
Key: IGNITE-8496
URL: https://issues.apache.org/jira/browse/IGNITE-8496
Project: Ignite
Issue Type: T
Actually sometimes users ask about JSON configuration (e.g. was PR in
vertx-ignite project). But it's non trivial task because it will
require development of some DSL (or set of DSL's) and will make adding
new configuration elements some kind of pain while we should be
focused on basic functionalit
Igor Sapego created IGNITE-8495:
---
Summary: CPP Thin: Implement thin client start and connection
establishment
Key: IGNITE-8495
URL: https://issues.apache.org/jira/browse/IGNITE-8495
Project: Ignite
Igor Sapego created IGNITE-8494:
---
Summary: CPP Thin: Implement Thin CPP client
Key: IGNITE-8494
URL: https://issues.apache.org/jira/browse/IGNITE-8494
Project: Ignite
Issue Type: New Feature
Dmitriy,
Looks good for me please merge.
On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Dmitriy,
>
> Ok, I will do it soon.
>
> On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov
> wrote:
>
>> Hi Dmitriy G,
>>
>> could you please pick up this review?
>
Petr, do we really need to check Java version for SqlLine at all? I think
it will work with any version of Java, so restricting it to a certain
version is just wrong.
What do you think about removing the Java version check altogether from the
SqlLine script?
D.
On Tue, May 15, 2018 at 10:21 AM,
Stanilovsky Evgeny created IGNITE-8493:
--
Summary: [Test] GridToStringBuilder fails with NPE deals with
primitive arrays operations.
Key: IGNITE-8493
URL: https://issues.apache.org/jira/browse/IGNITE-8493
Hi Igniters,
By common efforts from maintainers, committers and experienced
contributors, it was possible to reduce the number of PA tasks
- waiting for review to 88,
- with no activity for 1 month and waiting for review to 24.
'No activity' tasks are more than a quarter from all patches waitin
I still do not understand *why* do we need to add additional formats for
the configuration. Can you please show me some users on the user@ list or
stack overflow who asked for it? I just want to make sure that if we are
creating work for ourselves, then someone actually needs it.
D.
On Tue, May 1
I don't think we need to add new formats on server side as there may
be a lot of different formats for different clients. On the other hand,
supporting additional formats may be non trivial and error-prone, while
adding little to a user experience.
For clients, I see no problem in adding for examp
Folks,
I guess when work on a thin client will be completed, we get more newcomers
who use go/python/php/js.
And we can do ignite more friendly for them, support familiar formats for
configuration.
On Tue, May 15, 2018 at 12:13 PM, Dmitry Pavlov
wrote:
> Hi Igniters,
>
> In general I aggree wit
Hi Igniters,
In general I aggree with adding new format, e.g. JSON is more popular than
XML for new applications.
In the same time I've never heard that user asked this in the user list. Or
did I missed such topics?
Sincerely,
Dmitriy Pavlov
вт, 15 мая 2018 г. в 9:31, Pavel Tupitsyn :
> Dmitri
Thanks for proposals, guys, I will do this.
Denis,
Readme.io is not very convenient for some big tables. They look OK,
while they have 3-4 columns, but if we are going to add more clients
(or should I say "when") it is going to be a mess. This may be a one
more argument when we consider to change
Hi Alexey, thank you for review.
Hi Igor, could you please merge this PR?
вт, 15 мая 2018 г. в 11:18, Alexey Kuznetsov :
> Looks good for me now.
>
> On Tue, May 15, 2018 at 12:38 AM, Dmitry Pavlov
> wrote:
>
> > Hi Alexey K,
> >
> > could you please check that all proposals were applied?
> >
>
I'd like to thank GridGain's engineers for the plugin's donation.
I believe that the plugin will help Ignite's developers prepare PR
with the higher quality of code style what will reduce reviewer's time
for PR checking.
Dmitry thank you for the task's pushing!
On Mon, May 14, 2018 at 7:27 PM,
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/3998
ignite-2.5.1-p2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p2
Alternatively you can revi
Taras Ledkov created IGNITE-8492:
Summary: JDBC: Add a note about authentication for thin driver to
docs
Key: IGNITE-8492
URL: https://issues.apache.org/jira/browse/IGNITE-8492
Project: Ignite
Vladislav Pyatkov created IGNITE-8491:
-
Summary: Add JMX flag: Is the node in baseline or not?
Key: IGNITE-8491
URL: https://issues.apache.org/jira/browse/IGNITE-8491
Project: Ignite
Issu
Alexey Kuznetsov created IGNITE-8490:
Summary: Web Console: Update to AngularJS 1.7.x
Key: IGNITE-8490
URL: https://issues.apache.org/jira/browse/IGNITE-8490
Project: Ignite
Issue Type: B
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/3997
IGNITE-8449 no need for checkpoint lock in case of stale updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Dmitriy,
Ok, I will do it soon.
On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov
wrote:
> Hi Dmitriy G,
>
> could you please pick up this review?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 10 мая 2018 г. в 15:50, Александр Меньшиков :
>
>> Hi,
>>
>> I have fixed problem with the test
>> CacheGroupsM
Looks good for me now.
On Tue, May 15, 2018 at 12:38 AM, Dmitry Pavlov
wrote:
> Hi Alexey K,
>
> could you please check that all proposals were applied?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 10 мая 2018 г. в 22:59, Igor Rudyak :
>
> > Hi guys,
> >
> > I addressed all the comments and need one
Not yet.
After 2.5 release, I plan to prepare a roadmap for Apache Ignite support of
future Java releases (based on their’s current release cycle) and to coordinate
corresponding works for introducing support of future Java versions.
> On 15 May 2018, at 01:55, Dmitriy Setrakyan wrote:
>
>
70 matches
Mail list logo