[ANNOUNCE] Release Apache Trafodion 2.0.1-incubating

[Steve Varnau]

I am pleased to announce release of Apache Trafodion 2.0.1-incubating.



This is a small patch release based on 2.0.0-incubating, which adds
convenience binaries for client-side tools.



Detailed release notes are available at:
http://trafodion.incubator.apache.org/release-notes-2-0-1.html



Source and Binaries are available from mirror sites:
http://trafodion.incubator.apache.org/download.html



--Steve





DISCLAIMER

Apache Trafodion is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by Apache Incubator. Incubation is required of
all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF.

[VOTE] Release Apache Trafodion 2.0.1 (incubating)

[Steve Varnau]

Hello,



This is a call to vote on the patch release 2.0.1-incubating (Release
Candidate 1).



The changes were small, just to address things that came up in the 2.0.0
reviews, primarily addressing the issue that prevented providing a
convenience binary of the clients package.



Changes since 2.0.0:

   [TRAFODION-2024] Openssl libraries (ssl & crypto) are linked dynamically

   [TRAFODION-2023] Clarify license text; Also small mods to instructions
on running RAT

   Bump release version number to 2.0.1; Also backported a one line change
to a test expecting specific release number



The trafodion community has approved RC1 for release.

<
https://lists.apache.org/thread.html/428f04f6f2a3d500f31d059a92a44770d2a2b6f59f2a0f33d6a0c93f@%3Cdev.trafodion.apache.org%3E
>



The tag for this candidate is “2.0.1rc1”. Git repository: git://
git.apache.org/incubator-trafodion.git

https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=7f4add54e46bb5395069e2b77bcdfa4024efc006



Release artifacts are:

https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.1-RC1

Artifacts are signed with my key (7F14AF20), which is in

https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS



Instructions:

  Setting up build environment:
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment


  Building:
https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source



[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)



Vote will be open for at least 72 hours, unless cancelled.

I will not be available next week, so Roberta Marton will be following up
on this release.



Thanks,

--Steve

[ANNOUNCE] Release Apache Trafodion 2.0.0-incubating

[Steve Varnau]

On behalf of the Trafodion community, I'm happy to announce our second
major Apache (incubating) release.

Apache Trafodion (incubating) is a web-scale SQL-on-Hadoop solution
enabling transactional or operational workloads on Hadoop.

Apache Trafodion 2.0.0-incubating

New Features
* This is the first release to include convenience binaries. Due to a
package/license issue (TRAFODION-2024), the clients binary package was not
included. This is being fixed, and a patch release (2.0.1) is expected
soon.
* Support for Hadoop distributions CDH 5.4, HDP 2.3, as well as Apache
HBase 1.0 (TRAFODION-1706)
* Ability to online add / remove nodes from a Trafodion instance
(TRAFODION-1885)
* Support transaction protection for DDL operations (TRAFODION-1798)
* Native support for Large OBjects (BLOB and CLOB data types) (preview
mode)
* Support to ALTER all attributes of a column (TRAFODION-1844)
* Support for GBK charset in SQL TRANSLATE function (TRAFODION-1720)

Improvements
* Advanced predicate pushdown (TRAFODION-1662)
* Improved co-ordination between transactions and HBase region splits /
rebalance (TRAFODION-1648)
* Optimize MDAM scans with small scanner (TRAFODION-1900)
* Integrate library management into Trafodion metadata (TRAFODION-1879)
* Improved support for UPDATE STATISTICS for large tables (up to 1B rows)
* Numerous build improvements

Fixes
* This release contains 250+ fixes.

Detailed release notes will be posted on the project web site soon.
http://trafodion.incubator.apache.org/

Source and Binaries are available:
http://www.apache.org/dyn/closer.cgi/incubator/trafodion/apache-trafodion-
2.0.0-incubating/

--Steve


DISCLAIMER

Apache Trafodion is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by  Apache Incubator. Incubation is required
of all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Steve Varnau]

This vote passes, with condition of not including the client binary
package.

