gupta-sahil01 commented on code in PR #6436: URL: https://github.com/apache/texera/pull/6436#discussion_r3641183448
########## agent-service/src/recommender/hardcoded-rules.ts: ########## @@ -0,0 +1,211 @@ +/** + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +/** + * Hardcoded "what usually comes next" table for the Version 1 operator + * recommender (apache/texera#5240). Kept deliberately small and readable: a + * coarse category per operator, a ranked successor list per category, plus a + * handful of specific overrides for the most common dataflow patterns. + * + * Operator type strings here must match the `@JsonSubTypes` names registered on + * `LogicalOp` (the catalog the frontend and compiler use). Suggestions are + * validated against the live operator catalog before being returned, so a stale + * entry here degrades to "not suggested" rather than to a broken suggestion. + */ + +export type OperatorCategory = "source" | "transform" | "aggregate" | "join" | "order" | "udf" | "ml" | "sink"; Review Comment: How is "rowOps" as a broader name? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
