Cross-sending to dev@
Why do we need to append SQL_PUBLIC_ to all table names?
D.
-- Forwarded message --
From: Denis Magda
Date: Sun, Oct 8, 2017 at 7:01 AM
Subject: Re: Why SQL_PUBLIC is appending to Cache name while using JDBC
thin driver
To: "u...@ignite.apache.org"
Hi Au
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/2817
IGNITE-6577
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6577
Alternatively you can review and apply these
Eduard Shangareev created IGNITE-6577:
-
Summary: During start cache we should check temporary file
existence besides lock file
Key: IGNITE-6577
URL: https://issues.apache.org/jira/browse/IGNITE-6577
No more doubts on my side. +1 for Vladimir’s suggestion.
Denis
On Saturday, October 7, 2017, Dmitriy Setrakyan
wrote:
> I now tend to agree with Vladimir. We should always require that some
> address is specified. The help menu should clearly state how to connect to
> a localhost.
>
> D.
>
> On
Hello, Ray.
I think it can be done as a second step.
After DataFrame for a current Spark release would be merged.
Thoughts?
07.10.2017 16:42, Ray пишет:
Hi Nikolay,
Could you also implement the DataFrame support for spark-2.10 module?
There's some legacy spark users still using Spark 1.6, the