-1 (binding) Justin Mclean  (With client convenience binary)
+1 (binding) Justin Mclean (Without the client convenience binary)
+1 (binding) Michael Stack (carried over from dev list vote)
+1 (binding) Jean-Baptiste Onofre
+1 (binding) Sergio Fernandez

Thanks to those who took time to review and vote!

The podling community will decide whether to spin another release
candidate to fix the
client binary to NOT bundle OpenSSL or to release 2.0.0 (without client
binary) and follow
it immediately with a patch (2.0.1) release.

--Steve


> -Original Message-
> From: Steve Varnau [mailto:steve.var...@esgyn.com]
> Sent: Tuesday, May 31, 2016 10:10 AM
> To: 'general@incubator.apache.org' <general@incubator.apache.org>
> Subject: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
>
> Hello,
>
> This is a call to vote on releasing Apache Trafodion 2.0.0-incubating
(Release
> Candidate 3).
>
> The trafodion community has approved RC3 for release.
> Vote result:
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-
> dev/201605.mbox/%3Cebe8936d36c9cedc2fbf65a94e6c5cbf%40mail.gmail.co
> m%3E
> Or in Pony Mail: https://lists.apache.org/thread.html/Zl1sh41t2mahwox
>
> Voting thread: http://mail-archives.apache.org/mod_mbox/incubator-
> trafodion-
> dev/201605.mbox/%3C85e78601a290f595707ee81d033c6b4c%40mail.gmail.co
> m%3E
>
> Release artifacts:
>
https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.0
-RC3
> Artifacts are signed with my key (7F14AF20), which is in
> https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
> This is the first release we are including convenience binaries built
from the
> source code artifact.
>
> The tag for this candidate is "2.0.0rc3". Git repository:
> git://git.apache.org/incubator-trafodion.git
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> trafodion.git;a=tag;h=1a8942c91e58212968d94478db18005568f4
>
> The JIRA release notes:
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620;
v
> ersion=12333044
>
> Instructions for
> Setting up build environment:
>
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environ
> ment
> Building:
> https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Please vote by Friday, June 3, Noon Pacific Time (7pm UTC).
>
> Thank you,
> --Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Steve Varnau]

Stian,

Thanks for the note. Since it says 5002 "applies to software containing or
designed for use with encryption software", means that we would add our dist
directory even if we do not bundle OpenSSL, but merely have code that links
with it?

--Steve


> -Original Message-
> From: Stian Soiland-Reyes [mailto:st...@apache.org]
> Sent: Thursday, June 2, 2016 7:20 AM
> To: general@incubator.apache.org
> Subject: RE: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
>
> Note distributing OpenSSL mean you need to update the Trafodion entry on
>
> http://www.apache.org/licenses/exports/
>
> to also include your dist folder.
>
> On 1 Jun 2016 6:54 p.m., "Steve Varnau" <steve.var...@esgyn.com> wrote:
>
> > Justin,
> >
> > Thanks for clarifying the issues here.  I will write JIRAs to fix the
> > two
> > minor issues in next release (clarify the rescinded BSD-4 clause and
> > remove
> > the GPL part of the dual license).
> >
> > Looking at the openssl issue, I want to figure out why we are statically
> > linking the libraries.  If there is a key reason it needs to be static
> > rather than dynamically linked, then I'll want to go to legal-discuss
> > and
> > ask whether we can distribute it, given license changes in the works.
> >
> > If we can change the build to change to dynamic linking and not include
> > openssl in the binaries, then perhaps the expedient thing is to go ahead
> > with this release, minus the client binary. And re-package it for next
> > release.
> >
> > Thanks!
> >
> > --Steve
> >
> >
> > > -Original Message-
> > > From: Justin Mclean [mailto:jus...@classsoftware.com]
> > > Sent: Tuesday, May 31, 2016 8:15 PM
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
> > >
> > > Hi,
> > >
> > > +1 (binding) to release source package, but -1 for the client
> > > connivence
> > > binary
> > > until the 4 clause BSD licensing issue is resolved.
> > >
> > > For the source released I checked:
> > > - all files have incubating
> > > - signatures check out
> > > - disclaimer exists
> > > - LICENSE and NOTICE good
> > > - No unexpected binary in source
> > > - All ASF licensed file have ASF headers
> > >
> > > The source LICENSE has a minor issue. It mentions the 4 clause BSD
> > license
> > > which is not compatible with the Apache license (only the 2 and 3
> > > clause
> > > BSD
> > > licenses are) [1][2]. In this case the extra clause has been recinded
> > > [3]
> > > you
> > > might want to reword/state that in the license.
> > >
> > > But that does mean there is an issue with the client binary release as
> > > that
> > > includes OpenSSL which lists a 6 clause BSD style license (similar to
> > > a 4
> > > clause
> > > BSD license) and SSLeay under a 4 clause BSD license. You may need to
> > > clarify
> > > this on legal discuss. It may be that their intent to move to an
> > > Apache
> > > licence
> > > may mean you can hold off on doing anything but I’m not 100% sure.
> > > [4][5]
> > >
> > > I would also remove the GPL license text from the server’s LICENSE
> > > file
> > to
> > > make
> > > it clear which license it’s included under. If something is dual
> > > licensed
> > > you
> > > select which licence you want to use.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://www.apache.org/legal/resolved.html#category-a
> > > 2. https://issues.apache.org/jira/browse/LEGAL-185
> > > 3. https://opensource.org/licenses/BSD-3-Clause
> > > 4. https://www.openssl.org/blog/blog/2015/08/01/cla/
> > > 5. https://wiki.openssl.org/index.php/License
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Steve Varnau]

