What we will do for that? I think, we can start to write requirements and flows.
On 2020/03/05 20:19:38, Julian Jaffe wrote:
> Yeah, I think the primary objective here is a standalone writer from Spark
> to Druid.
>
> On Thu, Mar 5, 2020 at 11:43 AM itai yaffe wrote:
>
> > Thanks Julian!
> >
We also have a use case of reading from Spark. However we are using HDFS (on
prem solution) and not S3. While write would also be needed, our first
requirement is really to query the data from Spark. We ingest via Kafka today
into Druid.
- Rajiv
On 3/5/20, 11:43 AM, "itai yaffe" wrote:
As part of the requirements please include querying / reading from Spark as
well. This is a high priority for us.
- Rajiv
On 3/10/20, 1:26 AM, "Oguzhan Mangir" wrote:
What we will do for that? I think, we can start to write requirements and
flows.
On 2020/03/05 20:19:38, Julian Jaff
The primary bugs are logged as https://github.com/apache/druid/issues/7957
and https://github.com/apache/druid/issues/7904.
On Mon, Mar 9, 2020 at 5:47 PM Julian Hyde wrote:
> Reading the blog post, I was sorry to hear that "performance bottlenecks
> in the SQL parser” prevented you from making
