hi, look at file core/sql/exp/ExpAlignedFormat.h which discussed internal
details of aligned format.
anoop
-Original Message-
From: Liu, Ming (Ming) [mailto:ming@esgyn.cn]
Sent: Tuesday, November 17, 2015 12:08 AM
To: dev@trafodion.incubator.apache.org
Subject: how to interpret the
Hi,
As it turns out, we immediately hit issues with having the website as part
of the product source tree.
The website is really a standalone entity that operates at a different
speed than the product and that should be on a different release schedule
than the overall product.
The speed issue
Gunnar,
It looks verify nice. I tested the links to make sure they worked and
pointed to relevant sections.
I read through some of the text and there are a few editorial nits:
file:///C:/Users/rmarton/Downloads/trafodion-web/release-notes-1-3-0.html
The first sentence mentions "Using the
Thanks, I thought that may be the case. It is location for publishing to
the staging and published sites.
So the source ought to be in our main repo, but can be single branch (either
master or a branch just for web).
If the maven build of the site needs docs from multiple releases, then that
I would think so. I'm not sure how it could pull it out of the different
release branches?
On Tue, Nov 17, 2015 at 6:04 PM, Steve Varnau
wrote:
> Thanks, I thought that may be the case. It is location for publishing to
> the staging and published sites.
>
> So the
Not the greatest drawing (trying to make it look abstract modern). The idea
is that Trafodion is about transactions and, therefore, safe hand offs. If
your hand off fails, then you lose the race.
https://drive.google.com/file/d/0BxlwNhWxn8iTUGxVYlkzbVV3VE0/view?usp=sharing
--
Thanks,
Gunnar
I agree with Steve. The product documentation is tied to the source version
and should stay with the code repository.
The artifacts from the product build can be staged some place before the
website is built.
We can probably script that part that pulls in the necessary documentation
files
Hi Suresh,
I submitted changes to the pom.xml today but did not touch the team entries
much. I will remove #2 for the web site instead relying on the
auto-generated page from the pom.xml. One fewer place to maintain this
information.
So, if you can update the pom.xml to match the project page,
The third list is correct. I just updated it Monday with all the changes.
Roberta
On Nov 17, 2015 7:34 PM, "Gunnar Tapper" wrote:
> Hi,
>
> I find THREE places where contributors are recorded:
>
> 1. Master pom.xml
> 2.
Hi,
I find THREE places where contributors are recorded:
1. Master pom.xml
2. https://cwiki.apache.org/confluence/display/TRAFODION/Contributors
3. http://incubator.apache.org/projects/trafodion.html
Which one is the most accurate?
--
Thanks,
Gunnar
*If you think you can you can, if you
Hi Gunnar,
The mentor and committer list at bullet item 3) is accurate. Roberta
updated it recently.
The contributor list in bullet item 2) is the best we have, though I would
like to go through it once more time and compare with JIRA, github & email.
We have not maintained bullet item 1 for a
Hi, all,
I am trying to understand the details of Trafodion's 'aligned format' feature.
If table T has two columns:
A B
INT NOT NULL PKCHAR(5)
== =
1 'abc'
DDL: create
The pom.xml file tracks all. I believe that you must have filed an ICLA to
be listed.
-Original Message-
From: Carol Pearson [mailto:carol.pearson...@gmail.com]
Sent: Tuesday, November 17, 2015 11:45 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Which contributor list is
Hi Dave,
I have run the full regressions with Trafodion 2.0 with no issues. By any
chance have you mixed the debug and release environments - meaning started
Hbase when you were in release mode and then switched to debug mode to start
Trafodion instance or vice versa. I have encountered this kind
Hi,
I replaced the files with a zip file to make the download easier. To test:
1. Download zip file
2. Unzip
3. Open index.html
4. Consider the look-and-feel and proposed menu items.
Thanks,
Gunnar
Thanks,
Gunnar
On Mon, Nov 16, 2015 at 6:01 PM, Gunnar Tapper
Hi Suresh,
1. Just placeholders for now. We'll work on better ones.
2. The panel on the bottom appears on each page. We can have it or not.
3. Yes, I looked at other projects and they do the same since, I guess,
they're recognizing Apache stuff.
4. We should update the pom.xml for sure.
Thanks,
Hi Gunnar,
This new website is so neat. Thank you!
I like the color scheme and overall layout. It is not cluttered and easy on
the eye.
I have a few minor suggestions which don't really fall under look-and-feel
category
1) the color scheme for graphics on the central panel somehow does not fit
Hi,
+1 on this last.
This makes sense to me, so long as it's aligned with the criteria for
Apache incubating projects. This makes it easier for folks to contribute
documentation changes that are versioned, and to change the website
framework, so win-win.. I definitely agree we need to keep
18 matches
Mail list logo