Justin,

Thanks for clarifying the issues here.  I will write JIRAs to fix the two
minor issues in next release (clarify the rescinded BSD-4 clause and remove
the GPL part of the dual license).

Looking at the openssl issue, I want to figure out why we are statically
linking the libraries.  If there is a key reason it needs to be static
rather than dynamically linked, then I'll want to go to legal-discuss and
ask whether we can distribute it, given license changes in the works.

If we can change the build to change to dynamic linking and not include
openssl in the binaries, then perhaps the expedient thing is to go ahead
with this release, minus the client binary. And re-package it for next
release.

Thanks!

--Steve


> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: Tuesday, May 31, 2016 8:15 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
>
> Hi,
>
> +1 (binding) to release source package, but -1 for the client connivence
> binary
> until the 4 clause BSD licensing issue is resolved.
>
> For the source released I checked:
> - all files have incubating
> - signatures check out
> - disclaimer exists
> - LICENSE and NOTICE good
> - No unexpected binary in source
> - All ASF licensed file have ASF headers
>
> The source LICENSE has a minor issue. It mentions the 4 clause BSD license
> which is not compatible with the Apache license (only the 2 and 3 clause
> BSD
> licenses are) [1][2]. In this case the extra clause has been recinded [3]
> you
> might want to reword/state that in the license.
>
> But that does mean there is an issue with the client binary release as
> that
> includes OpenSSL which lists a 6 clause BSD style license (similar to a 4
> clause
> BSD license) and SSLeay under a 4 clause BSD license. You may need to
> clarify
> this on legal discuss. It may be that their intent to move to an Apache
> licence
> may mean you can hold off on doing anything but I’m not 100% sure. [4][5]
>
> I would also remove the GPL license text from the server’s LICENSE file to
> make
> it clear which license it’s included under. If something is dual licensed
> you
> select which licence you want to use.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/legal/resolved.html#category-a
> 2. https://issues.apache.org/jira/browse/LEGAL-185
> 3. https://opensource.org/licenses/BSD-3-Clause
> 4. https://www.openssl.org/blog/blog/2015/08/01/cla/
> 5. https://wiki.openssl.org/index.php/License
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Steve Varnau]

Hello,

This is a call to vote on releasing Apache Trafodion 2.0.0-incubating
(Release Candidate 3).

The trafodion community has approved RC3 for release.
Vote result:
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201605.mb
ox/%3Cebe8936d36c9cedc2fbf65a94e6c5cbf%40mail.gmail.com%3E
Or in Pony Mail: https://lists.apache.org/thread.html/Zl1sh41t2mahwox

