Hans,
It didn’t occur to me your proposed change would work. I was always
thinking we shouldn’t be adding the omitted columns in non-aligned format.
You can file a JIRA and I will fix it.
Selva
*From:* Anoop Sharma [mailto:anoop.sha...@esgyn.com]
*Sent:* Tuesday, March 15, 2016 6:03 PM
yes, one cqd to switch between one or the other behavior in all formats is
the right way to go.
Doing the other way based on the row format would cause more issues when we
support hybrid format rows where some columns are in aligned format and
others
are not.
anoop
*From:* Hans Zeller
Again, IMHO that's the wrong way to go, but I hope others will chime in.
Dave gave the best reason, it's a bad idea to make the semantics of UPSERT
depend on the internal format. Here is what I would suggest, using Selva's
table (proposed changes in red - hope Apache won't mangle them):
I believe phoenix doesn’t support insert semantics or the non-null default
value columns. Trafodion supports insert, upsert, non-null default value
columns as well as current default values like current timestamp and
current user.
Upsert handling in Trafodion is same as phoenix for non-aligned
Yes, that's what I had in mind, using a CQD as the syntax:
UPSERT handling aligned formatnon-aligned format
--
---
default behaviorreplace row replace row (create
all
OK. Then, it'll not be covered in the upcoming admin guide.
On Tue, Mar 15, 2016 at 2:05 PM, Sean Broeder
wrote:
> I think the concept of a warm start is a carryover from early SeaQuest
> days. A warm start was proposed to maintain some monitor and TM states,
> but it
Not sure we want the logical semantics of an operation to depend
on the physical layout of the row.
Would be better to have different syntax for each. With an explanation that
one works faster on one format, and the other faster on the other format.
*From:* Eric Owhadi
Would there be a problem if we implemented the phoenix semantic for non
align format, and the upsert semantic proposed by Hans in align format?
This would allow speed optimization without having the user to know about
subtle differences?
Eric
*From:* Anoop Sharma
Phoenix has upsert command and from what can tell, they originally came up
with upsert syntax.
Their semantic is to insert if not present and update the specified columns
with the specified values if present.
We did do an experiment and upsert only updates the specified columns.
Maybe we can
Hi,
It seems that when ANSI first added MERGE to the standard, it was portrayed
as “upsert” (see https://en.wikipedia.org/wiki/Merge_(SQL)).
I agree though that we are free to define our UPSERT to mean anything we
want.
I like what you suggest. Since our UPSERT syntax already specifies
Hi,
Here is a question on how we should define the meaning of an UPSERT
statement. UPSERT is not part of the ISO/ANSI SQL standard, so we have some
leeway to define it.
My personal feeling is that UPSERT should either insert a brand-new row or
it should completely replace an existing row, but it
I think the concept of a warm start is a carryover from early SeaQuest
days. A warm start was proposed to maintain some monitor and TM states,
but it never was fully implemented.
Regards,
Sean
*From:* Liu, Ming (Ming) [mailto:ming@esgyn.cn]
*Sent:* Tuesday, March 15, 2016 10:03 AM
>From what I understand, this will not work. What you need to do is to do
what gomon.cold does; that is, interact with sqshell telling it what you
want done.
On Tue, Mar 15, 2016 at 11:31 AM, Amanda Moran
wrote:
> Hi there All-
>
> So this is what is suggested to be able
Hi,
Just to complicate this a bit... :)
The documentation for the Trafodion client software is:
http://trafodion.apache.org/docs/client_install/index.html
It might be necessary to add a column that describes the content of each
document if people can't correlate "client" with "ODBC" or "JDBC"
The purpose I guess is to bypass time-consuming database recovery if it is a
warm start. Say, if you have a clean shutdown of Trafodion, you can warm
restart it. If one use ‘ckillall’, or simply loss power, one needs a cold
start. But I think this is just the concept. May not support yet? We
BTW, in what cases should gomon.warm or the sqstart warm argument be used?
Thanks,
Gunnar
On Tue, Mar 15, 2016 at 10:30 AM, Narendra Goyal
wrote:
> Yes, one can follow the commands in ‘gomon.cold’ (that sqstart uses (what
> Selva mentioned)) to startup without
Done. https://issues.apache.org/jira/browse/TRAFODION-1894
*From:* Gunnar Tapper [mailto:tapper.gun...@gmail.com]
*Sent:* Tuesday, March 15, 2016 8:52 AM
*To:* user@trafodion.incubator.apache.org
*Subject:* Re: 答复: where to download Trafodion odbc/jdbc install package?
I suggest a Jira and
Yes, one can follow the commands in ‘gomon.cold’ (that sqstart uses (what
Selva mentioned)) to startup without sqstart.
As such, before ‘sqstart’ executes the commands in ‘gomon.cold’, it does
some other checks (like checks for orphan processes), and cleans up IPC
constructs (semaphores,
I think Dave and Ming are onto something. If I'm looking for ODBC or JDBC
drivers, I'm most likely searching for "ODBC" or "JDBC" not "Clients". 6
If we could list these on the page somehow, that would be very helpful -
not just for searching, but also once I land on that page, I know what it
is
I suggest a Jira and then anyone can make the change. :)
On Tue, Mar 15, 2016 at 9:45 AM, Carol Pearson
wrote:
> I think Dave and Ming are onto something. If I'm looking for ODBC or JDBC
> drivers, I'm most likely searching for "ODBC" or "JDBC" not "Clients". 6
>
>
The use case is how Apache Ambari works: it assume node-by-node management
of services. This is how you achieve rolling upgrades, stopping all
services on a node, etc.
I wonder if it's possible to first start the monitor (using the startup
command) and then start/stop other components per node.
From my understanding, it is invalid to start trafodion on node by node mode.
Monitor simulate a single image of operating system from a bunch of nodes. One
process can be configured to be a pair: active and standby. So when start a
trafodion process, it will start two processes on two nodes.
Yes. The sqgen command takes in the configuration file for the trafodion
cluster and generates gomon.cold, gomon.warm and other relevant scripts.
These generated scripts are copied to all nodes in the cluster. These
scripts are nothing but the commands to sqshell. sqstart uses either
gomon.cold
23 matches
Mail list logo