Hi Denis, Thanks for the response. spring is indeed Apache 2.0, see
https://github.com/spring-projects/spring-framework/blob/master/src/docs/dist/license.txt
Am I missing something?
On Fri, Dec 21, 2018 at 22:37 Denis Magda wrote:
> Scott, Ilya,
>
> LGPL license is not compliant with Apache
Scott, Ilya,
LGPL license is not compliant with Apache 2.0 and, thus, ASF project can't
include binaries of LGPL libs to ASF releases:
https://www.apache.org/legal/resolved.html#category-x
Spring doesn't belong to ASF. It has its own rules and policies.
--
Denis
On Thu, Dec 20, 2018 at 5:04
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:
Andrew Mashenkov created IGNITE-10794:
-
Summary: MVCC: RemoveAll fails with assertion on unstable topology
Key: IGNITE-10794
URL: https://issues.apache.org/jira/browse/IGNITE-10794
Project: Ignite
Vladimir, thanks for your expert opinion.
I have some thoughts about 5 point.
I tried to find how it works for Oracle and PG:
*PG*: keep by default 1000 (can be configured) statements without and
discard the least-executed statements. Update statistics is asynchronous
process and statistics may
The general problem is a when a node pushes its IP addresses to S3, it has
no way to tell whether one of its IP address will be usable by other
nodes. On the consumer side, we are unable to determine at runtime which
of the addresses will work. So we end up doing discovery using worthless
IP
Aleksey Zinoviev created IGNITE-10792:
-
Summary: [ML] Add seed to test-train filter
Key: IGNITE-10792
URL: https://issues.apache.org/jira/browse/IGNITE-10792
Project: Ignite
Issue Type:
Hi,
Regarding the name, it's not just about being a good name. I would point to
the official AWS documentation [1], [2]. The current ELB does not stand for
just the Classic Load balancer. Based on this documentation, the naming is
good. I agree with your suggestion about extending
Alexey Platonov created IGNITE-10793:
Summary: [ML] Create comprehensive example for dataset generators
Key: IGNITE-10793
URL: https://issues.apache.org/jira/browse/IGNITE-10793
Project: Ignite
David Harvey created IGNITE-10791:
-
Summary: Avoid unusable network during discovery
Key: IGNITE-10791
URL: https://issues.apache.org/jira/browse/IGNITE-10791
Project: Ignite
Issue Type:
Sergey Antonov created IGNITE-10790:
---
Summary: Control.sh add ability to check tx on deadlock
Key: IGNITE-10790
URL: https://issues.apache.org/jira/browse/IGNITE-10790
Project: Ignite
Sergey Antonov created IGNITE-10789:
---
Summary: CacheInterceptor on server node get BinaryObject if put
was invoked by ClientCache.
Key: IGNITE-10789
URL: https://issues.apache.org/jira/browse/IGNITE-10789
Roman Kondakov created IGNITE-10788:
---
Summary: MVCC: Get operation may hang in some cases
Key: IGNITE-10788
URL: https://issues.apache.org/jira/browse/IGNITE-10788
Project: Ignite
Issue
It seems there is bug in latest 2018.2 TeamCity
Bug is filed [1]
[1] https://youtrack.jetbrains.com/issue/TW-58504
> On 19 Dec 2018, at 11:31, Petr Ivanov wrote:
>
> Investigating problem, stand by.
>
>
>> On 18 Dec 2018, at 19:41, Dmitriy Pavlov wrote:
>>
>> Both patches were applied.
Roman Kondakov created IGNITE-10786:
---
Summary: MVCC: Flaky test
IgniteClusterActivateDeactivateTestWithPersistence#testDeactivateDuringEvictionAndRebalance
Key: IGNITE-10786
URL:
Dmitriy Pavlov created IGNITE-10787:
---
Summary: [TC Bot] Setup TC bot profiling on the server using
SJK/stcap and prepare rules for Ignite thread groups
Key: IGNITE-10787
URL:
Roman Kondakov created IGNITE-10785:
---
Summary: MVCC: Grid can hang if transactions is failed to rollback
Key: IGNITE-10785
URL: https://issues.apache.org/jira/browse/IGNITE-10785
Project: Ignite
Vladimir Ozerov created IGNITE-10784:
Summary: SQL: Create a view with list of existing tables
Key: IGNITE-10784
URL: https://issues.apache.org/jira/browse/IGNITE-10784
Project: Ignite
Vladimir Ozerov created IGNITE-10783:
Summary: SQL: Ability to optionally disable partition pruning
Key: IGNITE-10783
URL: https://issues.apache.org/jira/browse/IGNITE-10783
Project: Ignite
Sergey Antonov created IGNITE-10780:
---
Summary: control.sh add ability to get tx state change history
Key: IGNITE-10780
URL: https://issues.apache.org/jira/browse/IGNITE-10780
Project: Ignite
Igniters,
Please, let us know if someone is going to do an additional review?
We should know can we merge the PR since it has been approved by
Nikolay Izhikov and Denis Mekhanikov or we should wait for other
community members.
On Thu, Dec 20, 2018 at 7:52 PM Vyacheslav Daradur wrote:
>
> I
Stepan Pilschikov created IGNITE-10782:
--
Summary: javadoc description for ml.math.exceptions.preprocessing
and ml.selection.scoring.evaluator
Key: IGNITE-10782
URL:
Taras Ledkov created IGNITE-10781:
-
Summary: Add supportion findNext for H2TreeIndex to use H2
optimization for DISTINCT
Key: IGNITE-10781
URL: https://issues.apache.org/jira/browse/IGNITE-10781
Nikolai Kulagin created IGNITE-10779:
Summary: PagesWriteThrottleSmokeTest.testThrottle is flaky
Key: IGNITE-10779
URL: https://issues.apache.org/jira/browse/IGNITE-10779
Project: Ignite
Roman Kondakov created IGNITE-10778:
---
Summary: MVCC: Invoke request may hang sometimes
Key: IGNITE-10778
URL: https://issues.apache.org/jira/browse/IGNITE-10778
Project: Ignite
Issue Type:
Hi,
I'd propose the following approach:
1) Enable history by default. Becuase otherwise users will have to restart
the node to enable it, or we will have to implement dynamic history enable,
which is complex thing. Default value should be relatively small yet
allowing to accommodate typical
Oleg Ignatenko created IGNITE-10776:
---
Summary: migrate from JUnit 3 to 4 config variations test suites
Key: IGNITE-10776
URL: https://issues.apache.org/jira/browse/IGNITE-10776
Project: Ignite
Alexey,
Yes, such property to configuration history size will be added. I think
default value should be 0 and history by default shouldn't be gather at
all, and can be switched on by property in case when it required.
Currently I planned use the same way to evicting old data as for
queryMetrics
Oleg Ignatenko created IGNITE-10775:
---
Summary: migrate from JUnit 3 to 4 test suites of simple dynamic
lists that use addTestIfNeeded API
Key: IGNITE-10775
URL:
Oleg Ignatenko created IGNITE-10777:
---
Summary: cleanup remainders of JUnit4TestAdapter and other JUnit 3
API involving test suites
Key: IGNITE-10777
URL: https://issues.apache.org/jira/browse/IGNITE-10777
Oleg Ignatenko created IGNITE-10774:
---
Summary: migrate test suites that are fixed lists of test classes
from Junit 3 to 4
Key: IGNITE-10774
URL: https://issues.apache.org/jira/browse/IGNITE-10774
Oleg Ignatenko created IGNITE-10773:
---
Summary: migrate examples testsuites from Junit 3 to 4
Key: IGNITE-10773
URL: https://issues.apache.org/jira/browse/IGNITE-10773
Project: Ignite
Issue
32 matches
Mail list logo
