drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chunhui Shi <c...@maprtech.com>
Subject Re: [GitHub] drill issue #507: DRILL-4690: CORS in REST API
Date Wed, 08 Jun 2016 18:25:55 GMT
I think to avoid that size increase is to revert back to the previous
change which implemented the CORS manually and did not introduce this extra
jar file. If our goal is to eat only one egg we don't need to buy a hen.

On Mon, Jun 6, 2016 at 2:36 PM, sudheeshkatkam <git@git.apache.org> wrote:

> Github user sudheeshkatkam commented on the issue:
>     https://github.com/apache/drill/pull/507
>     I am not familiar with CORS. One question: why is this enabled by
> default?
>     Also, there is a discussion about not increasing the size of the
> jdbc-all jar (subject: _drill-jdbc-all-1.7.0-SNAPSHOT.jar max size_). Any
> way to avoid that change?
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message