[log4j] Snowflake Appender

[Pawel Urbanowicz]

Hello,

I would like to contribute to log4j by implementing the Snowflake appender
which will use Snowpipe Streaming
.
WDYT about my idea for contribution?

Thanks a lot.
Pawel Urbanowicz

[log4j] Snowflake Appender

[Pawel Urbanowicz]

Hello,

I would like to contribute to log4j by implementing the Snowflake appender
which will use Snowpipe Streaming
.
WDYT about my idea for contribution?

Thanks a lot.
Pawel Urbanowicz

Re: [log4j] Snowflake Appender

[Ralph Goers]

In the past I have proposed that some of the similar components in Log4j be 
moved into their own separate Git repos. I would only be in favor of accepting 
this if that were the case.

Ralph

> On May 11, 2023, at 12:50 PM, Pawel Urbanowicz 
>  wrote:
> 
> Hello,
> 
> I would like to contribute to log4j by implementing the Snowflake appender
> which will use Snowpipe Streaming
> .
> WDYT about my idea for contribution?
> 
> Thanks a lot.
> Pawel Urbanowicz

Re: [log4j] Snowflake Appender

[Gary Gregory]

Pawel,

Your best bet is to provide this code in your own GitHub (or GitLab, or
wherever) repository and publish to Maven Central. This will give you the
freedom of providing features, bug fixes, and releases as you best see fit.

Gary


On Thu, May 11, 2023, 16:01 Pawel Urbanowicz 
wrote:

> Hello,
>
> I would like to contribute to log4j by implementing the Snowflake appender
> which will use Snowpipe Streaming
> <
> https://docs.snowflake.com/en/user-guide/data-load-snowpipe-streaming-overview
> >.
> WDYT about my idea for contribution?
>
> Thanks a lot.
> Pawel Urbanowicz
>

Re: [log4j] Snowflake Appender

[Piotr P. Karwasz]

Hi Paweł,

On Thu, 11 May 2023 at 21:59, Pawel Urbanowicz
 wrote:
> I would like to contribute to log4j by implementing the Snowflake appender
> which will use Snowpipe Streaming
> .
> WDYT about my idea for contribution?

We welcome every contribution to the larger Log4j ecosystem. We
certainly can update our site and provide links to third party
components.

However we are reluctant to **maintain** additional components that
have a very small user base and no committer uses. Of course we
maintain popular components that started as third party components,
but on the condition that the original author joins the team :-).
This is regularly debated on this mailing list, most recently here:

https://lists.apache.org/thread/3b4tn6t7zbhm66cw8yx8h8g26tyy50dj

Since we can not forecast how popular your Snowflake appender will be
I would propose to setup your own Github repository and give it a name
like `logging-log4j-snowflake` (all our repos must start with
`logging-`). If your component gets included into Log4j, we can simply
fork the repo and continue the development there.

If you hit any problems or need a code review, let us know.

Piotr

Re: [log4j] Snowflake Appender

[Gary Gregory]

Just don't use an Apache group ID in your maven coordinates.

Gary

On Thu, May 11, 2023, 19:14 Piotr P. Karwasz 
wrote:

> Hi Paweł,
>
> On Thu, 11 May 2023 at 21:59, Pawel Urbanowicz
>  wrote:
> > I would like to contribute to log4j by implementing the Snowflake
> appender
> > which will use Snowpipe Streaming
> > <
> https://docs.snowflake.com/en/user-guide/data-load-snowpipe-streaming-overview
> >.
> > WDYT about my idea for contribution?
>
> We welcome every contribution to the larger Log4j ecosystem. We
> certainly can update our site and provide links to third party
> components.
>
> However we are reluctant to **maintain** additional components that
> have a very small user base and no committer uses. Of course we
> maintain popular components that started as third party components,
> but on the condition that the original author joins the team :-).
> This is regularly debated on this mailing list, most recently here:
>
> https://lists.apache.org/thread/3b4tn6t7zbhm66cw8yx8h8g26tyy50dj
>
> Since we can not forecast how popular your Snowflake appender will be
> I would propose to setup your own Github repository and give it a name
> like `logging-log4j-snowflake` (all our repos must start with
> `logging-`). If your component gets included into Log4j, we can simply
> fork the repo and continue the development there.
>
> If you hit any problems or need a code review, let us know.
>
> Piotr
>