Vladimir Ozerov created IGNITE-11317:
Summary: Document that SQL DML statements (UPDATE/MERGE) cannot
update key fields
Key: IGNITE-11317
URL: https://issues.apache.org/jira/browse/IGNITE-11317
Pr
Ilya Borisov created IGNITE-11318:
-
Summary: Web console: add viewport meta tag
Key: IGNITE-11318
URL: https://issues.apache.org/jira/browse/IGNITE-11318
Project: Ignite
Issue Type: Improveme
Ilya Suntsov created IGNITE-11319:
-
Summary: ignitevisorcmd can't handle incorrect !q parameter
Key: IGNITE-11319
URL: https://issues.apache.org/jira/browse/IGNITE-11319
Project: Ignite
Issue
Sounds good, I agree with naming and marking *addCacheConfiguration* method
as deprecated with replacing on *addCacheConfigurationTemplate*.
Stanislav, could you please look at this?
Thank you,
Sergey
чт, 14 февр. 2019 г. в 01:49, Eduard Shangareev :
> CacheConfiguration cfg = ignite.cacheConfi
Hello, Ivan.
> Requirements for a prototype code are not the same as for a patch ready
to merge
True.
> I do not see much need in writing good javadocs for prototype.
We, as a community, can't force you to do it.
> Why should I stub it to be able run any build on TC?
Should the community spen
I'd recommend move the IgniteReproducingSuite to separate module to be
able use it for all modules.
For example, at the moment, we are not able use the suite to run tests
from 'indexing' module because of lack dependency.
On Thu, Feb 14, 2019 at 10:38 AM Павлухин Иван wrote:
>
> Ed,
>
> Thank yo
Nikolay,
> Should the community spend TC resources for prototype?
Why not? I think it is not bad idea to run all tests against some
changes into core classes. If I have a clever idea which is easy to
test drive I can do couple of prototype-test iterations. If tests
shows me that everything is bad
Hello!
What about existing convention of using asterisk to mark templates? How
does it integerate with this one?
Regards,
--
Ilya Kasnacheev
чт, 14 февр. 2019 г. в 13:04, Sergey Moldachev :
> Sounds good, I agree with naming and marking *addCacheConfiguration* method
> as deprecated with repl
Maksim,
I tried configuration with quite console and unlimited log file on my
machine. Naively configured in log4j-test.xml it works not so fine in
development environment because log file is appended by each test
execution. Console redirection works better in development
environment. Should we ha
Ivan,
> Could you please outline the benefits you see of failing compilation and
skipping tests execution if inspections detect a problem?
All community members are forced to follow code style.
It's harder to achieve it with dedicated suite.
чт, 14 февр. 2019 г. в 15:21, Павлухин Иван :
> Niko
Alexander Lapin created IGNITE-11320:
Summary: JDBC Thin: add support for individual reconnect in case
of best effort affinity mode.
Key: IGNITE-11320
URL: https://issues.apache.org/jira/browse/IGNITE-11320
Alexander Lapin created IGNITE-11321:
Summary: JDBC Thin: implement nodes multi version support in case
of best effort affinity mode.
Key: IGNITE-11321
URL: https://issues.apache.org/jira/browse/IGNITE-11321
ARomantsov created IGNITE-11322:
---
Summary: [USABILITY] Extend Node FAILED message by add
consistentId if it exist
Key: IGNITE-11322
URL: https://issues.apache.org/jira/browse/IGNITE-11322
Project: Ignit
Nikolay,
> All community members are forced to follow code style. It's harder to achieve
> it with dedicated suite.
Why it is easier to follow code style with use of maven checkstyle
plugin? Is it integrated into IDEA out of box? As I got it additional
IDEA plugin is needed as well. Who will enfo
Sergey, Ed,
On method naming/deprecation/etc.
I would actually like the new method to work for both templates and regular
caches.
For templates it would return a copy of the template.
For existing caches it would return a copy of the cache configuration.
In other words, it would be a shortcut for
Guys, I've updated the IEP page [1] once again.
Please, pay attention to sections Cache affinity mapping acquiring
(4.a, format of Cache Partitions Request) and Changes to cache
operations with single key (3 and 4, algorithm).
Long story short, I've decided to add some additional data to Cache
Pa
Ivan Bessonov created IGNITE-11323:
--
Summary: Reduce boilerplate "System.setProperty" code in tests
Key: IGNITE-11323
URL: https://issues.apache.org/jira/browse/IGNITE-11323
Project: Ignite
Hello Igniters,
I'd like to discuss the way we treat system properties in our test codebase.
It's a common pattern where we set system property in "beforeTestsStarted"
and clear it in "afterTestsStopped". Purest example that I've found is class
"RedisProtocolGetAllAsArrayTest".
There are similar
I find it absolutely positive and modern approach and good contribution.
Count on my support if you will need any assistance with applying this
patch.
чт, 14 февр. 2019 г. в 18:53, Ivan Bessonov :
> Hello Igniters,
>
> I'd like to discuss the way we treat system properties in our test
> codebase.
Greg created IGNITE-11324:
-
Summary: Getting Started Doc openweather API has changed
Key: IGNITE-11324
URL: https://issues.apache.org/jira/browse/IGNITE-11324
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-11325:
Summary: SQL: Single place to start missing caches
(H2Utils.checkAndStartNotStartedCache)
Key: IGNITE-11325
URL: https://issues.apache.org/jira/browse/IGNITE-11325
Dmitry,
Thanks for looking into this. I think that something went wrong with our
release procedure and we forgot to include the "examples" folder in Ignite
binary package. Sergey K. is checking the release procedures.
-
Denis
On Tue, Feb 12, 2019 at 7:28 PM Dmitry Melnichuk <
dmitry.melnic...@
Vladimir Ozerov created IGNITE-11326:
Summary: SQL: Common parsing logic
Key: IGNITE-11326
URL: https://issues.apache.org/jira/browse/IGNITE-11326
Project: Ignite
Issue Type: Task
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Alexander Kalinin created IGNITE-11327:
--
Summary: Console error with progress line component
Key: IGNITE-11327
URL: https://issues.apache.org/jira/browse/IGNITE-11327
Project: Ignite
Iss
25 matches
Mail list logo
