>
> >
> > I will proceed with Java updates. Will notify when finished.
> >
> >
> >
> >
> > > On 10 Aug 2018, at 11:37, Nikolay Izhikov wrote:
> > >
> > > Hello, Petr.
> > >
> > > TDE t
Hello, Paul.
Is there a ticket you trying to resolve?
Yes, please, provide the patch, so community can take a look.
В Чт, 16/08/2018 в 15:03 +0200, Paul Anderson пишет:
> org.apache.ignite.internal.commandline.CommandHandler (control.sh)
>
> Can I send you a diff rather than becoming a contribut
Let's do it.
Please, send a ticket number to this thread.
В Чт, 16/08/2018 в 15:22 +0200, Paul Anderson пишет:
> We needed here so I just did it... Very simple will raise a ticket and add
> patch to it...
>
> On Thu, 16 Aug 2018, 15:21 Nikolay Izhikov, wrote:
>
> >
Hello, Vladimir.
> 1) *Event ordering*.
I vote to keep things as is.
> 2) *Initial query*
> With MVCC it is now
> technically possible to query data on certain snapshot and then receive
> only events happened after this snapshot
I think it a usefull extension for current implementation.
В Пт,
Hello, Stuart.
Personally, I think we should change current tables naming and return table in
form of `schema.table`.
Valentin, could you share your opinion?
В Пн, 20/08/2018 в 10:04 +0100, Stuart Macdonald пишет:
> Igniters,
>
> While reviewing the changes for IGNITE-9228 [1,2], Nikolay and
Hello, Igniters.
I'm release manager of Apache Ignite 2.7.
It's time to start discussion of release. [1]
Current code freeze date is September, 30.
If you have any objections - please, responsd to this thread.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
signature.a
CC)
> - service grid stabilization
> - SQL memory utilization improvements
> - more?
>
> Can you please solicit status from the community for these tasks?
>
> D.
>
> On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
rations take this into account somehow.
>
> -Val
>
> On Mon, Aug 20, 2018 at 6:12 AM Nikolay Izhikov wrote:
> > Hello, Stuart.
> >
> > Personally, I think we should change current tables naming and return table
> > in form of `schema.table`.
> >
>
o the Spark table attribute.
> > >
> > > Stuart.
> > >
> > > [1]
> > > https://github.com/apache/spark/blob/master/sql/core/
> > > src/main/scala/org/apache/spark/sql/execution/
> > > datasources/jdbc/JDBCRelation.scala
> > >
Hello, Igniters.
While working on IGNITE-6055 [1] I need to do some fixes in ODBC.
I find out that setup of local CPP development environment is a very hard task:
1. Linux -
- We use a very old version of boost library.
Modern Linux distribution uses the new one.
Ther
gt;
> > Such article as "Ignite.NET Development" [1] helped me to prepare the
> > environment step by step.
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Ignite.NET+Development
> >
> > On Wed, Aug 22, 2018 at 12:06 PM Nikol
Hello, Vyacheslav.
Thanks, for sharing your design.
> I have a question about services migration from AI 2.6 to a new solution
Can you describe consequences of not having migration solution?
What will happen on the user side?
В Чт, 23/08/2018 в 14:44 +0300, Vyacheslav Daradur пишет:
> Hi, Igni
e sense.
>
> -Val
>
>
> On Wed, Aug 22, 2018 at 1:44 AM Nikolay Izhikov wrote:
>
> > Hello, Valentin.
> >
> > > I believe we should get rid of this logic and use Ignite schema name as
> >
> > database name in Spark's catalog.
> >
&
is thread, so that the community can track them.
> >
> > D.
> >
> > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov
> > wrote:
> >
> > > Hello, Dmitriy.
> > >
> > > I think Transparent Data Encryption will be available in 2.7
&g
ce/display/IGNITE/Apache+Ignite+2.7
В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> Hello, Pavel.
>
> Please, be aware of IGNITE-6055 [1]
>
> I'm edit thin protocol in that ticket.
> I can't support changes in Python and PHP clients, because, they are not
n tickets now according to [1]. This seems a bit to much.
> Can I ask everyone to review tickets assigned to yourselves and move those
> that will not be fixed. Then Nikolay will process the ones that are not
> assigned yet. Nikolay, can you take a look please?
>
> --Yakov
nts are merged to master, so the sooner you merge the PR the better.
>
> p.
>
> On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov wrote:
> > Hello, Pavel.
> >
> > Please, be aware of IGNITE-6055 [1]
> >
> > I'm edit thin protocol in that ticket.
>
se' in Spark. If there are multiple
> > clients, you would create multiple sessions and multiple catalogs.
> >
> > Makes sense?
> >
> > -Val
> >
> > On Fri, Aug 24, 2018 at 12:33 AM Nikolay Izhikov
> > wrote:
> >
> > > Hello, Valentin.
&
Hello, Pavel.
IGNITE-6055 merged to master.
Please, update your code accordingly.
You can take edits in CPP, .Net, NodeJS thin clients as example.
В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> PR is fully ready.
>
> I'm waiting final approve from Vladimir Ozerov.
&
Hello, Igniters.
I think we should discuss the release schedule.
Current dates are following:
* Code Freeze: September 30, 2018
* Voting Date: October 1, 2018
* Release Date: October 15, 2018
We discussed it privately with Vladimir Ozerov.
Is seems better to reschedule
Hell, Yakov
I'm ok with your proposal.
* Scope freeze - September 17 - We should have a full list of tickets
for 2.7 here.
* Code freeze - October 01 - We should merge all 2.7 tickets to master
here.
* Vote on RC1 - October 11.
* Vote on release - October 15.
В
Hello, Dmitry.
I tried to build your lib locally and it failed.
Error message and pip version are below.
Seems, we have to fix developer instructions.
Do we need specific version of pip or something?
I tried to use default versions.
I using Ubuntu Linux.
dragon:~/src/ignite/modules/platforms/py
s are you already have a
> recent Python 3 installed. Try `pip3`.
>
> On 9/3/18 4:25 PM, Nikolay Izhikov wrote:
> > Hello, Dmitry.
> >
> > I tried to build your lib locally and it failed.
> > Error message and pip version are below.
> >
> > Seems, w
Hello, Sergey.
If some resources are not closed after usage it certainly a bug.
Can you create a ticket and attach a simplest reproducer for desribed issue?
В Вт, 04/09/2018 в 17:44 +0300, Sergey Antonov пишет:
> Hello, Igniters!
>
> I found bug in org.apache
> .ignite.internal.processors.cache
> > > > I'll go ahead and make the changes to represent the schema name as the
> > > > database name for the purposes of the Spark catalog.
> > > >
> > > > If anyone knows of an existing way to list all available schemata
> >
>
Hello, Denis.
Thanks for providing reproducers for bugs!
I taked a look at your project and be able to reproduce some of errors.
I will create a ticket and start investigation in a next few days.
В Вт, 11/09/2018 в 12:28 +0300, Dmitriy Pavlov пишет:
> Hi Denis,
>
> Thank you for bringing this h
released in 2.7, right?
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89067473
>
> Could you also list what needs to be done at Phase 2 and how much time it
> might take.
>
> --
> Denis
>
> On Thu, Aug 9, 2018 at 8:48 AM Nikolay Izhikov wrote:
>
g into your request? As I understand the plan is
> > to get TDE Phase 1 released in 2.7, right?
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89067473
> >
> > Could you also list what needs to be done at Phase 2 and how much time it
> > might take.
curious what won't be
> supported in 2.7.
>
> --
> Denis
>
> On Tue, Sep 11, 2018 at 4:29 PM Nikolay Izhikov wrote:
>
> > > As I understand the plan is to get TDE Phase 1 released in 2.7, right?
> >
> > Yes. We will release TDE in 2.7
> >
&
Hello, Stuart.
Do you need any assistance with this task from me or other community member?
В Вт, 04/09/2018 в 19:03 +0300, Nikolay Izhikov пишет:
> Hello, Stuart.
>
> Sorry for the silence.
>
> I was swamped the last couple of days.
>
> I think you can go forward an
Hello, Dmitrii.
Can you give a link to detailed description of this feature?
Actually, I wonder if someone except bit developers know how to use it
чт, 13 сент. 2018 г., 22:46 Dmitrii Ryabov :
> Hello, Igniters!
>
> We've improved tests analysis in the TeamCity Helper.
>
> Now, when you view PR
Hello, Denis.
I've created a tests for Ignite codebase and attached it to the ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9593
В Вт, 11/09/2018 в 13:34 +0300, Nikolay Izhikov пишет:
> Hello, Denis.
>
> Thanks for providing reproducers for bugs!
>
> I
Igniters will attend I send an invitation to
> the beginning of next week.
>
> I hope in the nearest time we will have a few more features to speak about.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 13 сент. 2018 г. в 22:58, Nikolay Izhikov :
>
> > Hello, Dmitrii.
2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com> wrote:
> > >
> > >
> > > Hello!
> > >
> > > IGNITE-9408 <https://issues.apache.org/jira/browse/IGNITE-9408> looks
> > > good to me and may be
nch?
>
> Fabric removal related TC modifications are not ready yet, and code is not in
> master.
>
>
>
> > On 18 Sep 2018, at 13:07, Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
> >
> > I want to start and release procedures and make an RC1
loading the release.
> >
> > D.
> >
> > On Tue, Sep 18, 2018 at 1:18 PM Petr Ivanov wrote:
> >
> > > Ok.
> > >
> > > In case of TC questions — ask me.
> > >
> > >
> > >
> > > > On 18 S
> > >
> > > > Hi Paul.
> > > >
> > > > There are 2 PRs linked to that ticket. Who is reviewing your changes?
> > > >
> > > > Branch for 2.7 is still master, so if your changes are reviewed and
> > > > accepted soon it w
Hello, Igniters.
Currently, we are working on release scope for Apache Ignite 2.7
We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release.
If I understand correctly, the plan is following - We should have PR that
is ready for review at the end of September.
This deadline is very
Hello, Igniters.
I've started to write Wiki article for a future Release Managers.
Since release process doesn't described anywhere public I do it while releasing
2.7:
https://cwiki.apache.org/confluence/display/IGNITE/Release+manager+Notes
Any feedback is strongly appreciated.
I've tried to w
gnite-2.7 branches.
> On Wed, Sep 19, 2018 at 12:18 PM Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
> >
> > Vova, thank you for pointing this out.
> >
> > I ask all community members to iterate over assigned tickets.
> > Please, move your tickets to
pareVote&tab=artifacts#!hkm8d5gqy4ii
>
>
> > On 20 Sep 2018, at 17:39, Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
> >
> > I've started to write Wiki article for a future Release Managers.
> > Since release process doesn't describ
Hello, Denis
> - Nikolay Izhikov: Data Frames.
I'm waiting for Valentin Kulichenko review.
If and when further comments for DataFrame pull request appears I will
fix them immediately.
В Вт, 19/12/2017 в 12:07 -0800, Denis Magda пишет:
> Igniters,
>
> It’s time to sync up o
Hello, Dmitry.
I think it a great idea.
Do we a feature to list all running ComputeTasks?
I, personally, think we have to implement possibility to track all
user-provided tasks - CacheListener, ContinuousQuery, ComputeTasks,
etc.
В Чт, 21/12/2017 в 10:13 +0300, Dmitry Karachentsev пишет:
> Cros
>
> Thanks!
> -Dmitry
>
> 21.12.2017 13:18, Nikolay Izhikov пишет:
> > Hello, Dmitry.
> >
> > I think it a great idea.
> >
> > Do we a feature to list all running ComputeTasks?
> >
> > I, personally, think we have to implement possibility
ata frame into Ignite via
> DataFrameWrite API [3].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3084
> [2] https://issues.apache.org/jira/browse/IGNITE-7077
> [3] https://issues.apache.org/jira/browse/IGNITE-7337
>
> Nikolay Izhikov, thanks for the contribution and for all the hard
> work!
>
> -Val
Hello, guys.
Currently `getPreferredLocations` implemented in
`IgniteRDD -> IgniteAbstractRDD`.
But DataFrame implementation uses
`IgniteSQLDataFrameRDD -> IgniteSqlRDD -> IgniteAbstractRDD`
Where `->` is extension.
So, for now, getPreferredLocation doesn't implemented for a
IgniteDataFrame.
; [1] https://issues.apache.org/jira/browse/IGNITE-3084
> > [2] https://issues.apache.org/jira/browse/IGNITE-7077
> > [3] https://issues.apache.org/jira/browse/IGNITE-7337
> >
> > Nikolay Izhikov, thanks for the contribution and for all the hard
> > work!
> >
> > -Val
>
>
+1 from me.
В Ср, 10/01/2018 в 05:24 -0700, vveider пишет:
> Hi, Igniters!
>
>
> While working on Java 9 support adaptation, came to a problem with
> scala
> 2.10 and corresponding modules (scala-2.10, spark-2.10 and
> visor-console-2.10) which will not compile under Java 9. As I see
> here [1]
Hello, guys.
I have done prototype of implementation of optimization query from Spark to
Ignite [1].
Please, take a look at PR [2].
But still there are some issues I want to clarify with community:
* Can I know scale and precision of DECIMAL column?
Example - [3]
* Ignite have
in another thread?
[1]
https://docs.microsoft.com/ru-ru/sql/t-sql/functions/cast-and-convert-transact-sql
В Пт, 19/01/2018 в 14:18 -0800, Valentin Kulichenko пишет:
> Hi Nikolay,
>
> I will review this sometime next week.
>
> -Val
>
> On Fri, Jan 19, 2018 at 2:4
Serge, thank you!
Vladimir, guys, can you take a look at another questions:
* Can I know scale and precision of DECIMAL column?
Example - [3]
* Ignite have some limitation for a *distributed* join. For example, we can
execute join only for indexed columns. Example - [4].
*
Hello, Vladimir.
Thank you for an answer.
> Do you mean whether it is possible to read it from table metadata?
Yes, you are right.
I want to read scale and precision of DECIMAL column from table metadata.
> This will be fixed at some point in future, but I do not have any dates at
> the mome
Hello, guys.
I wonder what is best way to delete all rows from table?
Other RDBMS offer command like `TRUNCATE TABLE` or similar.
Is it would be faster if user execute `DROP TABLE XXX`, `CREATE TABLE XXX`
instead of `DELETE FROM XXX`?
Hello, guys.
I've finish implementation of IGNITE-7337 [1]
Support of saving data frame to Ignite.
Please, review.
Valentin, I think it would be better to review this task prior IGNITE-7077
(query optimization).
Because, this issue is relatively smaller and easier to review.
And, from my point
Hello, guys.
I working on support of saving Spark DataFrame to Ignite [1].
I want to execute "DROP TABLE XXX" query.
To execute some SQL query in regulary way one need some cache.
That cache has to differs from table cache to execute "DROP TABLE" successfully.
I founded 3 different ways to execu
Hello, Igniters.
Improvement of Continuous Query public API are ready for merge.
AFAIK Anton Vinogradov and Yakov Zhdanov are happy with proposed API. [1]
With this improvement we can transform entry on the server node before sending
it to the listener to reduce network utilization.
Example of
Hello, Igniters.
Please, consider including IGNITE-7337 - Spark Data Frames: support saving a
data frame in Ignite [1] in the 2.4 release.
It seems we can merge it into the master in a day or few.
[1] https://issues.apache.org/jira/browse/IGNITE-7337
В Ср, 07/02/2018 в 08:35 -0800, Denis Magda
Anton,
The merge is done!
Thank you, very much.
Your help can't be overestimated.
В Чт, 08/02/2018 в 12:38 +0300, Anton Vinogradov пишет:
> Looks like no one have objections.
>
> Nikolay,
> Let's merge.
>
> On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov w
Hello, Igniters.
Good news.
IGNITE-7337 [1](Spark Data Frames: support saving a data frame in Ignite) are
merged to master.
For now we can both - read from and write to Ignite SQL table with Data Frame
API.
Big thanks to Valentin Kulichenko for a quick review.
So it seems we can include this f
n be done faster though.
>
>
> Alexey Goncharuk, Dmitriy Pavlov, any ideas?
>
> D.
>
> On Wed, Feb 7, 2018 at 9:07 AM, Nikolay Izhikov wrote:
>
> > Hello, Igniters.
> >
> > Please, consider including IGNITE-7337 - Spark Data Frames: support saving
&
ng to 2.4 except blockers is not possible at this phase of
> release process.
>
> Hope, 2.5, with your changes, will be released soon :)
>
> On Fri, Feb 9, 2018 at 7:19 AM, Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > Good news.
> >
> &
Hello, Dmitriy.
Data Frame Read feature is documented in
https://issues.apache.org/jira/browse/IGNITE-7345
AFAIK page isn't published yet.
I will document Data Frame Save feature in a few days.
There is a ticket for it - https://issues.apache.org/jira/browse/IGNITE-7655
В Вс, 11/02/2018 в 15:
Hello, Igniters.
I've fix some relatively small issue(100 loc) IGNITE-6005 [1], PR [2]
The fix in DataStructuresProcessor.java
As far as I can see from git log Ilya Lantukh maintains this piece of code.
Ilya, can you please take a look at the fix?
[1] https://issues.apache.org/jira/browse/IGNIT
Hello, Igniters.
We have some requests from users [1] to have ability to get list of all running
continuous queries.
I propose to implement such ability.
To implement it we have to extend our JMX beans to provide the following
information:
* List of continuous queries for cache:
* local
Hello, Alexey.
Could you please, write little more about your implementation
1. Design of implementation.
2. Advantages of you implementation in compare with other ways?
3. Transactions performance penalties/improvements?
В Вт, 13/02/2018 в 14:17 +, ALEKSEY KUZNETSOV пишет:
> Hi, Igniters
; component, please feel free to create it on your own. As
> far as testing of joins, I think it makes sense to start working on it when
> we finish ANSI compliance testing which is already in progress.
>
> On Wed, Jan 24, 2018 at 12:27 PM, Nikolay Izhikov
> wrote:
> &
te it on your own.
> > As far as testing of joins, I think it makes sense to start working on it
> > when we finish ANSI compliance testing which is already in progress.
> >
> > On Wed, Jan 24, 2018 at 12:27 PM, Nikolay Izhikov
> > wrote:
> > > Hello, Vl
> find one under "sql" component, please feel free to create it on your own.
> > As far as testing of joins, I think it makes sense to start working on it
> > when we finish ANSI compliance testing which is already in progress.
> >
> > On Wed, Jan 24, 201
dex should not cause query to
> fail. What is the exception?
>
> -Val
>
> On Tue, Feb 13, 2018 at 8:07 AM, Nikolay Izhikov wrote:
> > Hello, Valentin.
> >
> > > When you're talking about join optimization, what exactly are you
> > > ref
s is because you enabled non-collocated joins. I was not
> aware of this limitation though, do we have this documented somewhere?
>
> -Val
>
> On Tue, Feb 13, 2018 at 8:21 AM, Nikolay Izhikov
> wrote:
>
> > Val,
> >
> > Source code check: https://github.com/a
ation timestamp (?)
> >* start timestamp (?)
> >
> > * List of running jobs for node:
> >* node ID task started from.
> >* task class name.
> >* other job parameters.
> >* creation timestamp (?)
> >* start timestamp (?)
&
lay, how about regular SQL queries?
>
> On Tue, Feb 13, 2018 at 6:31 AM, Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > We have some requests from users [1] to have ability to get list of all
> > running continuous queries.
> > I propose to i
Hello, Dmitry.
If other community member are also iterested in that kind of information I can
try to do the talk.
В Ср, 14/02/2018 в 10:49 +, Dmitry Pavlov пишет:
> Hi Nikolay,
>
> I've notices there are a number of very lively discussions on dev list about
> SparkDataFrames. But I, for ex
+1
В Чт, 15/02/2018 в 17:27 +0300, Vladimir Ozerov пишет:
> Igniters,
>
> AI 2.4 release was shifted a bit and over this time we implemented two
> important SQL features:
> 1) COPY command for fast file upload to the cluster [1]
> 2) Streaming mode for thin driver [2]
>
> Both commands are very
from my PR until:
> >
> > 1. We create documentation for all join limitations.
> > 2. Create the way to check is certain join satisfy current limitations.
> >
> > [1]
> > http://apache-ignite-developers.2346864.n4.nabble.com/SparkDataFrame-Query-Optimizati
Hello, Igniters.
There is an issue [1] with very small patch - 4 LOC.
State is Patch Available.
This part of code was introduced be me in [2].
I reviewed patch and want to merge it.
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-7409
[2] https://issues.apache.org/jira/browse/
Hello, Igniters.
I'm working on issue [1].
Team City doesn't collect info about scalatest execution because of wrong
pom.xml
I'm fixed it in PR [3]
It happens there is a 2 broken tests written in Scala - [4]
1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
saveValues
" by Denis Magda, which has been presented some times ago.
> > >
> > > On Wed, Feb 14, 2018 at 5:03 PM, Dmitriy Setrakyan
> > > wrote:
> > > > I am definitely interested. Great idea!
> > > >
> > > > On Wed, Feb 14, 2018 at 4
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I'm working on issue [1].
> >
> > Team City doesn't collect info about scalatest execution because of wrong
> > pom.xml
>
Hello, Dmitriy.
Seems, that I haven't suffictient access to do test mute.
Can you give me access?
Or please, mute it.
В Пт, 16/02/2018 в 12:03 +, Dmitry Pavlov пишет:
> I think you should be able to mute any test. If not, please write to me.
>
> пт, 16 февр. 2018 г. в 15:02, N
Hello, Dmitriy
Seems like apache mail doesn't allow attachments.
Can you enlist failing tests in github gist or some similar service?
В Пн, 19/02/2018 в 14:18 +, Dmitry Pavlov пишет:
> Hi Igniters,
>
> I've done experiment on past two weekends to find out which test are
> currently failing
Hello, Igniters.
While working on IGNITE-7727 I found strange behavior of IgniteDataStreamer:
If we have IgniteUuid as an indexed type update silently brokes on a server
node.
Client doesn't have any notification about fails.
All calls of `addData`, `close`, etc. succeed on a client side but fai
Hello, Dmitriy.
Sorry, I thought I did it by myself.
Thank you, anyway.
В Вт, 20/02/2018 в 15:24 +, Dmitry Pavlov пишет:
> Hi Nikolay,
>
> A number of TC tests began to fail with link to
> https://issues.apache.org/jira/browse/IGNITE-7727
>
> I've muted all tests, which I found. Please umut
ion should be propagated to that
> future. Do you not see it there?
>
> D.
>
> On Mon, Feb 19, 2018 at 1:00 PM, Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > While working on IGNITE-7727 I found strange behavior of
> > IgniteDataStreamer:
&g
is fix causes 100% timeout in Data Structures suite and wastes
> > agents for a long time.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 12 февр. 2018 г. в 17:54, Ilya Lantukh :
> >
> > > Hi Nikolay,
> > >
> > > Thanks for contrib
e.html?buildTypeId=IgniteTests24Java8_RunAll&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F2773%2Fhead
> >
> > So, Nikolay, I suggest to start RunAll in this suite group.
> >
> > I can check results later in compare with master.
> >
> > ср, 21 фе
estSemaphoreSingleNodeFailure.
> And it can be failed with link to
> https://issues.apache.org/jira/browse/IGNITE-5975
>
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 февр. 2018 г. в 10:07, Nikolay Izhikov :
>
> > Andrey,
> >
> > I made TC run.
> >
run.
>
> Please see investigations assigned to you. What can we change to avoid
> these tests to be included into run other suites?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I'
> Is it possible IgniteRDDSpec.IgniteRDD became unit tests, which is started
> with code compile?
>
> This can be reason these tests appeared in suites which is not related to
> IgniteRDD, such as Scala Examples.
>
> чт, 22 февр. 2018 г. в 13:20, Nikolay Izhikov :
>
&
> Looks like second attempt is successful for such case.
>
> On Wed, Feb 21, 2018 at 1:36 PM, Dmitriy Setrakyan
> wrote:
>
> > On Wed, Feb 21, 2018 at 12:10 AM, Nikolay Izhikov
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > > Does
che.org/viewLog.html?buildId=1106598&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteOSGi
> (other
> change PR run). I'm not sure that OSGI build configuration is appropriate
> suite to run these tests.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 февр.
y for specific team city plans.
I.e "Ignite RDD" and "Ignite RDD spark 2_10".
Thoughts?
[1] https://github.com/apache/ignite/pull/3570
В Пн, 26/02/2018 в 14:35 +0300, Nikolay Izhikov пишет:
> Hello, Dmitriy.
>
> I'm investigate issue and share results later to
Hello, Alexey, what do you think?
Let's fix this issue!
В Пн, 26/02/2018 в 16:29 +, Dmitry Pavlov пишет:
> I agree.
>
> Alexey K, what do you think?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 26 февр. 2018 г. в 19:17, Nikolay Izhikov :
>
> > Hello, Dm
Hello, Igniters.
I've created several examples for a Ignite DataFrame.
Currently, they are not tested on Team City.
As far as I can understand, they should be checked in "Ignite Scalar Examples
[Scala]".
But it marked as obsolete [1]
Please, give me advice:
1. Should we test Ignite DataFrame e
Hello, Alexey.
Great mail, by the way.
I think, it would be great to have this feature in Ignite.
> I haven't removed thread id completely from code.
Can we remove thread id completely from code?
Can you estimate how much effort do we need?
As far as I can see from parent task [1] we need some
Hello,
If there are no any objections I merge the fix tomorrow.
https://github.com/apache/ignite/pull/3570
В Вт, 27/02/2018 в 13:27 +0300, Nikolay Izhikov пишет:
> Hello, Alexey, what do you think?
>
> Let's fix this issue!
>
> В Пн, 26/02/2018 в 16:29 +, Dmitry Pavlo
figuration for
> > ignite-spark module. If anything Spark related is currently in Scalar
> > suite, it should be moved from there.
> >
> > -Val
> >
> > On Tue, Feb 27, 2018 at 3:03 AM, Nikolay Izhikov
> > wrote:
> >
> > > Hello, I
ctly calculated for suspended transactions. You can find them in
> `GridCacheTransactionalAbstractMetricsSelfTest`.
>
> Please, feel free to propose additional tests for the ticket.
>
>
> вт, 27 февр. 2018 г. в 17:27, Nikolay Izhikov :
>
> > Hello, Alexey.
> >
&g
Hello, Igniters.
We have `flatten-maven-plugin` in `parent/pom.xml` [1]
As far as I can understand it minimize pom.xml before it installed in
repository.
It introduce some strange behavior in modules:
I must to enlist all test dependencies in my module to get tests work.
Otherwise tests fails w
spark/pom.xml#L144
В Чт, 01/03/2018 в 11:49 +0300, Petr Ivanov пишет:
> Nikolay,
>
>
> Can you describe your problem and desired behaviour more thoroughly, please?
>
>
>
> > On 28 Feb 2018, at 21:16, Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
&g
801 - 900 of 1145 matches
Mail list logo
