[native] Naming convention clarification

[Mionsz]

I am not sure if the valid and 'should use' name for presto-native-execution was declared. This makes some people confused and not sure if or not the listed bellow are same product:

• Prestissimo
• PrestoCpp
• presto-native-execution
• Presto native server

Could we have this clarified and replaced in the documentation or can we make a vocabulary that will clarify this?
@majetideepak

[rohanpednekar]

@psbell-meta Could you please take this further?

[mbasmanova]

CC: @aditi-pandit @amitkdutta @xiaoxmeng

[spershin]

@Mionsz
Is the issue only about references in the docs or something else?

Essentially they are all the same, although the semantics might slightly change, like "Presto native server" - what does that even mean. :)
Historically, through the years of development (about 2 now) the names were brought in by different people and adopted with a different degree.

These days I try to use Presto Native and nothing else.
The folder "presto-native-execution" will likely stay as is or we can rename it if that's a good practice.
Docs can be modified, but we need to some to a consensus as to what name is the 'one to rule them all'. :)

[Mionsz]

@spershin The purpose of my question is more to clarify the naming convention - as I had an occasion to see it can confuse new users - and also it was a kind of management open question to ask what should be used like in internal documentation etc. Btw. having documentation refactored would also be a nice-to-do.

Nevertheless a simple vocabulary in documentation should be created additionally to clarify what is the proper name and how people use to call this query engine. I am not sure but this can have an impact on google search ranges and project visibility - it easier to find product if the name is clarified :).

Btw If there is some kind of consensus I can do documentation refactoring.

[spershin]

@Mionsz

Btw If there is some kind of consensus I can do documentation refactoring.

That is probably the biggest issue.
Everyone is working on it, but no one really thinks that one unified name is important enough to get it sorted out or takes initiative to actually do something about it.

I would go as far here as to suggest to use "Presto Native", unless some in context it does not fit. :)

[Mionsz]

@mbasmanova @spershin Could you rise this issue or discuss it on corporate/team level and give a kind of permanent answer or is the "Presto Native" the one? I ask as I do feel "Presto Native" is not a catchy name at all, "Prestissimo" is lots better and will probably give more consistent search results than two words name and this implicates far greater 'ranges'.

[Mionsz]

Then we could write: "Prestissimo is a Presto Worker native execution query engine written using low-level programming languages like C++ and overcoming all of JAVA performance bottlenecks by utilizing CPU vector operations instructions sets..."

[mbasmanova]

@Mionsz I like the description you proposed above and agree that Prestissimo is a better name than Presto Native. I'd like to wait for @majetideepak Deepak to come back (after the holidays) to bring this up for discussion and make a decision.

CC: @aditi-pandit

[majetideepak]

I concur with @mbasmanova and @Mionsz. We should use Prestissimo as the main name. Just like Databricks calls their stack Photon.
@Mionsz do you still have the bandwidth to implement this name change?

[Mionsz]

@majetideepak Yes I can handle this but probably not faster than in 2 weeks from now .

[majetideepak]

@Mionsz that works! I will be happy to help review.