Stanilovsky Evgeny created IGNITE-14593:
---
Summary: Calcite. Support not equal expression.
Key: IGNITE-14593
URL: https://issues.apache.org/jira/browse/IGNITE-14593
Project: Ignite
Hi folks,
Did you have a discussion? How did it go? Can someone summarize the results?
-Val
On Mon, Apr 12, 2021 at 2:00 AM Kseniya Romanova
wrote:
> Hi! Scheduled open call for Friday
> https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/277518672/
> Please join to see the zoom link.
Alexey,
These are bad examples and unfortunately, most of the Ignite code doesn't
look self-descriptive.
(Do you feel the difference between @SerializableTransient and
@TransientSerializable?)
To understand the semantic of e.g. 'metricsHistSize' you have to analyze
its usages.
Getter and setter
Agree with Ivan - internal code does not need mandatory Javadoc.
Most of it is meaningless and does not bring any value, just wastes
everyone's time.
Alexey, I think public APIs should always have Javadoc,
even if it is the same thing as the member name, but with spaces -
this will make the
Hi Igniters,
There is meetup next week, where I want to share my knowledge about
Ignite Persistence module. It will be high level overview of the main
components and the main ideas behind the Persistence module. So if you
are a new ignite contributor or you don't feel confident enough in
I personally do not understand why we need mandatory javadoc even in public
modules. I think javadoc is needed only when the code is not
self-descriptive. What value does a javadoc like this bring
Hi Andrey and Igniters,
Sorry if I misread something but I have totally different opinion in
one aspect. In my mind it is much better in practice to follow strict
rules for public API javadocs but not for internals. I would use
static checks for API packages and disable them for internal ones and
Tested signatures, tested hashsums, tested installation on Mac Os X 10.15.7
on python 3.9.4.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Nikolay Izhikov created IGNITE-14592:
Summary: Incapsulate config modification logic into callback
Key: IGNITE-14592
URL: https://issues.apache.org/jira/browse/IGNITE-14592
Project: Ignite
Hi Marius,
Similar build failure issue was discussed in user mailing list.
http://apache-ignite-users.70518.x6.nabble.com/build-failure-for-module-hibernate-5-3-tp33621p33629.html
As suggested in above link, you can add to your settings.xml:
Hi Igniters,
We use JDK Javadoc tool to validate javadocs on TC (Javadoc suite) in
Ignite 2 and now in Ignite 3.
A javadoc tool is designed for javadoc site generation that also performs
some basic checks and markup validation,
but has nothing to do with javadoc styles.
I've found
Also checked the hashcode generation
>> from pyignite import _cutils
>> print(_cutils.hashcode('test'))
>> 3556498
On Mon, Apr 19, 2021 at 11:01 AM Anton Vinogradov wrote:
> Checked the installation from sources.
> +1
>
> On Sat, Apr 17, 2021 at 7:47 PM Ivan Daschinsky
> wrote:
>
>> Another
Andrey Mashenkov created IGNITE-14591:
-
Summary: Add Javadoc rules to maven checkstyle plugin.
Key: IGNITE-14591
URL: https://issues.apache.org/jira/browse/IGNITE-14591
Project: Ignite
Konstantin Orlov created IGNITE-14590:
-
Summary: Calcite engine. Sort out the types/decimal and
types/string directories
Key: IGNITE-14590
URL: https://issues.apache.org/jira/browse/IGNITE-14590
Konstantin Orlov created IGNITE-14589:
-
Summary: Calcite engine. Numerous problem with type Decimal
Key: IGNITE-14589
URL: https://issues.apache.org/jira/browse/IGNITE-14589
Project: Ignite
Thank you, Vishwas
Can you point to the reference in the documentation for this information?
If it is missing (and the info is transmitted via email) then I'll raise a
ticket and add it myself.
Thanks,
Marius Filip
On Mon, Apr 19, 2021 at 3:41 AM Vishwas Bm wrote:
> Hi Marius,
>
> This is
Checked the installation from sources.
+1
On Sat, Apr 17, 2021 at 7:47 PM Ivan Daschinsky
wrote:
> Another reason why whe should host docs on readthedocs.io only is the
> fact,
> that
> pyignite has a separate release cycle. We will release and add more
> features frequently. It's strange to
Aleksey Plekhanov created IGNITE-14588:
--
Summary: Calcite integration: Wrong processing of nested aggregates
Key: IGNITE-14588
URL: https://issues.apache.org/jira/browse/IGNITE-14588
Project:
Rodion created IGNITE-14587:
---
Summary: ServerImpl.resolveCoordinator returns daemon node as
coordinator when daemon node is older then real coordinator
Key: IGNITE-14587
URL:
19 matches
Mail list logo
