[jira] [Created] (CALCITE-1171) Limit N on JdbcSchema pushdown doesn't seem to work

Dan Di Spaltro created CALCITE-1171: --- Summary: Limit N on JdbcSchema pushdown doesn't seem to work Key: CALCITE-1171 URL: https://issues.apache.org/jira/browse/CALCITE-1171 Project: Calcite

Calcite-Master-JDK-1.8 - Build # 40 - Fixed

The Apache Jenkins build system has built Calcite-Master-JDK-1.8 (build #40) Status: Fixed Check console output at https://builds.apache.org/job/Calcite-Master-JDK-1.8/40/ to view the results.

Re: Misconfigured Jenkins slaves for maven deploy

Awesome, thanks for the confirmation. I had tried something to exclude them already, but I'll switch to the label you provided (since I'm not sure if mine would even work). Daniel Takamori wrote: Hey Josh, These Rackspace nodes have been giving us a bit of trouble, in the meantime you can cha

Re: Misconfigured Jenkins slaves for maven deploy

Hey Josh, These Rackspace nodes have been giving us a bit of trouble, in the meantime you can change the label to "Ubuntu&&!cloud-slave" to avoid any issues with them. We have a ticket in JIRA to document the issue https://issues.apache.org/jira/browse/INFRA-11543 Cheers, -Pono On Fri, Mar 25, 20

Re: Calcite-Master-JDK-1.8 - Build # 39 - Failure

I sent a note to infra about these "jenkins-test-.*" nodes that seem to be misconfigured. Meanwhile, I tried to update the label expression to restrict these nodes completely when running the build. Apache Jenkins Server wrote: The Apache Jenkins build system has built Calcite-Master-JDK-1.8

Misconfigured Jenkins slaves for maven deploy

Hi -- We've been seeing some failures to deploy snapshot artifacts to Nexus on Calcite builds. These seems to be occurring on a subset of the servers: jenkins-test-601 and jenkins-test-3d4. I'm guessing that the settings.xml/settings-security.xml isn't properly configured on these nodes (nod

Re: Tenanted SQL

So I definitely understand the data side of the target database ("A"), that I am virtualizing. I guess more specific questions would be: * How would I expose only two tables from "A" (they would both include the tenantId field), I'm guess I might override the JdbcSchema using some whitelist. * Sin

Calcite-Master-JDK-1.8 - Build # 39 - Failure

The Apache Jenkins build system has built Calcite-Master-JDK-1.8 (build #39) Status: Failure Check console output at https://builds.apache.org/job/Calcite-Master-JDK-1.8/39/ to view the results.

Re: Tenanted SQL

Maybe you give each table a tenantId column, and give each tenant a view that adds a “WHERE tenantId = XXX”. Thus each tenant only sees its own stuff. It could be a different view for each tenant, or it could be same view with XXX a call to a function that retrieves, say, a variable in the conne

Tenanted SQL

I'd basically like to offer some tables tenanted which, in this case, means filtered by some tenant. How would I do that the right way in Calcite? Obviously the tricky part is during the query execution there's no way to pass extra variables/markers/whatever using JDBC. Which is where I'd like to