Voting thread:
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201605.mb
ox/%3C85e78601a290f595707ee81d033c6b4c%40mail.gmail.com%3E

Release artifacts:
https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.0
-RC3
Artifacts are signed with my key (7F14AF20), which is in
https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
This is the first release we are including convenience binaries built from
the source code artifact.

The tag for this candidate is "2.0.0rc3". Git repository:
git://git.apache.org/incubator-trafodion.git
https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=
1a8942c91e58212968d94478db18005568f4

The JIRA release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620;
version=12333044

Instructions for
Setting up build environment:
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environ
ment
Building:
https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Please vote by Friday, June 3, Noon Pacific Time (7pm UTC).

Thank you,
--Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: GitHub vs. the mailing lists

[Steve Varnau]

Infra can configure the github to mailing list & github to JIRA for you.

In trafodion, we have all github PR and comments going to a codereview mail
list
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-codereview/
So there is a catch-all, even if the PR title is not in the correct format
to mirror into Jira. (And for those that prefer email notice versus
following on GH or Jira.)

--Steve


> -Original Message-
> From: Mike Jumper [mailto:mike.jum...@guac-dev.org]
> Sent: Wednesday, May 18, 2016 10:00 AM
> To: general@incubator.apache.org
> Cc: d...@guacamole.incubator.apache.org
> Subject: Re: GitHub vs. the mailing lists
>
> On May 18, 2016 9:54 AM, "Jean-Baptiste Onofré"  wrote:
> >
> > Hi Mike,
> >
> > it's what we are doing at Beam.
> >
> > A PR submission result:
> > - to a mail on the mailing list
> > - to a comment in Jira (if the PR contains commit with issue ID).
> >
>
> How have you achieved this?
>
> For Guacamole, we're seeing emails for the merge of a PR only (due no
> doubt
> to hooks in the ASF git repos). Comments on a PR, etc. will not find their
> way to the list.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: LICENSE info for ALv2, not ASF

[Steve Varnau]

> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: Monday, March 7, 2016 2:10 PM
> To: general@incubator.apache.org
> Subject: Re: LICENSE info for ALv2, not ASF
>
> HI,
>
> Current recommendation is not to include it [1] but it’s not an error to
> do so.
>
> Justin
>
> 1.http://www.apache.org/dev/licensing-howto.html#alv2-dep
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Good point. That section does make clear the distinction between the Apache
licensed SW and ASF SW.

Thanks,
-Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: LICENSE info for ALv2, not ASF

[Steve Varnau]

> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Monday, March 7, 2016 1:09 PM
> To: general@incubator.apache.org
> Subject: Re: LICENSE info for ALv2, not ASF
>
> On 3/7/16, 12:26 PM, "Craig Russell"  wrote:
>
> >As I understand it, LICENSE is for licenses. Period. If advertising is
> >required, the NOTICE file is used.
>
> Sorry, I should have been more clear.  When I said "consider NOTICE" I
> meant that any NOTICE for the non-ASF AL dependency may have content that
> needs to into the NOTICE and not LICENSE.
>
> >
> >If there are third party works included in a distribution that use the
> >same Apache 2.0 license as any Apache components, the license file
> >already contains the appropriate license.
>
> Agreed.  Sebb's recommendation, AIUI, was to simply mention in LICENSE
> that there is a non-ASF AL bundle without copying the entire LICENSE.
>
> -Alex

Got it. Thanks Alex & Craig for the clarifications.

-Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

LICENSE info for ALv2, not ASF

[Steve Varnau]

Hi,



I’m compiling information for LICENSE file for a binary distribution.  We
(Trafodion) have a bundled dependency that is Apache-2.0 license, but not
part of ASF.  Do we need to call these out in the license file, or only
call out the things that are non-Apache-2.0?



Thanks,

--Steve

RE: License statement third party modified code

[Steve Varnau]

Thanks, I will take the question to legal-discuss list.

--Steve


