Ek prompt ko kai rows par chalane ka sabse sasta tareeka bulk processing hai, antahkriyatmak daam ka lagbhag aadha, aur jis file ki use zaroorat hai wo theek ek baat par berahem hai: nateeje usi kram mein lautte hain jisme wo poore hote hain. Aapki apni pehchaan hi wo iklauti cheez hai jo nateeje ko uski row se jodti hai, isliye dohrayi gayi pehchaan ka matlab hai do aise nateeje jinme farq nahi kiya ja sakta — chupchaap, aur kaam chal chukne ke baad. Yahaan template rows par phailta hai, pehchaan kisi column se aati hai ya bana di jaati hai, dohraav takraane ke bajaye badal diye jaate hain, aur kaam ka aakaar naapa jaata hai taaki aap jaanein ki aap kya bhej rahe hain.
Features
Har row ke liye ek request, template aur table se
Pehchaan aapke chune column se, ya banayi hui
Dohrayi gayi pehchaan takraane ke bajaye badal di jaati hai
Pehchaan unhi aksharon tak seemit ki jaati hai jo field leta hai
Kisi placeholder ko value na mile to row-dar-row warning
Kaam ka aakaar: requests ki sankhya, token anumaan aur file aakaar
Request ka mukhya bhaag aur wahi requests JSONL mein, dono
Bahut bada kaam baantta hai aur bhejne ka tareeka dikhata hai
Batch Request Builder kaise use karein
Prompt template aur apni rows paste kijiye
Model aur prati request token seema chuniye
Pehchaan ke liye column chuniye
Request ka mukhya bhaag download karke bhejiye
Example
Input
"custom_id": "Acme-Ltd"
Output
Row 2 repeats the id “Acme-Ltd”; renamed to “Acme-Ltd-2”
Nateeje kram se bahar aate hain, aur row tak lautne ka raasta sirf pehchaan hai.
Common errors aur troubleshooting
Nateejon ko rows se mila nahi pa raha. — Sthiti ke bajaye pehchaan se jodiye: nateeje poore hone ke kram mein lautte hain. Isiliye yahaan dohraav badal diye jaate hain.
Bhejne par reject ho raha hai. — Endpoint requests array wala JSON mukhya bhaag leta hai, JSONL file nahi. Dono diye jaate hain; bhejiye .json.
Mere prompt mein placeholder aksharsah reh gaya. — Us row ke paas uske liye value nahi thi. Sabhi prabhavit rows, placeholder ke naam ke saath, soochibaddh hoti hain.
Kaam bahut bada hai. — Use baant lijiye. Sankhya paar hote hi das hazaar requests tak ki files apne aap suggest kar di jaati hain.
Aksar pooche jaane wale sawaal
Bulk processing sasti kyun hai?
Kyunki wo antahkriyatmak nahi hai. Kaam qatar mein lagkar tab chalta hai jab kshamta ho, aur uski yojana banana kahin aasaan hai — isiliye daam lagbhag aadha. Aap deri badal rahe hain, gunvatta nahi.
Apni pehchaan kis liye hai?
Nateejon ko inputs se milane ke liye. Nateeje bhejne ke kram mein nahi, poore hone ke kram mein aate hain, isliye source row se bharosemand jod pehchaan hi hai.
Do rows ki pehchaan ek ho to?
Asli kaam mein do aise nateeje jinme farq nahi kiya ja sakta. Yahaan dohraav badal diya jaata hai aur bata diya jaata hai, aur ye abhi pata chalna kahin behtar hai.
Endpoint JSON leta hai to JSONL output kyun?
Line-aadharit tools ke liye: bade kaam ko baantna, do versions ki tulna, kisi aur chalane wale ko dena. Bheja JSON mukhya bhaag hi jaata hai.
max_tokens kaise chunoon?
Itna bada ki koi jawab kate nahi: kata hua nateeja dobara chalana padta hai. Dikhayi gayi upari seema maanti hai ki har request poora quota lega — ye sabse buri sthiti hai, anumaan nahi.