Thanks. I will post my further questions in drill list.
Rahul
On Mon, Apr 25, 2016 at 5:25 AM, Julian Hyde wrote:
> I think this thread should be in the Drill list. Path names in tables is
> not supported by Calcite.
>
> Julian
>
>
> > On Apr 24, 2016, at 7:42 AM, Ted Dunning wrote:
> >
> > I
You may have noticed that JIRA is only allowing project contributors and
committers to log JIRA cases. Apache infrastructure have imposed this temporary
measure in response to a spam attack across all projects.
That said, we want all legitimate community members to be able to log JIRA
cases, no
I think this thread should be in the Drill list. Path names in tables is not
supported by Calcite.
Julian
> On Apr 24, 2016, at 7:42 AM, Ted Dunning wrote:
>
> I was suggesting a single workspace that is sensitive to the content of a
> property that could be set according to user id.
>
>
>
Julian Hyde created CALCITE-1213:
Summary: Changing AvaticaDatabaseMetaData from class to interface
breaks compatability
Key: CALCITE-1213
URL: https://issues.apache.org/jira/browse/CALCITE-1213
Proje
Resending. Sent earlier mail to 'incubator' mailing list by mistake. Sorry
about that.
On Sun, Apr 24, 2016 at 8:27 PM, Amogh Margoor wrote:
> Hi,
> In Quark, we have tried to optimize join queries using auto detection of
> materialised views. For instance, when we have materialised view of tab
Hi,
In Quark, we have tried to optimize join queries using auto detection of
materialised views. For instance, when we have materialised view of table
'X' named 'X_part' defined by query: " select * from X where X.a >
'2016-01-01' " then we expect following query to be optimised by 'X_part':
sele
I was suggesting a single workspace that is sensitive to the content of a
property that could be set according to user id.
On Sun, Apr 24, 2016 at 11:57 AM, Rahul Raj wrote:
> One workspace per user might be difficult to maintain with the increasing
> number of users.
>
> We are evaluating the
One workspace per user might be difficult to maintain with the increasing
number of users.
We are evaluating the possibility of hundreds of users(and more) connecting
and executing queries on a single workspace. The users will be maintained
by a web application and the queries will be modified bas
Have you looked at what Drill does in this way?
In particular, it has workspaces which could plausibly look at environment
variables to introduce a home directory path.
In fact, is there a strong reason not to use Drill for this?
On Sun, Apr 24, 2016 at 3:47 AM, Rahul Raj wrote:
> We are build
