Ivan,
Good catch.
1. Let's remove this label at all. Neither Spark [1] nor Cassandra [2] has
it and their docs look much better.
2. Agree, time to change the year in the copyright.
3. Still, something is wrong with our font size. Just compare to [1] and
[2] to see the difference. Can we reuse
Hi Denis,
Info about Python, PHP, Node.JS thin clients:
The clients itself do not contain any cryptographic code but use the
features provided by the underlying platforms.
Python client uses Python's SSL lib [1] which is a wrapper over OpenSSL [2].
Python 2.7 and Python 3.4 require OpenSSL
Igniters,
Regardless of the fact that Ignite is an open source software, ASF as an
entity based in the U.S. has to comply with certain exporting regulations
[1].
Dmitry Pavlov and I are working on adding Ignite to the table [2] of
projects allowed for export and might need the assistance of some
+1 for including checkstyl to "Build Apache Ignite".
В Ср, 12/06/2019 в 21:29 +0300, Павлухин Иван пишет:
> Maxim,
>
> Options 1 and 3 sounds fine to me. And taking into account current
> state I tend to think that option 1 is even better.
>
> вт, 11 июн. 2019 г. в 14:19, Maxim Muzafarov :
> >
I went through a couple of pages and layout looks good.
A couple of aside notes:
1. There is a label "Ignite - In-Memory Database and Caching
Platform". Do we need that label at all? Can we replace it with a link
having text "Ignite" and referring to ignite.apache.org?
2. The copyright is out of
Denis,
Minor changes to your suggestion:
*"ERROR: Type 'Person' has a different/incorrect type
for field 'salary'. Expected 'double' but 'string' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required."*
===
Garrett Alley
Maxim,
Options 1 and 3 sounds fine to me. And taking into account current
state I tend to think that option 1 is even better.
вт, 11 июн. 2019 г. в 14:19, Maxim Muzafarov :
>
> Dmitry,
>
> Thank you.
> Sure, I'll not change anything on TC without discussion with all the
> community.
>
> On Tue,
Alex, Garrett,
How about this error message?
That's what we have know: *ERROR: Binary type has different field types
[typeName=Person, fieldName=salary, fieldTypeName1=double,
fieldTypeName2=String]*
That's how I would change it: *"Type 'Person' has different/incorrect type
for field 'salary'.
Igniters,
I'd like us to move on and finish our conversation on the IGFS [1] and
Hadoop Accelerator [2] support.
To my knowledge, there is no single committer who maintains the
integrations; they are no longer tested and, even more, the community
stopped providing the binaries since Ignite 2.6.0
Such OutOfMemory protection will be available in next Ignite releases. In
particular, if a query is about to consume more than X memory than it will
be terminated. Yury, could you please share more details?
-
Denis
On Wed, Jun 12, 2019 at 10:13 AM Shane Duan wrote:
> Thanks, Ilya. Yes, I am
Thanks, Ilya. Yes, I am planning to bump up the heap size in our testing.
Just curious, is it possible to fail the query/request, instead of crash
Ignite instance with a system error (OutOfMemoery)? Will reduce the query
pool size (for JDBC) help?
Regards,
Shane
On Tue, Jun 11, 2019 at 5:56 AM
11 matches
Mail list logo