> -Original Message-
> From: Marvin Humphrey [mailto:mar...@rectangular.com]
> Sent: Thursday, February 18, 2016 6:36 PM
> To: general@incubator.apache.org
> Subject: Re: License statement third party modified code
>
> On Thu, Feb 18, 2016 at 8:59 AM, Steve Varnau <steve.var...@esgyn.com>
> wrote:
>
> > I did not see any responses in the past week on the general list.  Is
> > there
> > another place I should ask this question?
>
> This was a good list to ask on.  Since you've haven't received
> answers, though, I'd ask on legal-discuss@apache next.
>
> For what it's worth, I haven't answered in part because although I
> have ideas about how these cases could be handled, I don't know if my
> ideas align with the recommendations you'd hear from others. This
> issue hasn't come up a lot since I got active in the Incubator around
> 2010 and the policy predates that.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: License statement third party modified code

[Steve Varnau]

Hi,



I did not see any responses in the past week on the general list.  Is there
another place I should ask this question?



--Steve



*From:* Steve Varnau [mailto:steve.var...@esgyn.com]
*Sent:* Thursday, February 11, 2016 9:15 AM
*To:* 'general@incubator.apache.org' <general@incubator.apache.org>
*Subject:* License statement third party modified code



Hello,



Instructions on the website regarding source headers:
http://www.apache.org/legal/src-headers.html

Gives instructions for “Treatment of third-party works”. Point five says:



Major modifications/additions to third-party should be
dealt with on a case-by-case basis by the PMC.



So here I am with cases we have in Trafodion. In both cases, I believe we
have handled the third-party copyright/license statements correctly in the
LICENSE file and in the source code.  The question is whether this code has
had so much modification that we need to also put an Apache license header
into these files, or some other sort of statement, or if it fine as is with
only the third-party copyrights?



Case 1:  One file (only couple hundred lines) that was taken from flex for
parsing was modified substantially to create new function in order to
handle parsing of Unicode text. As far as I can tell, all the
Unicode-specific work is specific to Trafodion and was developed by HP,
which was then granted to ASF.
https://github.com/apache/incubator-trafodion/blob/master/core/sql/parser/ulexer.h



Case 2: Several dozen tests that were written for Phoenix by Salesforce.
Trafodion took a copy of those tests after they were open-sourced, but
before the code was granted to ASF.  Trafodion adapted those tests to run
against Trafodion instead of Phoenix. The tests generally do the same
things as originally intended, but were heavily modified due to what
Phoenix supported versus what Trafodion supported at that time and since.
The forked tests were maintained separately over the last couple years,
they were not merged over after the initial copy.
https://github.com/apache/incubator-trafodion/tree/master/tests/phx/src/test/java/org/trafodion/phoenix/end2end



Any guidance?



--Steve

License statement third party modified code

[Steve Varnau]

Hello,



Instructions on the website regarding source headers:
http://www.apache.org/legal/src-headers.html

Gives instructions for “Treatment of third-party works”. Point five says:



Major modifications/additions to third-party should be
dealt with on a case-by-case basis by the PMC.



So here I am with cases we have in Trafodion. In both cases, I believe we
have handled the third-party copyright/license statements correctly in the
LICENSE file and in the source code.  The question is whether this code has
had so much modification that we need to also put an Apache license header
into these files, or some other sort of statement, or if it fine as is with
only the third-party copyrights?



Case 1:  One file (only couple hundred lines) that was taken from flex for
parsing was modified substantially to create new function in order to
handle parsing of Unicode text. As far as I can tell, all the
Unicode-specific work is specific to Trafodion and was developed by HP,
which was then granted to ASF.
https://github.com/apache/incubator-trafodion/blob/master/core/sql/parser/ulexer.h



Case 2: Several dozen tests that were written for Phoenix by Salesforce.
Trafodion took a copy of those tests after they were open-sourced, but
before the code was granted to ASF.  Trafodion adapted those tests to run
against Trafodion instead of Phoenix. The tests generally do the same
things as originally intended, but were heavily modified due to what
Phoenix supported versus what Trafodion supported at that time and since.
The forked tests were maintained separately over the last couple years,
they were not merged over after the initial copy.
https://github.com/apache/incubator-trafodion/tree/master/tests/phx/src/test/java/org/trafodion/phoenix/end2end



Any guidance?



--Steve